Recently, I've been having problems with an irssi script, so I turned on debugging (and later added some more debugging around the problem spot) with the output going to another window.
The problem is that tracking when did the problem occur....why...and how to deal with it. And, later what happens if I just ignore it.
Anyways...the problem is I'm not watching the output constantly, so hours may have gone by before I notice
that the problem had occurred.
I suppose I could've customized the debug output to focus in on where I suspected the problem to be, but I didn't want to make that big of change to it.
I have auto_log on...but that only logs channel/query windows....so not the window that the debug output is going to. Hmm, just noticed that channel/query logging includes twirssi....guess I found another way to search my twitter history
So, I had mainly been searching around "irssi search window".... "search" turns out to be one of those annoying terms to use in a search. And, "window" isn't really that much better. Good thing, the word "home" was not something relevant to this search.
Wasn't until I started other terms with irssi that I found something that would fulfill my needs. Save wasn't something I had thought of, though I had tried looking for how to log this window where auto_log wasn't. But, I guess I wasn't coming up with the right terms to narrow in on it. Or that I'm using Bing instead of Google.
Eventually, I found this: irssi, logging a chat w/o logging enabled
Yea, sorry, couldn't find a better title.
This is probably the shortest howto in this forum so here it goes.
Last night I had a conversation with someone. I usually IRC from a remote box so I don't log anything because, well, I'm paranoid.
Thing is that when I woke up this morning I really wanted to have the conversation saved on my drive. So, if you're lazy like me and don't feel like scrolling back, copying and pasting as you go, here's what I did:
First, you enable logging on the window you want to save the buffer from.
/window log on
And then you use /lastlog to scroll the entire contents of the buffer from give window.
Note that if the buffer is bigger than 1000 lines you'll need to use /lastlog with the '-force' option like so:
Now that we've first enabled logging on this window, all the output from the lastlog command will be saved to a file stored by default in your homedir.
Hope someone finds this guide useful some day.
P.S.: Obviously this won't work if the window you want to use this guide on has been closed.
Years later, somebody posts at 2011-05-14 05:25:22 that they search for "irssi save buffer" in Google and its the 5th hit... So, I tried the search in Bing, and there it is....the 5th hit, highlighting the text of from this posting. Wonder if the post would've come up in Google if somebody hadn't said what terms to use in the posting?
Wonder what impact this note to self is going to have
You can also save the messages that are in the buffer for the current channel with just:
/lastlog -file (insert filename here)
Latest Poopli Updaters -- http://lkc.me/poop
|<< <||> >>|
«tivo hd» progressive replaytv mdadm amazon.com usb tardis «watch instantly» raid1 orac prescription tv virtualbox linux woot dvd zen «windows 7» cpap 10.04lts box «amazon prime» tivo «powersource 400» «sans digital» cox ebay raid «doctor who» ups «windows xp» «air purifier» twitter «hd movie» boxee cfengine3 boinc eyeglasses freebsd b2evolution upgrade dsl lhaven batteries «instant streaming» backuppc «chicago tardis» appletv netflix ubuntu