From: Lele Gaifax <lele@metapensiero.it>
To: notmuch@notmuchmail.org
Subject: New "notmuch address" command
Date: Fri, 12 Dec 2014 10:16:14 +0100 [thread overview]
Message-ID: <878uid9qjl.fsf@nautilus.nautilus> (raw)
Hi all again,
I'm happily using "notmuch-addrlookup"[1] as "notmuch-address-command", in
my Emacs configuration.
As explained in my other message, yesterday I spent some time tweaking
that configuration and tried to replace it with the new "notmuch
address" introduced in version 0.19.
An (almost) equivalent of "notmuch-addrlookup foo" could be "notmuch
address to:foo* OR from:foo*", but it has at least one indesiderable
difference: it seems considering the "CC" field, but always emits the
"TO" content (i.e., assuming I have a message I sent to "john@doe.com"
and CCed to "foo@bar.com", "notmuch address to:foo" emits
"john@doe.com", not "foo@bar.com") so the candidates it generates are
way too much.
I don't know it that's done on purpose (I clearly miss the use case if
so).
I wonder if it would be reasonable adding a "--complete" flag to the
"address" command that selects a more specific behaviour, so that
"notmuch address --complete foo":
a) automatically performs a partial match (i.e. it adds the '*' suffix
on its own)
b) searches the given text only in the related headers (hiding the
difference between "incoming" and "outgoing" messages, and not
considering the body at all)
c) avoids the "bug"/"feature" explained above
What do you think?
Thank you,
ciao, lele.
[1] https://github.com/aperezdc/notmuch-addrlookup-c
--
nickname: Lele Gaifax | Quando vivrò di quello che ho pensato ieri
real: Emanuele Gaifas | comincerò ad aver paura di chi mi copia.
lele@metapensiero.it | -- Fortunato Depero, 1929.
next reply other threads:[~2014-12-12 9:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 9:16 Lele Gaifax [this message]
2014-12-12 10:39 ` New "notmuch address" command Michal Sojka
2014-12-12 12:10 ` Lele Gaifax
2014-12-14 14:24 ` Michal Sojka
2014-12-14 18:56 ` Lele Gaifax
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=878uid9qjl.fsf@nautilus.nautilus \
--to=lele@metapensiero.it \
--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).