From: Pieter Praet <pieter@praet.org>
To: Florian Friesdorf <flo@chaoflow.net>, notmuch@notmuchmail.org
Subject: Re: Optimization for notmuch tag by implicit filters
Date: Sat, 16 Apr 2011 14:59:34 +0200 [thread overview]
Message-ID: <87mxjqgxmx.fsf@A7GMS.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87y63d6y25.fsf@eve.chaoflow.net>
On Thu, 14 Apr 2011 10:23:46 +0200, Florian Friesdorf <flo@chaoflow.net> wrote:
>
> With 60k messages and 12k tagged as sent:
>
> $ time notmuch tag +sent -- from:flo@chaoflow.net
>
> real 0m8.561s
> user 0m8.069s
> sys 0m0.212s
>
> $ time notmuch tag +sent -- from:flo@chaoflow.net and not tag:sent
>
> real 0m0.043s
> user 0m0.036s
> sys 0m0.006s
>
>
> This could be made implicit:
>
> notmuch tag +A +B -- <filter>
> -->
> notmuch tag +A +B -- <filter> and not \(tag:A and tag:B\)
>
> Apply command, if one of the tags is not set.
>
>
> notmuch tag -C -D -- <filter>
> -->
> notmuch tag -C -D -- <filter> and \(tag:C or tag:D\)
>
> Apply command, if one of the tags is set.
>
>
> notmuch tag +A +B -C -D -- <filter>
> -->
> notmuch tag +A +B -C -D -- <filter> and \(not tag:A or not tag:B\ or tag:C or tag:D\)
>
>
> In order to enforce tagging and disable the filter there could be a
> flag.
>
> I lack the knowledge/time to implement it, but I think it's at least
> worth documenting it.
>
> --
> Florian Friesdorf <flo@chaoflow.net>
> GPG FPR: 7A13 5EEE 1421 9FC2 108D BAAF 38F8 99A3 0C45 F083
> Jabber/XMPP: flo@chaoflow.net
> IRC: chaoflow on freenode,ircnet,blafasel,OFTC
Non-text part: application/pgp-signature
> _______________________________________________
> notmuch mailing list
> notmuch@notmuchmail.org
> http://notmuchmail.org/mailman/listinfo/notmuch
Most of us already do this explicitly in our tagging scripts, so no harm
in making it standard behaviour, I guess.
Though to keep the implementation nice & clean, I'd advise against the
use of parens: no need for escape chars, no messing with De Morgan's
law, simply map the tag operations to their inverse in conjunctively
joined filters:
notmuch tag +A +B -- <filter> and not tag:A or not tag:B
notmuch tag -C -D -- <filter> and tag:C or tag:D
notmuch tag +A +B -C -D -- <filter> and not tag:A or not tag:B or tag:C or tag:D
Peace
-Pieter
next prev parent reply other threads:[~2011-04-16 12:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 8:23 Optimization for notmuch tag by implicit filters Florian Friesdorf
2011-04-16 12:59 ` Pieter Praet [this message]
2011-04-26 21:31 ` Florian Friesdorf
2011-04-27 20:41 ` Pieter Praet
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=87mxjqgxmx.fsf@A7GMS.i-did-not-set--mail-host-address--so-tickle-me \
--to=pieter@praet.org \
--cc=flo@chaoflow.net \
--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).