[sup-talk] Sup won't start after upgrade to ruby 1.8.7

2008-06-03 Thread Benjamin Kircher
Hi there, got an exception, which is attached. I'm running the git master branch on a Debian sid box. Today ruby and libncurses5 got updated and Sup won't start anymore. Please let me know if I can provide more information. Benjamin --- ArgumentError from thread: main wrong number of

Re: [sup-talk] [PATCH] maildir speedups

2008-06-03 Thread Ben Walton
Ok, I took Grant's suggestion and just dropped the cleanup of the id - filename mapping hash. -Ben -- --- Ben Walton [EMAIL PROTECTED] When one person suffers from a delusion,

Re: [sup-talk] [PATCH] sup color customization

2008-06-03 Thread William Morgan
Reformatted excerpts from Lionel Ott's message of 2008-06-03: Sure I'll attach it this time hopefully it won't break this way. Ok great. I've merged this into next. I tweaked it a little bit. In particular: 1. I removed top-level colors: from colors.yaml. 2. Single attributes can now be

Re: [sup-talk] [bug] NoMemoryError on huge mbox

2008-06-03 Thread William Morgan
Reformatted excerpts from Gabriel Landais's message of 2008-06-03: Here it is (for 10, same thing for 100 000!) : [EMAIL PROTECTED]:~/.mozilla-thunderbird/4v86e51w.default/Mail/pops.codelutin.com ] $ ruby -e 'p File.open(Inbox).read(10)' \000\000\000\000\000\000\000\000\000\000 Ok, well,

Re: [sup-talk] Sup won't start after upgrade to ruby 1.8.7

2008-06-03 Thread William Morgan
Reformatted excerpts from Benjamin Kircher's message of 2008-06-03: got an exception, which is attached. I'm running the git master branch on a Debian sid box. Today ruby and libncurses5 got updated and Sup won't start anymore. Gah. This doesn't even make any sense: --- ArgumentError from

Re: [sup-talk] [PATCH] adding a reply-to hook for setting the default reply-to mode

2008-06-03 Thread William Morgan
Merged in to next. Thanks! Reformatted excerpts from its.jeff.balogh's message of 2008-05-31: Trying again, hopefully the docs are better now. If there's a better way to pretty-print the array, I'd be glad to know it. You could use REPLY_TYPES.inspect. -- William [EMAIL PROTECTED]