record it might have stopped a wrong timeout/io func (or probably not,
because new source func was allocated soon after, and it'd have the same tag
which would just be free'd twice).
git-svn-id: http://svn.irssi.org/repos/irssi/trunk@2324 dbcabf3a-b0e7-0310-adc4-f8d773084564
conditions if /SET dcc_download_path was set to some directory where other
users could write files as well. Also, the created file mode is always 0600
now.
git-svn-id: http://svn.irssi.org/repos/irssi/trunk@2318 dbcabf3a-b0e7-0310-adc4-f8d773084564
and it didn't work properly if nick was 9 chars with last char being '_'
(not very likely though :). Also handle properly the situation where nick
and alternate_nick are the same.
git-svn-id: http://svn.irssi.org/repos/irssi/trunk@2311 dbcabf3a-b0e7-0310-adc4-f8d773084564
it was also buggy and didn't work.. Anyway, now we don't anymore even try to
remove "non-wanted" modes set by server when reconnecting, if you really
don't want to have some mode, set it with -x in /set usermode.
git-svn-id: http://svn.irssi.org/repos/irssi/trunk@2304 dbcabf3a-b0e7-0310-adc4-f8d773084564
the connection_lost to TRUE, the disconnection is after the "server
incoming" signal is finished.
Changed irc_parse_incoming() back to not handling any commands in server's
input buffer after server_disconnect() is called, it's not safe enough.
git-svn-id: http://svn.irssi.org/repos/irssi/trunk@2299 dbcabf3a-b0e7-0310-adc4-f8d773084564
shouldn't emit the "server disconnected" again.
We'll now handle the remaining data coming from server after disconnection.
git-svn-id: http://svn.irssi.org/repos/irssi/trunk@2290 dbcabf3a-b0e7-0310-adc4-f8d773084564
use a destroyed server record when some /command disconnects the server
(shouldn't happen really) or when irc_send_cmd() fails sending data to server
and disconnects the server (I don't know if this ever happens, but if it does,
it very well could have caused crashes)
git-svn-id: http://svn.irssi.org/repos/irssi/trunk@2243 dbcabf3a-b0e7-0310-adc4-f8d773084564
which were part of it. Removed it now and replaced it with saving only
op/halfop/voice status. Might have caused some crashes? (hopefully did :)
git-svn-id: http://svn.irssi.org/repos/irssi/trunk@2234 dbcabf3a-b0e7-0310-adc4-f8d773084564
indicates if event belongs to redirection even while it didn't have any
redirection signal. Proxy uses this to figure out if the event should be
sent to clients or not (/WHOIS in proxy sent 3 middle lines to all clients
before this).
git-svn-id: http://svn.irssi.org/repos/irssi/trunk@2221 dbcabf3a-b0e7-0310-adc4-f8d773084564
server_redirect_event() to get a signal emitted when redirection begins /
ends.
git-svn-id: http://svn.irssi.org/repos/irssi/trunk@2215 dbcabf3a-b0e7-0310-adc4-f8d773084564
kills, stop reconnecting to the server entirely.
When reconnecting to server and setting back the old user mode, only use the
modes that we actually wanted to change with /MODE commands, don't try to
set back modes given to us by server (eg. +r).
git-svn-id: http://svn.irssi.org/repos/irssi/trunk@2205 dbcabf3a-b0e7-0310-adc4-f8d773084564
redirections have gone without reply to our redirection. This is because
the timeout itself may fail if lag to the server is too high.
git-svn-id: http://svn.irssi.org/repos/irssi/trunk@2177 dbcabf3a-b0e7-0310-adc4-f8d773084564
that are just given in server_redirect() (fixes a small problem of /MSG nick
who is away + /WHOIS nick, then receiving the first away reply from server
to /MSG command irssi thinks it's a reply to /WHOIS)
git-svn-id: http://svn.irssi.org/repos/irssi/trunk@2175 dbcabf3a-b0e7-0310-adc4-f8d773084564
are printed like receiving wall messages. /ACTION @#channel didn't work
properly.
git-svn-id: http://svn.irssi.org/repos/irssi/trunk@2169 dbcabf3a-b0e7-0310-adc4-f8d773084564
