From: David Bremner <david@tethera.net>
To: Wenlong Dai <whudwl@gmail.com>
Cc: notmuch@notmuchmail.org
Subject: Re: Search Case Sensitivity
Date: Wed, 18 Nov 2020 18:53:08 -0400 [thread overview]
Message-ID: <87ft5646qz.fsf@tethera.net> (raw)
In-Reply-To: <CADmxP+NPsrK5ytOmH_4=WpTu_qPxNqBWn1JCNfonE+h0A14-fw@mail.gmail.com>
Wenlong Dai <whudwl@gmail.com> writes:
> I later realised my statement was wrong. I did not test all search terms.
> I was only testing the folder: search term.
>
> It seems folder: search is always case-sensitive and it doesn't allow wild
> cards.
> So if I want to find messages in a specific folder, I'll have to spell the
> folder name case-sensitively,
> and I'll have to either remember the full path or use regex. Is this
> understanding correct?
> If it is, then I would say it's a bit unexpected and odd.
Yes, that sounds right. folder: (and path:) searches are based on the
paths on disk. I have to admit I don't use folder searches (or upper
case path names ;)) much, so I leave it to others to discuss whether having
case-insensitive path searches would be worthwhile. Offhand I think it
would require indexing some additional terms, and we'd want to know how
much that increased the database size before deciding.
path: prefixes do support a limited form of wildcards to support
recursive search. In general Xapian wildcard is somewhat limited,
currently only allowing wildcards at the end of terms. I think that may
change in the future, and could be useful for notmuch queries, since
people are used to globs in paths.
prev parent reply other threads:[~2020-11-18 22:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 11:02 Search Case Sensitivity Wenlong Dai
2020-11-18 11:28 ` David Bremner
2020-11-18 20:56 ` Wenlong Dai
2020-11-18 22:53 ` David Bremner [this message]
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=87ft5646qz.fsf@tethera.net \
--to=david@tethera.net \
--cc=notmuch@notmuchmail.org \
--cc=whudwl@gmail.com \
/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).