[PATCH] emacs: add tag jump menu

[Jani Nikula]

On Sun, 18 Sep 2016, Ioan-Adrian Ratiu <adi at adirat.com> wrote:
> On Sun, 18 Sep 2016, Mark Walters <markwalters1009 at gmail.com> wrote:
>> On Sun, 18 Sep 2016, Ioan-Adrian Ratiu <adi at adirat.com> wrote:
>>> Hi
>>>
>>> I have implemented something similar in my tree and I really like the
>>> idea. I have one issue though.
>>>
>>> On Sat, 17 Sep 2016, Mark Walters <markwalters1009 at gmail.com> wrote:
>>>> Add a "jump" style menu for doing tagging operations.
>>>> ---
>>>>
>>>> Jani suggested something like this on irc today. This is a first cut
>>>> to see if people like it. By default the tagging jump menu is bound to
>>>> k (which works in search/show/tree mode), and has the following options
>>>>
>>>> a (Archive) -inbox -unread
>>>> u (Mark Read) -unread
>>>> d (Delete)  +deleted
>>>>
>>>> If you do ctrl-u k the it will do the reverse operation.
>>>
>>> I know C-u is default emacs behaviour but I find very cumbersone to do
>>> C-u for unapplying the tag. What I do and want is to simply apply the
>>> tag when pressing "d" then unapply it when pressing "d" again if the
>>> mail/thread already contains the deleted tag (basically it's a toggle).
>>
>> I agree that C-u is a little cumbersome -- I think I would be happy for
>> a toggle for single messages (with a single tag change), but for
>> multiple messages like a thread I think it would be very unclear what it
>> was doing.
>
> My workflow with the kind of code shown above is as follows:
>
> If in notmuch-search then pressing 'd' "deletes" everything selected,
> including multiple messages in a region and if a thread was selected in
> that region then the entire thread is deleted.

You are not addressing the toggle case where some of the messages in
those threads have the tag, and some do not. How should notmuch know
whether you want to add or remove the deleted tag?

> IMO this is the simplest and the clearest workflow.

While working on Notmuch, one of the main lessons I've learned is that
*everyone* has their own, personal email workflow. We need to try to
give people discoverable and intuitive *mechanisms* on dealing with
email, and let people build their own workflows that suit them.

(That said, I always try to encourage people to rethink their workflows
when switching to Notmuch. But it's still *their* workflow.)


BR,
Jani.