unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Michael J Gruber <michaeljgruber+grubix+git@gmail.com>
To: io <io@ooeeeoo.com>
Cc: notmuch@notmuchmail.org
Subject: Re: Advanced search with wildcard using notmuch for mutt
Date: Thu, 30 Nov 2023 12:53:02 +0100	[thread overview]
Message-ID: <CAA19uiT=NOYqm=6_GU4MKArG4Z+_3jcd3xabCzMY=+dwHA-pkw@mail.gmail.com> (raw)
In-Reply-To: <ZWfwofrtxSWxF044@mail.ooeeeoo.com>


[-- Attachment #1.1: Type: text/plain, Size: 728 bytes --]

Am Do., 30. Nov. 2023 um 12:37 Uhr schrieb io <io@ooeeeoo.com>:

>
>
>
> i have an html email with this sentence 'xycfe11cg64d_2501034012' within
> the body of the message.
> no result found when i search for '2501034012'
> i have even tried using '*2501034012*' (wildcard)
>
> Notmuch doesn't support regular expressions ("wildcards") when searching
the body of messages, see the man page  for `notmuch-search-terms`. It
computes stems of words and indexes (and searches) those.

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?).

Michael

[-- Attachment #1.2: Type: text/html, Size: 1154 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2023-11-30 11:53 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 [this message]
2023-11-30 13:31   ` David Bremner
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='CAA19uiT=NOYqm=6_GU4MKArG4Z+_3jcd3xabCzMY=+dwHA-pkw@mail.gmail.com' \
    --to=michaeljgruber+grubix+git@gmail.com \
    --cc=io@ooeeeoo.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).