| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
weechat protocol
|
|
They are used in completion of commands `/filter disable` and
`/filter enable`.
|
|
They are used in completion of commands `/trigger disable` and
`/trigger enable`.
|
|
|
|
Regression was indirectly caused by commit
d18f68e497c4244404ff8f4f50de82717b178e09 in core that allows to display all
control chars in buffers.
But the fix is in exec plugin: end of line in command output can now be "\r\n"
in addition to a single "\n".
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
(issue #1926)
|
|
|
|
|
|
#1808)
|
|
|
|
|
|
This allows you to use escape characters if you start the fifo command
with \ instead of *, in the same way as the escape_commands option in
the relay protocol. This allows you to send commands consisting of
multiple lines by using \n if the buffer has input_multiline set.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
capability) and not sending "CAP END" (issue #1040, issue #1796)
The bug was fixed in version 2.0 (issue #1040) but a regression in version 3.7
happened while using the new IRC parser for message arguments (issue #1796,
commit 96ed47126130ac62350aef4a9236009b7fc3cd5f).
|
|
"relay_client_irc_out"
|
|
This option was broken with commit 031bd45e3.
|
|
|
|
|
|
issue #1886)
|
|
|
