[notmuch] Recent (and forthcoming) improvements to the emacs interface
cworth at cworth.org
Fri Dec 4 09:10:45 PST 2009
Thanks for the followup.
On Fri, 04 Dec 2009 14:08:52 +0530, "Aneesh Kumar K. V" <aneesh.kumar at linux.vnet.ibm.com> wrote:
> > Recommendation: Make SPACE only page the current message. Recommend
> > that user use 'a' to advance to next thread, (or 'x' to exit back to
> > search results).
> Later you mention 'N' and 'n' to do the same task. Or are you suggesting
> that 'a' would move to the next task after marking the current task
> read ?
Sorry, I meant for 'N' and 'P' to move between messages in a thread.
But it would make sense to also have commands to navigate to the next
and previous threads. So many actions and so few keys... :-}
> ok that explains. But with Xapian ticket 250 we would definitely want
> some keybinding that move to the next mail without updating tags.
I don't want to let a current bug shape the interface we want. But, yes,
that's a current reality.
> > Recommendation: Revert 'a' to act on all messages in a thread---not
> > only those that match the search results. Then change '*' to work by
> > walking the list and explicitly calling the same action as 'a' on
> > each line. This will provide the desired feedback and should be
> > plenty fast.
> With xapian ticket 250 doing a tag update per thread is going to be
> really slow right ?
Yes, but that's already the case with '*'. The Xapian work involved
should be the same whether calling "notmuch tag" once with the whole
search string, or several times, (once for each thread).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
More information about the notmuch