Bug#576120: Sending 333 in response to /query confuses rcirc.

2010-04-11 Thread trentbuck
Wilmer van der Gaast wrote: > I just also found http://www.alien.net.au/irc/irc2numerics.html which > seems like a great source for info like this; better than anything else > I found so far. > > Looks like 320 is more suitable for this and is abused by various > clients for showing misc. informat

Bug#576120: Sending 333 in response to /query confuses rcirc.

2010-04-11 Thread Wilmer van der Gaast
I just also found http://www.alien.net.au/irc/irc2numerics.html which seems like a great source for info like this; better than anything else I found so far. Looks like 320 is more suitable for this and is abused by various clients for showing misc. information in /WHOIS replies already. I'll swit

Bug#576120: Sending 333 in response to /query confuses rcirc.

2010-04-01 Thread Wilmer van der Gaast
Sigh. I could've known. :-( I spent a little while trying to pick a suitable number that isn't in use already, but 333 is definitely in use already for /topic, yeah. Bd choice, even though irssi let me get away with it. This is definitely BitlBee's fault. I should find another int to use. IRC

Bug#576120: Sending 333 in response to /query confuses rcirc.

2010-03-31 Thread Trent W. Buck
Package: bitlbee Version: 1.2.5-1 Severity: normal I got the error below when connecting rcirc (part of GNU Emacs) to bitlbee, which was speaking XMPP to an internal server (running ejabberd, I believe). rcirc's developer, rcy, believes bitlbee is at fault. Please investigate. I just got this