From: Panayotis Manganaris <panos.manganaris@gmail.com>
To: Teemu Likonen <tlikonen@iki.fi>, frederik@ofb.net
Cc: notmuch@notmuchmail.org
Subject: Re: searching for a message by path
Date: Mon, 23 Sep 2024 18:14:00 -0400 [thread overview]
Message-ID: <87v7ymt3vb.fsf@ASCALON.mail-host-address-is-not-set> (raw)
In-Reply-To: <8734lssymz.fsf@iki.fi>
Teemu Likonen <tlikonen@iki.fi> writes:
>
> How about simply using Bogofilter's output value
>
To each their own, of course. I just prefer "wholemeal" programming, as Geraint Jones called it.
I did think of some relevant considerations, though:
"notmuch tag --batch" is much faster than repeatedly invoking "notmuch tag"
Of course, this performance difference is probably not noticeable in a well curated inbox.
Also, the awk-print-tag-batch pattern is re-usable if you'd like to auto-tag messages in other ways e.g.
- tag "vip" threads from known addresses
- pick out coupon codes using a full text search (again, to each their own)
I find this way to be more flexible than the current provisions for "named queries" in the notmuch config/database:
query:<name>
The 'query:' prefix allows queries to refer to previously saved queries added with ‘notmuch-config(1)’.
Though, I'm not poo-pooing that feature. I would certainly appreciate further development on this front.\r
next prev parent reply other threads:[~2024-09-23 22:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-20 17:52 searching for a message by path Frederick Eaton
2024-09-21 0:25 ` Pengji Zhang
2024-09-21 3:23 ` Frederick Eaton
2024-09-21 9:01 ` Pengji Zhang
2024-09-21 9:38 ` Michael J Gruber
2024-09-21 10:44 ` Gregor Zattler
2024-09-21 16:24 ` Panayotis Manganaris
2024-09-21 17:30 ` Teemu Likonen
2024-09-23 22:14 ` Panayotis Manganaris [this message]
2024-09-24 13:00 ` David Bremner
2024-09-24 9:09 ` Michael J Gruber
2024-09-28 2:56 ` Frederick Eaton
2024-09-29 12:08 ` David Bremner
2024-10-12 22:59 ` David Bremner
2024-10-14 6:50 ` Michael J Gruber
2024-10-14 10:58 ` 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=87v7ymt3vb.fsf@ASCALON.mail-host-address-is-not-set \
--to=panos.manganaris@gmail.com \
--cc=frederik@ofb.net \
--cc=notmuch@notmuchmail.org \
--cc=tlikonen@iki.fi \
/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).