All times are UTC.
00:41:37 <-- Ornthalas has quit (Quit: KTHXBYE) 01:14:09 <-- hicham has quit (Client exited) 01:18:19 <-- GeekShadow has quit (Quit: The cake is a lie !) 01:28:48 --> micahg has joined #instantbird 02:35:37 --> mepine has joined #instantbird 02:59:23 <-- mepine has quit (Quit: mepine) 03:20:14 --> mepine has joined #instantbird 04:12:19 <-- rikki has left #instantbird () 04:12:41 --> rikki has joined #instantbird 05:10:29 --> DGMurdockIII has joined #instantbird 07:55:39 <-- DGMurdockIII has quit (Quit: get satisfied! :: www.unitedservers.de ««« (Gamers.IRC) »»» gamersirc.net ::) 10:54:25 <-- flo has quit (Quit: Instantbird 0.3a1pre) 10:54:43 --> flo has joined #instantbird 10:54:43 * ChanServ sets mode +qo flo flo 11:06:10 --> Ornthalas has joined #instantbird 11:30:43 <-- Jan has quit (Ping timeout) 11:52:27 --> IRCMonkey56526 has joined #instantbird 11:53:29 * IRCMonkey56526 is now known as Jan 11:54:29 * Jan is now known as IRCMonkey11198 11:56:03 * IRCMonkey11198 is now known as Jan 12:52:16 --> GeekShadow has joined #instantbird 13:24:16 --> hicham has joined #instantbird 14:07:47 <-- mepine has quit (Quit: é¨ç·£ä¹) 14:17:45 --> Andrey has joined #instantbird 14:28:30 <instantbot> email@example.com added attachment 452 to bug 598. 14:28:31 <instantbot> firstname.lastname@example.org requested review from the wind for attachment 452 on bug 598. 14:28:33 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=598 nor, --, ---, florian, ASSI, Twitter support 14:29:02 <flo> whoever is interested in my twitter work should feel free to review and comment that patch :). 14:48:02 --> clokep has joined #instantbird 14:48:02 * ChanServ sets mode +h clokep 15:02:30 --> tymerkaev has joined #instantbird 15:14:55 <clokep> flo: Reviewing your Twitter code. ;) 15:15:10 <clokep> Nice API. :) 15:25:05 <-- GeekShadow has quit (Quit: The cake is a lie !) 15:43:25 --> GeekShadow has joined #instantbird 15:50:09 <-- clokep has quit (Ping timeout) 16:01:52 <-- Andrey has quit (Quit: ) 16:08:26 --> clokep has joined #instantbird 16:08:26 * ChanServ sets mode +h clokep 16:37:35 <flo> clokep: thanks :) 16:38:26 <clokep> You're welcome. 16:38:37 <clokep> I didn't run it, just read over it. 16:39:49 <-- flo has quit (Input/output error) 16:41:58 <-- clokep has quit (Quit: Instantbird 0.3a1pre) 16:42:07 --> clokep has joined #instantbird 16:42:07 * ChanServ sets mode +h clokep 16:44:09 --> flo has joined #instantbird 16:44:09 * ChanServ sets mode +qo flo flo 16:44:34 <flo> stupid power outages... :( 16:45:08 <clokep> :-\ Snow? 16:45:40 <clokep> Yay, finally able to verify my logger patch haha. :) 16:46:00 <flo> it's not snowing right now, but the temperature is <0Â°C and there's still some snow outside 16:46:37 <flo> ah, we will have a bug in the verified state? :-D 16:48:13 <-- tymerkaev has quit (Ping timeout) 16:56:35 <clokep> Hmm? No. It works fine. :) 17:01:10 --> Mic has joined #instantbird 17:01:11 * ChanServ sets mode +h Mic 17:01:17 <flo> clokep: the "Status" drop down of bugs has a "verified" status, for when someone has checked a build that includes the commited fix, and verified it actually works 17:01:41 <clokep> Ah, right. But I thought it's bad form to "verify" your own fix? 17:01:57 <flo> ah, maybe :) 17:03:15 <flo> but if you comment there "I've just checked that it works", and someone else changes the status to verified and comments "verified per comment <n-1>", it's spammy ;) 17:06:25 <clokep> True. :) 17:31:21 <clokep> flo: Can we just poll Twitter every x-seconds? Or use the streaming API? 17:31:34 <clokep> (To get tweets after the account is connected.) 17:56:44 <-- hicham has quit (Client exited) 18:00:55 --> hicham has joined #instantbird 18:08:59 <-- hicham has left #instantbird () 18:16:37 --> DGMurdockIII has joined #instantbird 18:44:22 --> tymerkaev has joined #instantbird 18:50:32 <-- skeledrew has quit (Quit: Instantbird 0.3a1pre) 18:52:34 --> skeledrew has joined #instantbird 18:53:33 * skeledrew is surprised that there's an automatic update for the nightly 18:54:00 <skeledrew> partial update failed though, so now it's trying a full update... 18:54:27 <clokep> skeledrew: There should be auto-updates *nightly*! ;) 18:55:05 <skeledrew> lol 18:55:07 <skeledrew> yeah 19:01:19 <DGMurdockIII> the partial update fails for me alot 19:02:35 <clokep> It mostly works for me, every once in a while it fails. Today's worked though from the last build, which was like a week ago. 19:02:53 <DGMurdockIII> correct 19:04:47 <DGMurdockIII> the update fails for mr more becse when it restart instantbird it thinks instantbird was open and could not start installing the update so i have to close the program then it installes 19:15:26 <-- sabret00the has quit (Ping timeout) 19:15:30 <-- tymerkaev has quit (Ping timeout) 19:25:21 <-- clokep has quit (Ping timeout) 19:26:06 <Mic> DGMurdockIII: I think we had this problem before 19:26:23 <DGMurdockIII> yeah 19:26:29 <DGMurdockIII> but if never whent away 19:28:05 <Mic> Can you file a bug for it? 19:28:21 <Mic> Merry Christmas, by the way :) 19:28:31 <DGMurdockIII> i thnk i have 19:31:03 <-- Jan has quit (Connection reset by peer) 19:31:54 <DGMurdockIII> https://bugzilla.instantbird.org/show_bug.cgi?id=478 19:31:58 <instantbot> Bug 478 nor, --, ---, nobody, NEW, more info on update link broken 19:32:11 <DGMurdockIII> i havent but i will file one 19:33:17 <Mic> Thanks :) 19:33:58 --> Jan has joined #instantbird 19:35:47 <DGMurdockIII> 2(Mic2): where shold i file it in Instantbird (UI), purplexpcom or Websites 19:35:47 <DGMurdockIII> 2(micahg2): where shold i file it in Instantbird (UI), purplexpcom or Websites 19:35:47 <DGMurdockIII> 2(Mic|away2): where shold i file it in Instantbird (UI), purplexpcom or Websites 19:35:53 <DGMurdockIII> sorry 19:40:11 --> clokep has joined #instantbird 19:40:11 * ChanServ sets mode +h clokep 19:41:29 <clokep> DGMurdockIII: Instantbird UI most likely. 19:41:43 <DGMurdockIII> mic, could you help look at this add tell me what you think 19:42:11 <DGMurdockIII> http://pastebin.com/bvDQZCgg 19:44:52 <instantbot> New Websites - Updates bug 641 filed by email@example.com. 19:44:55 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=641 cri, --, ---, nobody, UNCO, instantbird Automated Update broken 19:57:11 <Mic> The update works only after restarting the second time? 20:00:07 <skeledrew> hmm 20:00:15 <-- skeledrew has quit (Quit: Instantbird 0.3a1pre) 20:01:11 --> skeledrew has joined #instantbird 20:01:41 <skeledrew> yep. 2 restarts 20:03:17 <Mic> Skeledrew: you can confirm that? 20:03:37 <Mic> Which OS are you two using? 20:04:04 <clokep> I've had this happen to me, but it's random. 20:04:36 <skeledrew> XP 20:06:12 <skeledrew> the first restart was with the partial update, which failed. the second was for the full update 20:10:45 * clokep just successfully sent formatting. :) 20:13:07 --> sabret00the has joined #instantbird 20:16:51 <-- sabret00the has quit (Ping timeout) 20:30:10 <instantbot> firstname.lastname@example.org added attachment 453 to bug 364. 20:30:11 <instantbot> email@example.com requested review from florian@instantbird .org for attachment 453 on bug 364. 20:30:13 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=364 enh, --, ---, benediktp, ASSI, Show in the Themes preference pane which theme are disabled 20:32:08 <Mic> Forgot one thing again.. it sucks having to try on a unpacked copy of Instantbird and having to mvoe the changes to Hg later :S 20:35:13 <instantbot> firstname.lastname@example.org added attachment 454 to bug 364. 20:35:14 <instantbot> email@example.com cancelled review?(florian@instantbird .org) for attachment 453 on bug 364. 20:35:16 <instantbot> firstname.lastname@example.org requested review from florian@instantbird .org for attachment 454 on bug 364. 20:35:17 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=364 enh, --, ---, benediktp, ASSI, Show in the Themes preference pane which theme are disabled 20:36:19 <Mic> bye 20:36:24 <-- Mic has left #instantbird () 20:38:32 --> sabret00the has joined #instantbird 20:54:05 --> rikki1 has joined #instantbird 20:54:12 <-- rikki has quit (Connection reset by peer) 21:03:19 <-- micahg has quit (Quit: Leaving.) 21:03:23 --> micahg has joined #instantbird 21:23:50 --> Mic has joined #instantbird 21:23:51 * ChanServ sets mode +h Mic 21:28:10 <DGMurdockIII> mic, if i get the message saying the updae could not be fun becse it think instantbird is still open all i do is close instantbird and start it and will usually install the update 21:28:41 <clokep> It happens if the process doesn't close fast enough I think? Idk why it's happenign though. 21:30:20 <DGMurdockIII> sometime i waite a while when i click check for update to click restart instantbitrd on the update window 21:31:12 <DGMurdockIII> clokep, if you could could could you add the comment to my bug report to the problem you expernese woth partal updates 21:31:40 <DGMurdockIII> clokep, windows 7 64 bit 21:31:52 <clokep> I haven't experienced problems in months -- and at the time I was experiencing them across all Mozilla apps (Tb, Fx, Ib). 21:31:59 <clokep> So...I think it's a different issue. 21:32:18 <DGMurdockIII> becse i also get the problem you saying with it it happend to me recently last week 21:32:23 * DGMurdockIII slaps skeledrew around a bit with a large trout 21:32:56 <Mic> There's no trout-add-on yet 21:32:58 <DGMurdockIII> the partal update problem but the other one happend just today when i updated 21:34:49 <DGMurdockIII> skeledrew, could u please comment with the problem on my bug repport https://bugzilla.instantbird.org/show_bug.cgi?id=641 21:34:53 <instantbot> Bug 641 cri, --, ---, nobody, UNCO, instantbird Automated Update broken 21:35:15 <DGMurdockIII> mirc 21:45:13 <skeledrew> DGMurdockIII: k 21:45:51 <Mic> good night 21:46:05 <clokep> 'night Mic. 21:47:22 <skeledrew> night 21:48:09 <skeledrew> it's the first i'm having this issue though (and the first IB has ever autoupdated) 21:48:35 <skeledrew> it could've been a fluke 21:49:19 <-- Mic has quit (Quit: Instantbird 0.3a1pre) 21:49:55 <skeledrew> clokep: in fixing the logger, do you think it's better to insert the new date into the current log file, or close the current and open a new one? both have their pros and cons... 21:51:16 <clokep> skeledrew: I'm not sure, making a new file is bad because it would split a conversation over two files, while it probably maintains "backwards compatibility" with libpurple logs. 21:51:20 <clokep> Either should work OK. 21:51:28 <clokep> I personally probably wouldn't want my file split. 21:51:35 <clokep> Is there a bug about that that you're working ON? 21:51:43 <skeledrew> if i write the new date to the log, the file name would still only have the date it was created. but creating a new file could split a convo... 21:51:49 <skeledrew> k 21:51:55 <skeledrew> umm. not sure 21:52:05 <skeledrew> i think i filed a report, but i don't remember 21:53:31 <clokep> If you log into Bugzilla, there's a "My Bugs" link in the bottom left hwich will show you stuff you've reproted. ;) 21:53:42 <skeledrew> hmm 21:54:02 * skeledrew doesn't even remember the password for the account... 21:54:09 <clokep> :( 21:54:16 <clokep> I just leave myself logged in all the time haha. 21:55:24 <skeledrew> Fx remembered it for me :) 21:56:35 <skeledrew> bug 476 21:56:35 <skeledrew> :) 21:56:38 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=476 nor, --, ---, nobody, UNCO, Date change in open conversations not logged. 21:57:39 <clokep> OK, I was just curious. :) 21:57:59 <clokep> I confirmed it for you btw. 21:58:04 <skeledrew> k 21:58:06 <skeledrew> thx 21:58:11 <flo> skeledrew: so it's the very first nightly update that failed for you? 21:58:20 <clokep> I would write any questions about stuff like that to flo. ;) 21:58:35 <skeledrew> flo: yep 21:58:50 <flo> if your original nightly was a zip build that you unzipped, then it's a known issue 21:58:54 <skeledrew> but it's the first IB ever autoupdated for me anyway 21:58:58 <flo> and the following updates should work 21:59:06 <skeledrew> oh 21:59:09 <skeledrew> it was a zip 21:59:16 <flo> if your original build was using the installer, it's something I don't know 21:59:30 <flo> partial updates never work with .zip builds. 21:59:41 <skeledrew> i don't like installs :) 21:59:46 <flo> as soon as it has updated itself once, you should not see the issue anymore 22:00:04 <flo> skeledrew: neither do I, but windows user tend to get lost when they don't have an installer to waste their time ;) 22:00:06 <skeledrew> flo: and if i change the folder location or something? 22:00:15 <flo> skeledrew: doesn't matter :) 22:00:17 <skeledrew> yep 22:00:43 <skeledrew> k then :) 22:01:05 <skeledrew> flo: how about that logger bug? what would you prefer? 22:01:15 <-- sabret00the has quit (Ping timeout) 22:01:21 <flo> skeledrew: my answer may disappoint you ;) 22:01:30 <skeledrew> ? 22:01:50 <skeledrew> i kinda prefer the new file... 22:01:59 <flo> 1. Fixing the old plain text log files is in my opinion mostly a waste of time as we know we should rewrite them. 22:02:14 <flo> 2. Knowing when the day changed is a real issue, even when logs are not enabled 22:02:47 <skeledrew> just check the time when each message is sent or something ;) 22:03:47 <skeledrew> i think this fix can be easily carried over to the new format though 22:04:08 <flo> knowing that we will replace the storage format, I would rather not add anything that wouldn't be compatible with the current format (it would force us to write some more code when doing the code to import the old logs to the new format later) 22:04:28 <skeledrew> it's just REALLY getting to me... 22:04:29 <skeledrew> hmm 22:04:32 <flo> skeledrew: when I say "new format", I mean logs stored in SQLite 22:04:42 <skeledrew> oh 22:04:50 <skeledrew> so that was the decision ... 22:05:03 <skeledrew> no XML logs :( 22:05:09 <clokep> flo: Wouldn't a better thing to do jus thave a system message on all conversations when the date changes that says "It is now 12/27/2010" or something? 22:05:12 <flo> XML is an exchange format, not a storage format 22:05:23 <flo> we will be able to export into XML pretty easily 22:05:28 <skeledrew> clokep: that could work 22:05:31 <skeledrew> flo: ok 22:05:50 <flo> clokep: This is a feature I want, which is related to "2." in what I said and as nothing to do with the log storage :). 22:06:21 <clokep> Maybe we can convert the bug and skeledrew could look into that? 22:06:54 <flo> clokep: that would be a welcom enhancement, but I don't think it fixes skeledrew's annoyance :-/ 22:07:01 <skeledrew> convert? 22:07:11 <skeledrew> clokep: ^ 22:07:14 <clokep> Eh, change the description and hijack it. ;) 22:07:25 <skeledrew> oh 22:07:35 <skeledrew> sure 22:07:38 <clokep> I meant the bug in bugzilla. 22:07:46 <clokep> Would that fix your annoyance skeledrew, or not really? 22:08:02 <skeledrew> but i'm not sure what's going on there anyway 22:08:09 <flo> skeledrew: so basically, you were proposing 2 possible workarounds, which don't fix the real issue, but release the pain, right? :) 22:08:10 <skeledrew> clokep: not really 22:08:11 <skeledrew> lol 22:08:19 <flo> what are the pros and cons of each exactly? :) 22:08:22 <skeledrew> flo: pretty much 22:09:58 <flo> I think I would like to split the files actually. Would just like to ensure we mitigate (eliminate?) the side cases where it would not be wanted... 22:10:01 <skeledrew> flo: if i just write the new date to the log, the file name would still only have the date it was created. but creating a new file could split a convo in progress (clokep doesn't like that)... 22:10:31 <flo> skeledrew: so writing the new date in the log, well, just write it as a system message in the conversation 22:10:49 <flo> but that doesn't make it any easier to navigate to in the current (poor) log viewer 22:11:21 <skeledrew> flo: sure, but as i said, we'd be stuck with the initial file name of the first date 22:11:50 <skeledrew> yup. users of the viewer would prob be confused 22:11:53 <flo> yes. That's useful mostly for when you look at the conversation before closing it's tab 22:12:07 <flo> *its 22:12:53 <flo> clokep: do you know in which cases splitting the log file is annoying? 22:13:01 <skeledrew> flo: but the only time i close convo tabs is if i really run out of space or i'm restarting or something 22:13:12 <skeledrew> that's the initial causer of the issue 22:13:19 <flo> I suspect we could decide to split it if the day changes and the conversation/log started more than 6 hours ago, or something... 22:13:41 <skeledrew> flo: if you're in the middle of a convo 22:13:55 <flo> what's a good way to know that? 22:14:06 <skeledrew> hmm 22:14:07 --> sabret00the has joined #instantbird 22:14:31 <skeledrew> when you check the date, you can also check the time of the last message 22:15:05 <clokep> 6 hours between the last message and this message as opposed to from the firs tmessage. 22:15:10 <flo> skeledrew: if that's an IRC room (which is a place where you probably really want to split the file), the most recent message will be very recent if it's an active room 22:15:17 <skeledrew> so you may only split after a convo is seen as complete 22:15:47 <skeledrew> flo: we could also detect if it's a chat room... 22:15:54 <skeledrew> (this is getting complex) 22:16:03 <flo> clokep: in the "new format", I think it will be something like "20 minutes since the last message", but it will be mostly irrelevant as the limit between stored conversation will be mostly invisible. 22:16:21 <flo> skeledrew: detecting chat rooms was my first idea ;) 22:16:34 <skeledrew> k :) 22:16:51 <clokep> flo: Is there a way to say "hey, I haven't a DOM element is there any REAL content in this?"? 22:16:56 <clokep> (I.e. text content.) 22:17:22 <flo> what do you mean by "I haven't a DOM element"? 22:17:47 <clokep> Oops, typo: "I have a" 22:18:12 <flo> element.textContent ? 22:18:31 <flo> trim the result maybe :) 22:18:51 <clokep> Hmm..OK. :) 22:19:14 <flo> what is this for? Formatted outgoing messages? 22:19:43 <skeledrew> clokep: flo: also, for non-chat convos, a system message could announce the date change if you're in the middle of a convo. then a new file would be created after the convo is complete ie. a new message is received x minutes after the last 22:19:58 <clokep> flo: I'm sending blank messages right now because it adds a line break, which gets sent. :( 22:20:01 <skeledrew> so both would be in effect 22:23:33 <instantbot> New Websites - bugzilla.instantbird.org bug 642 filed by email@example.com. 22:23:36 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=642 nor, --, ---, raynaudquentin, NEW, interdiff doesn't work on bugzilla 22:24:03 <flo> skeledrew: I think you can take the system message thing separately from the split logs thing. 22:24:27 <flo> whatever we decide for log splitting, displaying the date change in the conversation as a system message is probably a good idea 22:24:56 <skeledrew> yeah. it could probably tell someone that it's time for bed... 22:25:04 <flo> :-D 22:25:18 <skeledrew> lol 22:27:08 <skeledrew> and it'd probably be better to only give the system message when a message is sent, since we don't want the overhead of polling for the date change 22:27:55 <flo> yes, add it only when a new message is displayed and it's not the same day as the previous one 22:27:58 <skeledrew> besides, the person will only know the date changed if they're chatting... 22:28:24 <flo> so that we don't seem to display 10 "date change" system messages in a raw if the user has been away for 10days :) 22:28:46 <skeledrew> lol 22:29:05 <skeledrew> the current date would be stored in a global variable 22:29:50 <skeledrew> when there's a mismatch, the action is triggered 22:30:39 <flo> in a what?!? :-P 22:31:15 <skeledrew> flo: you don't like global vars? 22:31:25 <clokep> flo: You don't know too much about editor, right? I'm trying to get it to only display <br> when you do shift+enter... 22:31:26 <flo> no 22:31:43 <skeledrew> k :) 22:32:10 <flo> clokep: I know most people who have touched it tend to fear messing with it again ;) 22:32:30 <skeledrew> you'd prefer a separate date for each convo??? 22:32:31 <clokep> Honestly so far it s really not too bed. 22:32:45 <clokep> Just crappy documentation. 22:32:54 <clokep> So I need to try things and then figure it out. 22:33:37 <skeledrew> flo: a bool is probably needed too for splitting when a convo is detected to have ended some time into the new date... 22:33:37 <flo> skeledrew: the date is already in each message. You can just keep the last message of each conversation. 22:34:04 <skeledrew> that could be alot of convos... 22:34:37 <skeledrew> before my last restart, i had upwards of 15 open. and sometimes it's worse 22:35:35 <clokep> flo: Blocked on bug 300! ;) 22:35:38 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=300 enh, --, ---, nobody, NEW, Add an array of all the displayed messages 22:35:57 <skeledrew> hmm 22:36:08 <flo> skeledrew: I'm not sure of what you are trying to day. How much memory do you think it represent to keep one value per conversation if you have 15 of them? 22:36:12 <flo> s/day/say/ 22:36:27 <flo> clokep: certainly not. We need the *last* message. Not all of them. :) 22:36:54 <skeledrew> more than one global var would take :p 22:38:45 <flo> skeledrew: the discussion on this point we have just had is most likely currently taking more RAM than those variables would take in your whole life of usage of Instantbird. 22:39:08 <skeledrew> hmm 22:39:31 <skeledrew> guess i should recycle my window then :) 22:39:44 <skeledrew> that brings me to another issue 22:40:12 <skeledrew> i need a way to clean a convo without actually closing it... 22:40:23 <flo> if you are concerned with RAM usage when keeping the application opened for extended periods of time, you want bug 301 22:40:26 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=301 enh, --, ---, nobody, NEW, Remove old messages 22:40:36 <skeledrew> maybe just keep the last 10 messages or something 22:40:56 <skeledrew> yup. that bug IS handy 22:40:56 <flo> what's the use case? 22:41:28 <skeledrew> i dislike having old convos remain with the new ones 22:41:42 <flo> close them :) 22:41:47 <skeledrew> esp when they're over 2 days 22:42:46 <skeledrew> i don't wanna. i just want a way to consume the older ones in the same tab when it gets to a certain length or something 22:43:08 <skeledrew> as you should've figured by now, i have a tab closing phobia 22:43:20 <skeledrew> you should see my Firefox :) 22:43:24 <flo> how many tabs do you have in your browser? 22:43:31 <flo> you seem like me :-D 22:43:43 <skeledrew> over 30 at last count 22:43:50 <flo> I used to have around 300+ tabs in my Firefox until I wrote an add-on to close them for me as soon as I have forgotten about them 22:44:31 <skeledrew> yeah. but i go back to mine even after days, so i still need them open. i don't forget them 22:44:38 <flo> hmm, maybe only between 180 and 250, not 300+ 22:44:57 <skeledrew> yikes! still a crazy amount 22:45:06 <flo> you may like my add-on 22:45:19 <skeledrew> how many windows do you keep them in? 22:45:30 <flo> 1 22:45:34 <flo> https://addons.mozilla.org/en-US/firefox/addon/7565/ 22:45:40 <skeledrew> !!! 22:45:43 <skeledrew> O.O 22:46:04 <skeledrew> does your addon save a link or something to the tabs it closes? 22:46:48 <skeledrew> i don't even want to see the size of those tabs 22:47:05 <clokep> There's a limit to the size the tabs can get. 22:47:08 <clokep> The minimum size. 22:47:14 <flo> firefox has a "recently closed tabs" menu in the History menu 22:47:32 <skeledrew> ah yes 22:48:05 <skeledrew> it does keep the URL history in it too right? 22:48:36 <flo> are you familiar with the location bar of Firefox, where the history is searched as soon as you type something? 22:49:03 <skeledrew> sure 22:49:05 <flo> I wonder how users can come up with comments like "It is great that you are developing this addon as an experimental but you still need to give people something they can actually use functionally." 22:49:14 --> rikki has joined #instantbird 22:49:24 <-- rikki1 has quit (Connection reset by peer) 22:49:24 <flo> I need to what?? 22:50:10 <skeledrew> but i meant the history of the tabs themselves (back/forward) 22:50:27 <flo> I don't know 22:50:33 <flo> that rarely matters though 22:50:34 <skeledrew> k 22:50:48 <skeledrew> i'm a rare case :) 22:51:01 <flo> the "recently closed tabs" list is there do comfort you, but you won't actually be using it 22:51:31 <skeledrew> i use it. alot 22:51:47 <flo> skeledrew: that part of the add-on description is important: "Unread tabs (displayed in red) will not be closed automatically. Additionally, it is possible to protect a tab by making a double click on it. When a tab is protected, its title is displayed underlined. Another double click will remove the protection." 22:51:52 <skeledrew> maybe we could put it in IB :) 22:53:27 <skeledrew> that's the thing. unless i set autorefresh (which would negate the add-on's functionality), many of my tabs have been read. partially 22:53:57 <skeledrew> or are there for further followup 22:55:52 <clokep> flo: How can I view all of somethings interfaces? 22:58:40 <flo> clokep: "somethings interfaces"? 22:59:06 <clokep> Like you can QueryInterface an object? I wanted to just list all the interfaces available. 22:59:09 <clokep> But I figured it out. :) Thanks. 23:01:30 <flo> you can only do it if the object implements nsIClassInfo 23:01:41 <flo> in which case calling QueryInterface in JS is useless 23:01:49 <flo> (it's done automatically) 23:04:47 <clokep> Oh? Interesting. 23:05:33 <clokep> Bah apparently I need to do http://www.mozilla.org/editor/writing-rules.html which isn't scriptable. 23:06:18 <flo> an article written by someone @netscape.com? 23:07:31 <clokep> It's editor code. ;) 23:09:02 <clokep> Maybe I should just ask in #developers. 23:09:11 <flo> you can try :) 23:10:38 <clokep> Not right now -- need to cook dinner in a few minutes. ;) Don't want to get into a debate about editor haha. 23:13:51 * flo can understand that 23:14:35 <clokep> I'm slightly afraid they'll be like "Oh, you want to know about editor? OK, you own it." ;) 23:15:00 <flo> ahah 23:15:27 <flo> I think they only do that if they have reviewed a few of your patches for other areas before that ;) 23:21:18 <instantbot> firstname.lastname@example.org granted review for attachment 454 on bug 364. 23:21:20 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=364 enh, --, ---, benediktp, ASSI, Show in the Themes preference pane which theme are disabled 23:25:20 <instantbot> email@example.com added attachment 455 to bug 364. 23:25:24 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=364 enh, --, ---, benediktp, ASSI, Show in the Themes preference pane which theme are disabled 23:27:52 <instantbot> firstname.lastname@example.org set the Resolution field on bug 364 to FIXED. 23:27:56 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=364 enh, --, 0.3a1, benediktp, RESO FIXED, Show in the Themes preference pane which theme are disabled 23:28:57 <instantbot> Check-in: http://hg.instantbird.org/instantbird/rev/894316e9bb37 - Benedikt P. - Bug 364 - Show in the Themes preference pane which theme are disabled, r=fqueze. 23:37:40 <-- GeekShadow has quit (Connection reset by peer) 23:40:55 --> GeekShadow has joined #instantbird 23:50:24 <instantbot> New purplexpcom - Debug bug 643 filed by email@example.com. 23:50:27 <instantbot> Bug https://bugzilla.instantbird.org/show_bug.cgi?id=643 min, --, ---, nobody, NEW, ASSERTION: purple_savedstatus_get_current should never return NULL