Excerpts from William Morgan's message of Mon Jun 08 14:00:23 -0400 2009: > 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.
A few questions: * How do I tell if a message is shown on the screen or not? * The implementation you describe still downloads the messages sequentially, which are usually not the messages we want to download first. I don't mind sup blocking on downloading a message, as long as it's one or two, which means I don't strictly need threads: I just need some API for, when a new message is opened, downloading it and then rendering it. What do you think of this? > The auto-completion is awesome. Adding a recipient to the contacts list is > a good idea. Does contacts.rb apply to people.txt or contacts.txt? > 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. Can you backport it easily to Sup 1.0? > 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. The explicit prompt makes me think about who I want to send the message to. I frequently forget to move the little knob with Sup's behavior. Cheers, Edward _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
