Always buffer private messages for replay#521
Conversation
This is useful if connecting with multiple hosts, and want private messages to get replayed when connecting a second(+) host, or reconnecting the same host. To facilitate clearing the buffer, the ClearAllBuffers command will now also clear the query buffer. I've also updated the clearbufferonmsg module to clear query buffers on msg as that seemed appropriate (and how I want things to work). This is largely based on the work found at https://gist.github.com/jreese/1206300 Tested with 1.2 release.
|
Yes, yes, yes! |
|
So with one client without clearbufferonmsg module you'll end up receiving the same queries again and again? |
|
To trigger this line you need to send a command to *status yourself |
|
No. The ClearAllBuffers command now also clears queries. So if the user has set to always playback then they would issue this command as normal. |
|
In the case where you're not keeping buffer, and thus you have Auto Clear Chan Buffer set to true, wouldn't it be clearing the buffers as it sends them, thus clearing the query buffer? |
"as normal"? You may try @kylef's clientaway module, which makes use of |
|
clientaway doesn't work for me. I often leave my laptop connected in my office, but will connect from my phone while out and about. If buffers are going to replay, I want /all/ buffers to replay. query buffers shouldn't be a special case, if anything they are more important than channel buffers. |
|
Then it needs a separate setting ( |
|
Superseded by #598 |
This is useful if connecting with multiple hosts, and want private
messages to get replayed when connecting a second(+) host, or
reconnecting the same host. To facilitate clearing the buffer, the
ClearAllBuffers command will now also clear the query buffer.
I've also updated the clearbufferonmsg module to clear query buffers on
msg as that seemed appropriate (and how I want things to work).
This is largely based on the work found at
https://gist.github.com/jreese/1206300
Tested with 1.2 release.