Hi Edward, I think these are by and large legitimate gripes and I'd be delighted to have someone motivated to fix them!
Reformatted excerpts from Edward Z. Yang's message of 2009-06-05: > 1. Threads should be lazy-loaded (possibly in the background), with > visible messages first. FWIW, this is particularly egregious in a direct IMAP connection, and those of us who have switched to Maildir or who use mbox aren't punished. But it would be very cool to have this. > If a conversation got a new message, Sup should only take its time to > load that message, and not the frickin' 24 other messages that were > also incidentally there. I suspect this will require some pretty > major refactoring. It might not be too bad. Turn off the call to m.load_from_source! on line 106 of thread-index-mode.rb, add a Queue to ThreadViewMode containing messages to call #load_from_source! on, don't call m.chunks in ThreadViewMode#regen_text unless the message has been loaded, start a thread that pops messages from the queue, calls #load_from_source! on them, and then calls regen_text when an open message has been loaded... and you're 90% of the way there. > 2. Auto-completion sucks and should be improved. I should be able > to press "c", type two letters, and then mash tab. If auto-completion > actually works, then I'll blame it on dismal contacts.txt support The auto-completion is awesome. Adding a recipient to the contacts list is a good idea. > 3. Polling and loading of threads should started, asynchronously, at > the same time. > Loading of threads should not hose my CPU. Agreed. Please fix. > Loading of threads should do smart things, instead of doing an O(n) > time warp. It's definitely worse than O(n). Loading threads could be sped up dramatically by storing the thread structure somewhere (either cached or just for every thread), since Sup does a lot of extra work rethreading everything every time you start it up. FWIW I'm doing this the right way in Sup 2.0. > 4. Sup should prompt me whether or not I want to Reply All or Reply on > appropriate cases, like pine. There have been a couple similar requests like this recently, though it's not clear if everyone has known about the ability to change the reply mode and about the reply-to hook. Since hitting 'r' defaults to replying to the sender alone (except for mailing list messages), I'd be ok with adding a Mutt-style reply-to-all key that starts up reply-mode with the 'reply to all' mode active. -- William <wmorgan-...@masanjin.net> _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
