Previously using option values
irc.look.buffer_open_before_join off
irc.look.buffer_switch_join on
and manually joining a channel which gets forwarded
(e.g. #linux -> ##linux-overflow on freenode) the channel buffer for
##linux-overflow was not switched to even though the option says it should
have.
This patch copies manual join and noswitch information for channels which
get forwarded.
This pointer is the first argument received by callbacks, and the
existing argument "data" is now automatically freed by WeeChat when the
object containing the callback is removed.
With this new pointer, the linked list of callbacks in scripts has been
removed. This will improve speed of scripts (using a lot of hooks),
reduce memory used by scripts and reduce time to unload scripts.
Following functions are affected in the C API:
* exec_on_files
* config_new
* config_new_section
* config_new_option
* hook_command
* hook_command_run
* hook_timer
* hook_fd
* hook_process
* hook_process_hashtable
* hook_connect
* hook_print
* hook_signal
* hook_hsignal
* hook_config
* hook_completion
* hook_modifier
* hook_info
* hook_info_hashtable
* hook_infolist
* hook_hdata
* hook_focus
* unhook_all_plugin
* buffer_new
* bar_item_new
* upgrade_new
* upgrade_read
Previously SASL did not fail when it was set up for the server but wasn't
supported by it. This makes no difference when the server's sasl_fail is
set to "continue" but might make a difference if set to "disconnect" or
"reconnect".
To make sure server connection is not made under such circumstances, this
patch adds an extra configurable ("on" by default) check to trigger SASL
failure when it is set up but not supported by the server. Although not
directly a SASL failure, this makes SASL not-authenticated scenarios all
handled consistently, while providing extra security by not silently
ignoring not being authenticated as requested.
Fixes#376. This avoids warnings for WHOX messages that we do not parse/
understand yet. Previously, IRC_PROTOCOL_MIN_ARGS was 5 where it should
have been 4 (which avoids warnings for WHOX commands only requesting one
WHOX type). Changing the behavior to support all different WHOX types
seems like a bad idea to me, as it's quite hard to figure out which
information was requested with the WHOX command.
The purpose of the fix is to display any PART received on a channel,
even if the nick is not found in the channel's nicklist
(when channel is "+a", all PART are received from nick "anonymous").
Sébastien Helleu