Excerpts from William Morgan's message of Thu Oct 01 12:53:15 -0400 2009: > Reformatted excerpts from Bo Borgerson's message of 2009-09-12: > > Register label-list-mode with the UpdateManager and handle added > > updates with a reload to keep unread message counts up to date > > Branch label-list-mode-auto-update, merged into next. >
Hi William. Thanks for looking at this. > I'm a little concerned with performance, but we'll see how it goes. > Yeah, I think I might be spoiled by my relatively few messages / labels. If it turns out to be an issue maybe it could be made toggle-able with a key-press? (Default off / configurable)? I actually use the label-list-mode as my "home" screen. I like it to stay up-to-date so I can quickly scan which labels have new messages. Incidentally the recent discussion in another thread about making the inbox more like other labels resonates with me. My workflow for all other labels is just to 'x' out when I'm done, but with the inbox I have to '$'ave and 'B'uffer-switch. > What do you think about handling labeled and deleted updates as well? Is there a way to label or delete threads without leaving the label-list-mode? There's already a refresh when switching back to the label-list-mode from elsewhere, I think, so any changes that are $aved should be reflected immediately when you get back. Labels added automatically in a before-add-message hook should already be present when the 'added' update event is received, right? I'm not trying to argue against adding handlers for labeled and deleted updates. I just want to make sure I understand the use cases so I know how to test. Thanks, Bo _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
