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
{{ message }}
This repository has been archived by the owner on Apr 17, 2020. It is now read-only.
==client2's view==
client1 [...] has joined #channel
client1 [...] has left #channel []
client1 [...] has joined #channel
...
...
//notice the lack of quit message.
The text was updated successfully, but these errors were encountered:
I haven't really investigated this yet, but I suspect this is caused by ignores being handled on two levels: the quit message from the irc server (of which there is only one) and the message being printed (of which there are as many as that client is on channels). The ignore is handled on one level, the ignore-exception on another. That is similar to a hilight-bug: #275 .
QUITs aren't the only thing affected by this, but it's probably the worst one.
I fear a complete solution for that sort of ignore problems would be similar to the solution in my comment in #275 : instead of doing the ignore immediately, flag a message as "to be ignored unless there is an ignore exception".
I'm attempting to hide JOINS PARTS QUITS from all channels except certain ones that I specify.
/ignore -except #channel JOINS PARTS QUITS
/ignore * JOINS PARTS QUITS
client2: /j #channel
client1: /j #channel
client1: /leave
client1: /j #channel
client1: /quit
==client2's view==
client1 [...] has joined #channel
client1 [...] has left #channel []
client1 [...] has joined #channel
...
...
//notice the lack of quit message.
The text was updated successfully, but these errors were encountered: