unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Wenlong Dai <whudwl@gmail.com>
To: David Bremner <david@tethera.net>
Cc: notmuch@notmuchmail.org
Subject: Re: Search Case Sensitivity
Date: Thu, 19 Nov 2020 07:56:24 +1100	[thread overview]
Message-ID: <CADmxP+NPsrK5ytOmH_4=WpTu_qPxNqBWn1JCNfonE+h0A14-fw@mail.gmail.com> (raw)
In-Reply-To: <87a6ve6gzp.fsf@tethera.net>


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

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.

On Wed, 18 Nov 2020 at 22:28, David Bremner <david@tethera.net> wrote:

> Wenlong Dai <whudwl@gmail.com> writes:
>
> > Based on my usage and testing, it seems to me that all notmuch searches
> are
> > case-sensitive.
> > Is this true?
> > Is there a way to do case-insensitive search?
>
> Most searches (other than boolean prefixes and regex searches) are in
> fact case insensitive. The definition of case is English-centric. Can
> you give an example of a search that is case-sensitive that you are
> expecting to be case insensitive?
>
> d
>
>

-- 
Kind Regards,
Wenlong Dai

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

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



  reply	other threads:[~2020-11-18 20:57 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 [this message]
2020-11-18 22:53     ` David Bremner

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='CADmxP+NPsrK5ytOmH_4=WpTu_qPxNqBWn1JCNfonE+h0A14-fw@mail.gmail.com' \
    --to=whudwl@gmail.com \
    --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).