appear in the channel window.
- Make actions and ctcp to @#channel etc appear in the
channel window.
- Clean up the code a little.
This fixes bug #46 apart from incoming msg to +#channel.
git-svn-id: http://svn.irssi.org/repos/irssi/trunk@4589 dbcabf3a-b0e7-0310-adc4-f8d773084564
sorting type to use for the activity bar:
- refnum (default)
- recent (same as actlist_moves on)
- level (sort by window level, same ordering used by active_window command)
git-svn-id: http://svn.irssi.org/repos/irssi/trunk@4583 dbcabf3a-b0e7-0310-adc4-f8d773084564
the connection immediately. Also clarify the error message
when the SSL handshake fails.
This bug was introduced after 0.8.11.
git-svn-id: http://svn.irssi.org/repos/irssi/trunk@4576 dbcabf3a-b0e7-0310-adc4-f8d773084564
This is now on numeric 470 instead of 379.
It works with hyperion and charybdis, and puts the
channel you were forwarded to in the window the original
channel would be in.
git-svn-id: http://svn.irssi.org/repos/irssi/trunk@4575 dbcabf3a-b0e7-0310-adc4-f8d773084564
(should be displayed in status if it's a join failure,
channel window otherwise)
git-svn-id: http://svn.irssi.org/repos/irssi/trunk@4574 dbcabf3a-b0e7-0310-adc4-f8d773084564
that the CHANNEL_REC is still around when handlers for
specific numerics are executed. This allows removing the
ugly special case for 437; I will also use this for 470
(channel forwarding).
git-svn-id: http://svn.irssi.org/repos/irssi/trunk@4572 dbcabf3a-b0e7-0310-adc4-f8d773084564
"Bad user info" (case insensitive) in an ERROR message as
an indication of a server ban.
git-svn-id: http://svn.irssi.org/repos/irssi/trunk@4571 dbcabf3a-b0e7-0310-adc4-f8d773084564
'after' context, so that '/lastlog -hilight -after 10 foo' has the same
semantic as '/lastlog -hilight -before 10 foo'.
git-svn-id: http://svn.irssi.org/repos/irssi/trunk@4570 dbcabf3a-b0e7-0310-adc4-f8d773084564
fixing a race condition with parallel builds.
Submitted by mandriva
Slightly simplified by me
git-svn-id: http://svn.irssi.org/repos/irssi/trunk@4559 dbcabf3a-b0e7-0310-adc4-f8d773084564
This fixes bug #510. Note that #510 only happened if multiple
bans were sent before the MODE came back and multiple unbans
were sent before the MODE came back.
git-svn-id: http://svn.irssi.org/repos/irssi/trunk@4544 dbcabf3a-b0e7-0310-adc4-f8d773084564
this retries joins that failed because of netsplits
(channel temporarily unavailable (437), duplicate channel)
A few servers abuse 437 for juped channels which should
not be retried, you should disable channels_rejoin_unavailable
if this is a problem.
- Display 437 and 407 numerics if channels_rejoin_unavailable
is not enabled.
Bug #495
git-svn-id: http://svn.irssi.org/repos/irssi/trunk@4537 dbcabf3a-b0e7-0310-adc4-f8d773084564
reconnect_save_status() for a server that has not sent 001
yet, do not free and reallocate conn->channels twice, and do
not copy the channels if server->connrec->no_autojoin_channels
is set. It seems a special case because reconnect_save_status()
is not usually called for servers that have not sent 001
yet, but it can't really hurt.
git-svn-id: http://svn.irssi.org/repos/irssi/trunk@4532 dbcabf3a-b0e7-0310-adc4-f8d773084564
cannot /msg, user is +g) in the channel or query window,
if any.
- Put the target name in front of "generic" numerics
printed to the channel/query window (useful if there are
multiple in one window, or if there is no such window).
git-svn-id: http://svn.irssi.org/repos/irssi/trunk@4526 dbcabf3a-b0e7-0310-adc4-f8d773084564
