| Age | Commit message (Collapse) | Author |
|---|
|
|
|
echo-message is NOT enabled (issue #2016)
|
|
echo-message is enabled (closes #2016)
|
|
echo-message is enabled (issue #2016)
|
|
`blake2s-*` in option sec.crypt.hash_algo (closes #2008)
|
|
in hash functions (issue #2008)
|
|
|
|
(closes #2013)
|
|
|
|
an IRC command (closes #1992)
|
|
version
|
|
|
|
|
|
|
|
and user's guide
|
|
(issue #1973)
|
|
(issue #2010)
|
|
Regression was introduced in commit 817d1eaf8e0be700bf9b61dcbaf9db7ab507d3af.
|
|
|
|
|
|
|
|
|
|
|
|
This commit also includes support for passive DCC RESUME.
There was also a potential segfault with calling `atoi(pos_token)` when `pos_token` is NULL, so `token` is set to be stored as a string. Although it is an integer, we don't need to store it as such. That's really more of an implementation detail.
|
|
Before making any significant changes, let's identify the existing xfer types by either active or passive.
|
|
This makes it easier to handle the optional "token" argument at the (right) end, which will be necessary to support passive DCC.
Incidentally, this is RtL parsing order is the reason why you'd get a cryptic "0" address error when attempting to do passive DCC: the "token" argument gets misinterpreted as the "size" argument. Every argument "shifts" over by one, leaving an address (port) of "0".
|
|
|
|
Only text between angle brackets (eg: "<name>") must be translated.
|
|
name contains wide chars
|
|
options weechat.buffer.* (issue #352)
|
|
hdata_compare (closes #1066)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
command (issue #923)
|
|
This makes possible to disable a key hiding another (because shorter than the
other, and beginning with the same key).
For example if key "meta-a" is set to an empty command, it would not hide any
more the key "meta-a,1" which has a non-empty command.
|
|
|
|
|
|
|
|
|
|
#2007)
|
|
(issue #352)
|
|
|
|
|
|
|
|
|
