From: Austin Clements <amdragon@MIT.EDU>
To: Dmitry Kurochkin <dmitry.kurochkin@gmail.com>
Cc: notmuch@notmuchmail.org
Subject: Re: [PATCH] tag: Automatically limit to messages whose tags will actually change.
Date: Tue, 8 Nov 2011 11:10:05 -0500 [thread overview]
Message-ID: <20111108161005.GB2658@mit.edu> (raw)
In-Reply-To: <878vnrut9j.fsf@gmail.com>
Quoth Dmitry Kurochkin on Nov 08 at 8:34 am:
> Hi Austin.
>
> On Mon, 7 Nov 2011 22:55:23 -0500, Austin Clements <amdragon@MIT.EDU> wrote:
> > This optimizes the user's tagging query to exclude messages that won't
> > be affected by the tagging operation, saving computation and IO for
> > redundant tagging operations.
> >
> > For example,
> > notmuch tag +notmuch to:notmuch@notmuchmail.org
> > will now use the query
> > ( to:notmuch@notmuchmail.org ) and (not tag:"notmuch")
> >
> > In the past, we've often suggested that people do this exact
> > transformation by hand for slow tagging operations. This makes that
> > unnecessary.
>
> Thanks! This is a very useful optimization.
>
> Does it work for multiple tags and tag removal? I.e.:
>
> notmuch tag -inbox -unread +sent from:dmitry.kurochkin@gmail.com
>
> can be converted to:
>
> notmuch tag -inbox -unread +sent from:dmitry.kurochkin@gmail.com and (tag:inbox or tag:unread or (not tag:sent))
Yep. This is pretty much exactly what it does.
next prev parent reply other threads:[~2011-11-08 16:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 3:55 [PATCH] tag: Automatically limit to messages whose tags will actually change Austin Clements
2011-11-08 4:34 ` Dmitry Kurochkin
2011-11-08 16:10 ` Austin Clements [this message]
2011-11-08 10:41 ` Sebastian Spaeth
2011-11-09 8:46 ` Jani Nikula
2011-11-09 13:40 ` Austin Clements
2011-11-10 13:28 ` Sebastian Spaeth
2012-11-06 1:56 ` David Bremner
2011-11-09 13:44 ` [PATCH v2] " Austin Clements
2011-11-16 17:41 ` Tomi Ollila
2011-11-28 15:46 ` David Bremner
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=20111108161005.GB2658@mit.edu \
--to=amdragon@mit.edu \
--cc=dmitry.kurochkin@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).