unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: Michael J Gruber <michaeljgruber+grubix+git@gmail.com>,
	io <io@ooeeeoo.com>
Cc: notmuch@notmuchmail.org
Subject: Re: Advanced search with wildcard using notmuch for mutt
Date: Thu, 30 Nov 2023 09:31:19 -0400	[thread overview]
Message-ID: <87jzpzqsew.fsf@tethera.net> (raw)
In-Reply-To: <CAA19uiT=NOYqm=6_GU4MKArG4Z+_3jcd3xabCzMY=+dwHA-pkw@mail.gmail.com>

Michael J Gruber <michaeljgruber+grubix+git@gmail.com> writes:


> Using xapian commands, one could extract all stems and grep those for a
> term which one "remembers partially" (often happened to me), and then feed
> that into notmuch. Might be worthwhile scripting or even integrating into
> notmuch (sexp?).

The words are stored unstemmed as well, so in principle we could extract
those and do some kind of fuzzy search on them to construct
queries. This is what notmuch already does for regex searches on fields
other than from, subject, and mid. The reason this is not too attractive
for the message body is that it works on a per word basis, and most uses
of regex (although not the one under discussion) involve matching
multiple words. Currently Xapian only supports trailing wildcards (which
would not help here), but we could do that for body words. It just
doesn't (or hasn't) seemed like such a common use case. 

Alas, none of the forward looking discussion really helps the original
poster.

  reply	other threads:[~2023-11-30 13:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-30  2:18 Advanced search with wildcard using notmuch for mutt io
2023-11-30 11:53 ` Michael J Gruber
2023-11-30 13:31   ` David Bremner [this message]
2023-12-04  1:36     ` io
2023-12-04 11:39       ` David Bremner
2023-12-04 20:00         ` Olly Betts
2023-12-04 21:10           ` David Bremner
2023-12-06  7:07             ` io
2023-12-07 18:55               ` Olly Betts

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=87jzpzqsew.fsf@tethera.net \
    --to=david@tethera.net \
    --cc=io@ooeeeoo.com \
    --cc=michaeljgruber+grubix+git@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).