[sup-talk] What's your sup workflow (and a spew of ideas)
rlane at club.cc.cmu.edu
Tue Aug 18 23:02:57 EDT 2009
Excerpts from Carl Worth's message of Tue Aug 18 21:58:55 -0400 2009:
> > allow-for-limiting-to-interesting-labels:
> > I have a hack for this. I reopen Redwood::Mode in the startup hook, then
> > add a keybinding to spawn a SearchResultsMode for a set of interesting
> > labels. Same for starred messages. A better solution would be good.
> While waiting for a better solution, would you mind sharing your code
> for this? I'm quite new to ruby, so even if what you described should
> be trivial for me to replicate, it's not yet. :-)
> Maybe a page on the wiki?
Sure, I added an example to the end of the Hooks page.
> Meanwhile, I thought of another race condition. If new mail arrives
> for the current thread when in thread-view-mode, does it get added to
> the view? It might seem nice for it to show up, but it might also lead
> to it getting accidentally archived away if I "knew" that there were
> only 4 messages, say, when I entered the thread view, then I hit ".a"
> and archived away 5 messages.
> It seems a silly thing, but it's the kind of thing that makes me start
> distrusting ".a" and instead using "x", double-checking, then "a"
> which is obviously less efficient. (Oh, and there's another place
> where the current selector needs to not be perturbed. After I hit "x"
> from thread-view-mode I find that a different thread can be selected
> than the one I was just viewing if new mail arrived.)
I'm glad to know there are other people annoyed by UI race conditions :).
Even after a quick look at the code I'm not sure what ThreadViewMode
will do when a thread is added to. It might actually archive/read/etc
new messages but not display them.
I'd like a keybinding to reload/redisplay the thread and a status bar
note if there are new messages. Any label changes should only affect
messages that have been displayed. What do you think?
More information about the sup-talk