From: David Bremner <david@tethera.net>
To: Sebastian Poeplau <sebastian.poeplau@eurecom.fr>,
notmuch@notmuchmail.org
Subject: Re: notmuch-tag-jump for multiple threads
Date: Fri, 05 Apr 2019 21:46:26 -0300 [thread overview]
Message-ID: <87r2agarkt.fsf@tethera.net> (raw)
In-Reply-To: <87d0m31eip.fsf@eurecom.fr>
Sebastian Poeplau <sebastian.poeplau@eurecom.fr> writes:
> Hi all,
>
> I'm wondering which workflow people use for this situation that comes up
> frequently for me: I have a search that gives me a bunch of threads, say
> new messages from a mailing list, and then I go over them, possibly
> reading some threads in detail and skipping over others. Afterwards, I
> would like to apply some tag changes to all threads, like "-unread" or
> "+archived". So far, the two ways I've found to do so in the search view
> are '*' (`notmuch-search-tag-all') and typing the tag change in the
> completing read, or marking the entire buffer followed by 'k'
> (`notmuch-tag-jump') and the shortcut for my change. It feels as if
> something like 'K' would be nice, offering the same jump menu like 'k'
> but applying the change to all displayed messages.
>
> What is your take? Do you ever encounter the same situation? I would
> give the implementation a try but wanted to make sure first that I'm not
> missing anything.
I tend to use '*' for those situations, but that might be because
tag-jump was added later. Your proposal sounds ok, as long as it re-uses
most of the tag-jump code.
On a semi-related note I sometimes miss the
ability to mark a set of non-contiguous threads / messages for action
(like 'm' in dired).
next prev parent reply other threads:[~2019-04-06 0:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 12:04 notmuch-tag-jump for multiple threads Sebastian Poeplau
2019-04-06 0:46 ` David Bremner [this message]
2019-04-08 9:11 ` Sebastian Poeplau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r2agarkt.fsf@tethera.net \
--to=david@tethera.net \
--cc=notmuch@notmuchmail.org \
--cc=sebastian.poeplau@eurecom.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).