From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id xIxgH6iKtV9MRQAA0tVLHw (envelope-from ) for ; Wed, 18 Nov 2020 20:57:12 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1 with LMTPS id piUeG6iKtV8XMQAAbx9fmQ (envelope-from ) for ; Wed, 18 Nov 2020 20:57:12 +0000 Received: from mail.notmuchmail.org (nmbug.tethera.net [144.217.243.247]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (2048 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 30E659400BF for ; Wed, 18 Nov 2020 20:57:11 +0000 (UTC) Received: from nmbug.tethera.net (localhost [127.0.0.1]) by mail.notmuchmail.org (Postfix) with ESMTP id 4763928C5B; Wed, 18 Nov 2020 15:57:05 -0500 (EST) Received: from mail-qt1-x82f.google.com (mail-qt1-x82f.google.com [IPv6:2607:f8b0:4864:20::82f]) by mail.notmuchmail.org (Postfix) with ESMTPS id 3982527113 for ; Wed, 18 Nov 2020 15:57:03 -0500 (EST) Received: by mail-qt1-x82f.google.com with SMTP id 7so2781075qtp.1 for ; Wed, 18 Nov 2020 12:57:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=FASafms61KlsJ5TDLrM221vQaPMOXYEeXOBz7g/RTrk=; b=IMs0LAuhUU+lzQFaWqEx1+fiK8/yZDChyjcyWcjDAEwLdH4qnSkkMzeIda8wjLBE5R 3i0+2dlrPAY7ETenj/3AoCfYvHxWl/btKCS0Y4Ps/Q2LpPXtQ5AMk78taKALH0q8o6LP 4DfX+r8KqI38JX8dwDgFBEDMUuAKDKyi6HS8oiem/EsLw4ekWSejpZl67psxK2Djoq4b Fu78Q4vDwBy4ziPzQS5qHNM8oQ2auc+Le3oyAyjlZSSJZjbzLy9aio+d9drWxoiP0tnv ipqBlbZ9zm4/e7xEcRsQz3aS08sQYXoRZfPS3LOCHa54VdsdfQT+bqEsHVxsgIs/lZ3Y IQOg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=FASafms61KlsJ5TDLrM221vQaPMOXYEeXOBz7g/RTrk=; b=PzD910O6dzCTchnrSJ1YAj0ctMyQJG3oQDrmPeZpap7BSZ3xG/wfgyv5DT7EY90iyI jIeyU5LJZXlhR5tWx0E4Xsgu1FKMIWBkAoqcFy2O4xNXchwr8EW0bix5uHhISIiHz+cV ztbCqGrNB6R2Mumk6l+aWkkadPBBIOQ3EQK3Y4S60PhoMtNgm8PY4NnEYWUumCLa2PzP 5vNaIiN7wsw9VA6mmLZ0q04Qlbj2dbuIy6KuzzByhLWv5l8xWuIhkYYvqeZkT6vDgg20 l8Gc/CxDzxvlOxyAn+dgwVJ82aGJvu30gtgxEkycLxrTbXupwaqIIKzzxaOhLII7lAPj DHBA== X-Gm-Message-State: AOAM531YM0cC189wvCwmMwil2FbZpkIxY3WkjkDVVTAeCoS8ai/gHYt4 /fWPcfgFss0a7KjyKC7uUkVzKvC7kAicTSZnJSt4+xZHJWE= X-Google-Smtp-Source: ABdhPJyaQeNURspUEsuaBMVY99ZZ1XmP4Mq+B3e6ibUlIMpD1Y3epgKcd8roXKiuf7q1uK7nCGZg7jOXulNOKI7hSoM= X-Received: by 2002:ac8:7b32:: with SMTP id l18mr7076690qtu.240.1605733022364; Wed, 18 Nov 2020 12:57:02 -0800 (PST) MIME-Version: 1.0 References: <87a6ve6gzp.fsf@tethera.net> In-Reply-To: <87a6ve6gzp.fsf@tethera.net> From: Wenlong Dai Date: Thu, 19 Nov 2020 07:56:24 +1100 Message-ID: Subject: Re: Search Case Sensitivity To: David Bremner Message-ID-Hash: 7DVISIILOL6XXIL6TNRNTD7YXSZ6SBSM X-Message-ID-Hash: 7DVISIILOL6XXIL6TNRNTD7YXSZ6SBSM X-MailFrom: whudwl@gmail.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-notmuch.notmuchmail.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; suspicious-header CC: notmuch@notmuchmail.org X-Mailman-Version: 3.2.1 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Help: List-Post: List-Subscribe: List-Unsubscribe: Content-Type: multipart/mixed; boundary="===============6169339987536193938==" X-Scanner: ns3122888.ip-94-23-21.eu Authentication-Results: aspmx1.migadu.com; dkim=fail (body hash did not verify) header.d=gmail.com header.s=20161025 header.b=IMs0LAuh; dmarc=fail reason="SPF not aligned (relaxed)" header.from=gmail.com (policy=none); spf=pass (aspmx1.migadu.com: domain of notmuch-bounces@notmuchmail.org designates 144.217.243.247 as permitted sender) smtp.mailfrom=notmuch-bounces@notmuchmail.org X-Spam-Score: 1.09 X-TUID: oS9qEBimsiX2 --===============6169339987536193938== Content-Type: multipart/alternative; boundary="00000000000066f98905b467da9c" --00000000000066f98905b467da9c Content-Type: text/plain; charset="UTF-8" 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 wrote: > Wenlong Dai 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 --00000000000066f98905b467da9c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I later realised my state= ment was wrong. I did not test all search terms.=C2=A0
I was only testing the folder: search term.=C2=A0

I= t seems folder: search is always case-sensitive and it doesn't allow wi= ld cards.=C2=A0
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 eit= her remember the full path or use regex. Is this understanding correct?=C2= =A0
If it is, then I would say it'= ;s a bit unexpected and odd.=C2=A0

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 searche= s 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

--00000000000066f98905b467da9c-- --===============6169339987536193938== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline --===============6169339987536193938==--