Age | Commit message (Collapse) | Author |
|
the string (issue #812)
Some tests are added as well to test the multiple masks in the string.
|
|
|
|
|
|
|
|
guide
|
|
|
|
|
|
|
|
|
|
|
|
(closes #781)
|
|
Windows subsystem for Linux (issue #770)
The test on socketpair() function is now made when hooks are
initialized (instead of doing the test at compilation time).
|
|
with Windows subsystem for Linux (closes #770)"
This reverts commit 399636f98453bdc1fca19b4dbc742993549aa6c3.
|
|
|
|
|
|
|
|
/input hotlist_clear
|
|
|
|
|
|
xfer_set_{local|remote}_address()
|
|
|
|
|
|
gui_buffer_input_buffer_init()
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
If the call to res_init() fails, the connection may be OK anyway
or in worst case it will fail (with an appropriate error) if the name
can not be resolved.
|
|
|
|
|
|
With weechat, if the network changes in anyway that causes resolv.conf
to be updated, that is not picked up, resulting in
irc: connecting to server XXXX.com/1026 (SSL)...
irc: address "XXX.com" not found
irc: error: Name or service not known
irc: reconnecting to server in 30 seconds
This happens, especially when one connects to an irc server behind a
VPN.
This can also happen when there is no network connectivity weechat was started
but later network is connected to.
The fix is simple, it relies on calling res_init (3) before getaddrinfo in
network_connect_child and other places.
res_init reloads the resolv.conf and getaddrinfo does not fail with
address resolution error.
|
|
Windows subsystem for Linux (closes #770)
|
|
irc: fix NULL pointer dereference in 734 command callback
|
|
found (closes #767)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
#573)
|
|
|
|
|
|
|
|
|
|
|
|
|