You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is related to #538 but concerns the part about the buffer being switched to on the relay.
Because /query switches the buffer on the relay, messages on that conversation are considered read and do not trigger a notification (this may only be the case on some setups, e.g. active connection to the relay from another machine).
Would it make sense to use /query -noswitchhere instead?
The text was updated successfully, but these errors were encountered:
Elarnon
added a commit
to Elarnon/weechat-android
that referenced
this issue
Sep 6, 2022
When clicking on a nick on the nicklist, the `/query` command is issued, causing the relay to switch its buffer to the query. weechat-android should switch the *client* buffer instead (see ubergeek42#538), but leave the relay buffer intact.
If the relay buffer is switched, it may cause missed notifications due to weechat incorrectly believing that messages have been seen on the relay, since the buffer is opened.
Fixesubergeek42#550
This is related to #538 but concerns the part about the buffer being switched to on the relay.
Because
/query
switches the buffer on the relay, messages on that conversation are considered read and do not trigger a notification (this may only be the case on some setups, e.g. active connection to the relay from another machine).Would it make sense to use
/query -noswitch
here instead?The text was updated successfully, but these errors were encountered: