| Age | Commit message (Collapse) | Author |
|---|
|
|
|
#1558)
|
|
bars (closes #1939)
|
|
The question must be first asked on the #weechat channel.
|
|
|
|
|
|
|
|
from WeeChat < 4.0.0 (issue #1927)
|
|
|
|
https://ircv3.net/specs/extensions/utf8-only
|
|
|
|
Changed triggers:
- cmd_pass
- cmd_pass_register
- server_pass
|
|
`${sec.data.xxx}` and option autojoin_dynamic is enabled (closes #1934)
|
|
|
|
|
|
|
|
(closes #1718)
|
|
|
|
banned on channel (closes #88)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Changes:
- use "=" to separate key from value, add it only if value is set (any string,
including empty string)
- do not convert "_" to "-" in key
|
|
|
|
|
|
|
|
enabled (issue #1923)
|
|
|
|
|
|
|
|
draft/multiline is enabled (issue #1923)
|
|
are lines in buffer (issue #1923)
|
|
(closes #1927)
|
|
|
|
|
|
(issue #1923)
|
|
The function now allows only a single message. Newline chars ("\n") are allowed
in messages but not used as message separator.
This is a preparation work for the support of capability "draft/multiline".
|
|
IRC_COMMAND_CAP_SUPPORTED
|
|
|
|
|
|
|
|
no spaces
For example typing this on core buffer:
/t1
/t2
was not executing the two commands but sent the text to the buffer instead.
This is because WeeChat thinks it's a path, and the newline should indicate
it's not (like a space before the next slash: "/t1 /t2" is a command, not a
path, but "/t1/t2" is considered a path).
|
|
`command_options` when input_multiline is set to 0
The API functions `command` and `command_options` (when `split_newline` = 0,
which is the default value) don't split on newline and then the first line is
executed and the subsequent lines (after "\n") are ignored.
There are no changes when the input has multiple lines filled by the user: the
split is done and multiple commands are executed (for example if the user is
pasting multiple commands to execute).
|
|
|
|
|
|
|
|
|
