From: Jani Nikula <jani@nikula.org>
To: Aaron Ecay <aaronecay@gmail.com>, notmuch@notmuchmail.org
Subject: Re: [PATCH] emacs: call "notmuch tag" only once when archiving a thread
Date: Thu, 05 Jan 2012 22:32:16 +0200 [thread overview]
Message-ID: <87fwftao1b.fsf@nikula.org> (raw)
In-Reply-To: <m2hb09kj0m.fsf@gmail.com>
On Thu, 05 Jan 2012 15:10:33 -0500, Aaron Ecay <aaronecay@gmail.com> wrote:
> On Tue, 3 Jan 2012 20:29:06 +0200, Jani Nikula <jani@nikula.org> wrote:
> > Optimize thread archiving by combining all the -inbox tagging operations to
> > a single "notmuch tag" call.
>
> Perhaps I’m missing something, but is there anything preventing emacs
> from just doing the following?
>
> notmuch tag -inbox thread:000whatever
In the search view it does exactly this.
In the show view it only modifies the messages that are currently
visible. This is to make sure you don't accidentally archive things that
have arrived after refreshing the buffer. I think this is safest.
I suppose the point in the difference is that in search view you're
archiving the thread without seeing the messages anyway. In show view
you have had enough interest in the thread to open it, and you're making
the decision based on the messages you've seen.
BR,
Jani.
next prev parent reply other threads:[~2012-01-05 20:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 18:29 [PATCH] emacs: call "notmuch tag" only once when archiving a thread Jani Nikula
2012-01-04 14:13 ` David Edmondson
2012-01-04 14:35 ` Tomi Ollila
2012-01-05 20:10 ` Aaron Ecay
2012-01-05 20:32 ` Jani Nikula [this message]
2012-01-05 20:38 ` Jameson Graef Rollins
2012-01-05 20:58 ` Jani Nikula
2012-01-06 21:31 ` Tomi Ollila
2012-01-09 0:56 ` Aaron Ecay
2012-01-09 1:12 ` Austin Clements
2012-01-09 8:15 ` David Edmondson
2012-01-09 8:41 ` Jani Nikula
2012-01-09 10:38 ` Tomi Ollila
2012-01-09 10:46 ` David Edmondson
2012-01-09 11:31 ` Mark Walters
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=87fwftao1b.fsf@nikula.org \
--to=jani@nikula.org \
--cc=aaronecay@gmail.com \
--cc=notmuch@notmuchmail.org \
/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).