When using PRIVMSG in an alias command (alias module), the message is sent to the IRC network and to ZNC's logs (log module) correctly, but not to connected clients. This can make it hard to test aliases, and strange to use them once set up because of the disconnect between knowing an alias's output was sent and not being able to see it in one's client.
In the interest of full disclosure, I first noticed this behavior in ZNC 1.6.x but did not test it in a nightly build myself. I walked a friend running ZNC 1.7.x-git-878-d4ae311 through the steps to confirm it is still present in a recent version.
Thought there was already an issue for this, since I actually noticed the bug months ago but forgot until a few days ago. Couldn't find one when I went looking for a status, though, so I guess I never made one.
When using `PRIVMSG` in an alias command (`alias` module), the message is sent to the IRC network and to ZNC's logs (`log` module) correctly, but **not** to connected clients. This can make it hard to test aliases, and strange to use them once set up because of the disconnect between knowing an alias's output was sent and not being able to see it in one's client.
In the interest of full disclosure, I first noticed this behavior in ZNC 1.6.x but did not test it in a nightly build myself. I walked a friend running ZNC 1.7.x-git-878-d4ae311 through the steps to confirm it is still present in a recent version.
Thought there was already an issue for this, since I actually noticed the bug months ago but forgot until a few days ago. Couldn't find one when I went looking for a status, though, so I guess I never made one.
<!-- github-sync-id:288313252 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
When using
PRIVMSGin an alias command (aliasmodule), the message is sent to the IRC network and to ZNC's logs (logmodule) correctly, but not to connected clients. This can make it hard to test aliases, and strange to use them once set up because of the disconnect between knowing an alias's output was sent and not being able to see it in one's client.In the interest of full disclosure, I first noticed this behavior in ZNC 1.6.x but did not test it in a nightly build myself. I walked a friend running ZNC 1.7.x-git-878-d4ae311 through the steps to confirm it is still present in a recent version.
Thought there was already an issue for this, since I actually noticed the bug months ago but forgot until a few days ago. Couldn't find one when I went looking for a status, though, so I guess I never made one.