| Age | Commit message (Collapse) | Author |
|---|
|
|
|
automatic check of WHOX on the channel (issue #1212)
|
|
|
|
release notes
|
|
|
|
|
|
Explicitly link with -lpthread to fix detection and compilation on some Linux distributions.
|
|
|
|
|
|
|
|
(closes #1206)
Now if there are at least one relay client connected via weechat protocol,
the buffer is always added to the hotlist.
|
|
|
|
|
|
|
|
|
|
#1204)
|
|
|
|
|
|
core: update Japanese translations
|
|
|
|
|
|
|
|
#1200)
|
|
|
|
|
|
|
|
|
|
support the option "-server xxx"
|
|
|
|
(closes #1133)
When a buffer is added or updated in the hotlist, the buffer pointer is sent.
When the hotlist is cleared or resorted, the buffer pointer is NULL.
|
|
|
|
core: update Japanese translations
|
|
|
|
|
|
When there are multiple addresses for a server and a TLS handshake failure
occurs, the next server in the list will connect and then timeout without
performing any TLS handshake.
This is because irc_server_close_connection closes server->sock so the next
pipe to be created reuses that fd, but the hook for the handshake fd still
exists when the next connection attempt is started.
The hook for network_connect_child_read_cb is never added because a hook
for the reused fd number still exists.
Resolve this by removing the handshake hook before calling the connect
callback.
|
|
|
|
|
|
|
|
|
|
|
|
hook_process_hashtable (plugin API reference)
|
|
hook_process_hashtable (plugin API reference)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
