code logs -> 2010 -> Sat, 29 May 2010< code.20100528.log - code.20100530.log >
--- Log opened Sat May 29 00:00:17 2010
00:08 Thaqui [Thaqui@27B34E.D54D49.F53FA1.6A113C] has joined #code
00:10
< Namegduf>
For Python, have you looked at Phenny?
00:11
< Namegduf>
I've had it recommended.
00:15 AnnoDomini [annodomini@Nightstar-d8256a85.adsl.tpnet.pl] has quit [[NS] Quit: Gnurgh.]
00:18 Derakon[AFK] is now known as Derakon
00:56 Reiv[Graduate] [orthianz@Nightstar-bb68d970.xnet.co.nz] has joined #code
01:06 gnolam [lenin@Nightstar-38637aa0.priv.bahnhof.se] has quit [[NS] Quit: Z?]
01:08 Attilla [Attilla@Nightstar-d665c003.threembb.co.uk] has quit [[NS] Quit: ]
01:11
<@ToxicFrog>
I generally don't work in Python, so, no
01:11
< Namegduf>
Ah.
01:29 Derakon is now known as Derakon[AFK]
01:35 Serah [Z@26ECB6.A4B64C.298B52.D80DA0] has quit [Ping timeout: 121 seconds]
01:54 Derakon[AFK] is now known as Derakon
02:24 Derakon is now known as Derakon[AFK]
02:33 Serah [Z@3A600C.A966FF.5BF32D.8E7ABA] has joined #code
02:44 cpux [Moo@Nightstar-20a84089.dyn.optonline.net] has quit [Ping timeout: 121 seconds]
02:59 cpux [Moo@Nightstar-20a84089.dyn.optonline.net] has joined #code
04:19 Serah [Z@3A600C.A966FF.5BF32D.8E7ABA] has quit [Ping timeout: 121 seconds]
04:19
< celticminstrel>
Okay. I have no idea why this function is getting called when it shouldn't be...
04:32
< celticminstrel>
...ooh, I think I forgot to update a variable. Duh.
04:33
<@ToxicFrog>
http://github.com/ToxicFrog/xclua !
04:36
< celticminstrel>
What's that?
04:36
<@ToxicFrog>
The xchat plugin for lua I've been talking about.
04:37
< celticminstrel>
Ah.
04:57
< celticminstrel>
So, if I create a method with the same name as a superclass method, it'll be called instead of that method, right?
04:58
< celticminstrel>
I need it to be called in addition...
05:00
<@ToxicFrog>
So call the superclass method in the subclass method
05:00
<@ToxicFrog>
Explicitly
05:00
<@ToxicFrog>
Using the 'super' keyword, I think
05:00
< celticminstrel>
So, just 'super.method()'? Just like Java?
05:01
<@ToxicFrog>
I don't know, I don't use Python!
05:01
<@ToxicFrog>
Look it up.
05:01
< celticminstrel>
Okay, okay.
05:08
< celticminstrel>
Uglier.
05:26
< celticminstrel>
Suppose channels A and C require passwords, but channel B does not. Would 'JOIN #A,#B,#C password1,*,password2' successfully join all three?
05:26
< celticminstrel>
Is that the right way to do this?
05:30
<@Vornicus>
I don't think there's a right way to do it
05:31
< celticminstrel>
Oh?
05:31
< celticminstrel>
So, not actually possible?
05:33
<@Vornicus>
Well, technically, the "right" way is to send a join with a single channel and password. I think.
05:36
< celticminstrel>
Well, the above format apparently should work if all the channels require passwords; it's just mixing them that I'm unsure of.
05:47
< Namegduf>
celticminstrel: You would probably omit passwords for channels that didn't need them, entirely
05:48
< Namegduf>
If that doesn't work, place channels needing them at the start of the lit
05:48
< celticminstrel>
Alright.
05:48
< celticminstrel>
That's easily done here.
05:49 celticminstrel [celticminstre@Nightstar-f8b608eb.cable.rogers.com] has quit [[NS] Quit: *whistles* Did you hear something?]
05:51
< Namegduf>
And no, the right way in IRC is not to send multitarget commands as separate commands; aside being bandwidth inefficient, that makes fakelag implementations angry at you.
05:51
< Namegduf>
(Which a lot of IRCDs have)
07:02
<@Kazriko>
Vornicus, actually, the way I do it is to move all the channels with passwords up first...
07:02
<@Kazriko>
ah, someone else had that solution already. heh
07:04 Derakon[AFK] is now known as Derakon
07:43 You're now known as TheWatcher
08:25 AnnoDomini [annodomini@Nightstar-d8256a85.adsl.tpnet.pl] has joined #code
08:25 mode/#code [+o AnnoDomini] by Reiver
08:37 You're now known as TheWatcher[afk]
08:37 Vornicus is now known as Vornicus-Latens
10:11 gnolam [lenin@Nightstar-38637aa0.priv.bahnhof.se] has joined #code
10:57 Tarinaky [Tarinaky@Nightstar-1c1774a2.adsl.virginmedia.net] has quit [Ping timeout: 121 seconds]
11:10 Tarinaky [Tarinaky@Nightstar-e48aa38f.adsl.virginmedia.net] has joined #code
11:44 Serah [Z@3A600C.A966FF.5BF32D.8E7ABA] has joined #code
12:05 AnnoDomini [annodomini@Nightstar-d8256a85.adsl.tpnet.pl] has quit [Ping timeout: 121 seconds]
12:11 AnnoDomini [annodomini@Nightstar-d8256a85.adsl.tpnet.pl] has joined #code
12:11 mode/#code [+o AnnoDomini] by Reiver
12:53 Rhamphoryncus [rhamph@Nightstar-bbc709c4.abhsia.telus.net] has quit [Client exited]
14:32 Thaqui [Thaqui@27B34E.D54D49.F53FA1.6A113C] has quit [Client closed the connection]
14:42 Serah [Z@3A600C.A966FF.5BF32D.8E7ABA] has quit [Ping timeout: 121 seconds]
14:56 celticminstrel [celticminstre@Nightstar-f8b608eb.cable.rogers.com] has joined #code
15:22 Attilla [Attilla@Nightstar-6323b909.threembb.co.uk] has joined #code
15:22 mode/#code [+o Attilla] by Reiver
15:30 Serah [Z@26ECB6.A4B64C.298B52.D80DA0] has joined #code
15:56 Orth [orthianz@Nightstar-8a5cef62.xnet.co.nz] has joined #code
15:57
< celticminstrel>
Okay, so there are plenty of replies to indicate that a PRIVMSG or NOTICE was unsuccessful, but how do I detect a successful one? Most other commands seem to echo on success, but not those ones...
15:58 cpux [Moo@Nightstar-20a84089.dyn.optonline.net] has quit [Ping timeout: 121 seconds]
15:59 Reiv[Graduate] [orthianz@Nightstar-bb68d970.xnet.co.nz] has quit [Ping timeout: 121 seconds]
16:11 cpux [Moo@Nightstar-20a84089.dyn.optonline.net] has joined #code
16:31 PinkFreud is now known as PinkCoffeeZombie
18:09 AbuDhabi [annodomini@Nightstar-848d9477.adsl.tpnet.pl] has joined #code
18:10 AnnoDomini [annodomini@Nightstar-d8256a85.adsl.tpnet.pl] has quit [Ping timeout: 121 seconds]
18:48
<@ToxicFrog>
celticminstrel: there is no reply. If it doesn't yell at you to indicate failure, it succeeded.
18:48
<@ToxicFrog>
I highly recommend using telnet, or your IRC client's rawlog feature, to experiment, btw
19:01
< celticminstrel>
I have been, actually.
19:01
< celticminstrel>
That's how I discovered the other commands echo on success.
19:01
< celticminstrel>
(for example)
19:02
< Namegduf>
Most "don't" strictly speaking echo on success
19:02
< Namegduf>
But give output back to you because they send it to the whole channel.
19:03
< Namegduf>
PRIVMSG/NOTICE are odd in that respect in that they still don't, even in channels.
19:04
< celticminstrel>
At least one command said in the specificatin that it echoes on success.
19:04
< celticminstrel>
^specification
19:04
< celticminstrel>
I think it was JOIN
19:05
< celticminstrel>
Though, this is RFC2812, not RFC1459; I'm not sure how accurate that would be...
19:05
< Namegduf>
That's correct, although implemented the way I said and you can get unsolicited JOIN messages.
19:05
< celticminstrel>
?
19:06
< celticminstrel>
You get JOIN messages whenever someone joins, yes...
19:06
< Namegduf>
Yeah, I meant one with you in it.
19:06
< Namegduf>
This indicates that you're being joined to something without asking, which can be the case for join on connect, serverside AJOIN, and in some IRCDs SAJOIN/FORCEJOIN.
19:07
< celticminstrel>
Ah...
19:08
< celticminstrel>
So, regarding the PRIVMSG/NOTICE thing, is the best way to check that the message will be successful before going ahead and logging it?
19:08
< celticminstrel>
That is, check for anything that would cause an error reply.
19:08
< Namegduf>
Assume success, add an additional log entry if you fail.
19:08
< Namegduf>
That's what I'd suggest and is how most client UIs do stuff, if they handle it.
19:09
< celticminstrel>
Hm, okay.
19:09
< celticminstrel>
...'a' mode would not allow you to delete a previous line, would it?
19:09
< Namegduf>
You can't really detect +M, +m, +b m:foo!*@* (on Insp), +q foo!*@* (same on Chary)
19:09
< Namegduf>
"delete a previous line"?
19:09
< celticminstrel>
In the file.
19:10
< celticminstrel>
That is, log the message, then delete if an error is returned.
19:11
< Namegduf>
Ah, wouldn't know if there was a way to do it. "append" mode wouldn't allow that generally, though.
19:11
< celticminstrel>
As I thought. I guess I'll do the "assume success, log error" method, then.
19:12
< Namegduf>
If it helps, netsplits can eat arbitrary messages with no feedback anyway.
19:12
< Namegduf>
It's the reason they can't be made to heal transparently easily.
19:12
< celticminstrel>
Not sure how that could help...
19:13
< Namegduf>
I was meaning "you're always doomed to log as successful potentially lost messages"
19:13
< Namegduf>
"So it might save you time worrying about avoiding that" :P
19:14
< celticminstrel>
Ah.
20:38 Rhamphoryncus [rhamph@Nightstar-bbc709c4.abhsia.telus.net] has joined #code
20:40 Vornicus-Latens is now known as Vornicus
20:56 You're now known as TheWatcher
20:57 * ToxicFrog pushes some documentation to github
20:57
<@ToxicFrog>
In writing this, and looking at the xchat-python docs for inspiration, I realized just how much further this implementation has to go :/
21:02
<@ToxicFrog>
Stuff that it still needs, offhand: /lua command; lua interactive shell; automatic loading of modules on startup
21:03 aoanla [AndChat@Nightstar-4aa0fdf5.range86-147.btcentralplus.com] has joined #code
21:23 aoanla [AndChat@Nightstar-4aa0fdf5.range86-147.btcentralplus.com] has quit [[NS] Quit: ]
22:21 Kazriko [kaz@Nightstar-e09690fa.client.bresnan.net] has quit [Ping timeout: 121 seconds]
22:21 Kazriko [kaz@Nightstar-e09690fa.client.bresnan.net] has joined #code
22:21 mode/#code [+o Kazriko] by Reiver
23:02 Rhamphoryncus [rhamph@Nightstar-bbc709c4.abhsia.telus.net] has quit [Client exited]
--- Log closed Sun May 30 00:00:18 2010
code logs -> 2010 -> Sat, 29 May 2010< code.20100528.log - code.20100530.log >