From: Kevin Foley <kevin@kevinjfoley.me>
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Subject: Re: Handling Email Addresses Without Name
Date: Mon, 17 Jan 2022 10:20:10 -0500 [thread overview]
Message-ID: <87k0eyz8wl.fsf@kevinjfoley.me> (raw)
In-Reply-To: <87lezhxidg.fsf@tethera.net>
David Bremner <david@tethera.net> writes:
> If you have want you can define a query
>
> $ notmuch config set query.John from:jdoe@example.com
>
> Then you can use
>
> $ notmuch search query:John
This isn't ideal as I'd prefer not to have to remember to use a query
instead of "from". However, I didn't know about the predefined query
feature so that's cool to see.
> Xapian has a synonym facility [1], but it is not currently used by
> notmuch. This would work well for this particular application, but
> (unlike query) it ORs the original term into the expansion (as makes
> sense for synonyms). That would make it less useful for cases like
> "from:me", where the query would match a literal "me" in the from
> field. Thanks to Apple's cloud thingy, that actually matches quite a
> lot.
>
> [1]: https://xapian.org/docs/synonyms.html
This could be interesting. I actually do something write now in my post
new hook script where I get all versions of my email address (I at one
time used an address based on each website) and update the value of
`user.other_email`.
If there was the ability to assign synonyms I might be able to do
something similar. It would depend what the interface was like I
suppose. For example, what if I wanted to connect "John", "John Doe",
and "Doe" to "jdoe@example.com"? I'm guessing based on the Xapian docs
that would end up being 3 different calls.
Kevin
next prev parent reply other threads:[~2022-01-17 15:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 21:54 Handling Email Addresses Without Name Kevin Foley
2022-01-15 12:15 ` Ralph Seichter
2022-01-17 15:05 ` Kevin Foley
2022-01-15 13:01 ` David Bremner
2022-01-17 15:20 ` Kevin Foley [this message]
2022-01-17 18:14 ` David Bremner
2022-01-17 20:57 ` Kevin Foley
2022-01-18 13:15 ` Gregor Zattler
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=87k0eyz8wl.fsf@kevinjfoley.me \
--to=kevin@kevinjfoley.me \
--cc=david@tethera.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).