From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id Q/b1FualtV/2JAAA0tVLHw (envelope-from ) for ; Wed, 18 Nov 2020 22:53:26 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0 with LMTPS id eBCIEualtV/yCwAA1q6Kng (envelope-from ) for ; Wed, 18 Nov 2020 22:53:26 +0000 Received: from mail.notmuchmail.org (nmbug.tethera.net [IPv6:2607:5300:201:3100::1657]) (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 2778B9403CD for ; Wed, 18 Nov 2020 22:53:23 +0000 (UTC) Received: from nmbug.tethera.net (localhost [127.0.0.1]) by mail.notmuchmail.org (Postfix) with ESMTP id E36D128C5B; Wed, 18 Nov 2020 17:53:14 -0500 (EST) Received: from fethera.tethera.net (fethera.tethera.net [IPv6:2607:5300:60:c5::1]) by mail.notmuchmail.org (Postfix) with ESMTP id 90FBB2710B for ; Wed, 18 Nov 2020 17:53:11 -0500 (EST) Received: by fethera.tethera.net (Postfix, from userid 1001) id 6DC585FB8B; Wed, 18 Nov 2020 17:53:09 -0500 (EST) Received: (nullmailer pid 2087918 invoked by uid 1000); Wed, 18 Nov 2020 22:53:08 -0000 From: David Bremner To: Wenlong Dai Subject: Re: Search Case Sensitivity In-Reply-To: References: <87a6ve6gzp.fsf@tethera.net> Date: Wed, 18 Nov 2020 18:53:08 -0400 Message-ID: <87ft5646qz.fsf@tethera.net> MIME-Version: 1.0 Message-ID-Hash: BAMACBZUBB4E4HHNMXJXBH4QPI3IND6M X-Message-ID-Hash: BAMACBZUBB4E4HHNMXJXBH4QPI3IND6M X-MailFrom: david@tethera.net 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: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Scanner: ns3122888.ip-94-23-21.eu Authentication-Results: aspmx1.migadu.com; dkim=none; dmarc=none; spf=pass (aspmx1.migadu.com: domain of notmuch-bounces@notmuchmail.org designates 2607:5300:201:3100::1657 as permitted sender) smtp.mailfrom=notmuch-bounces@notmuchmail.org X-Spam-Score: -1.01 X-TUID: 2eCZ7nXlbKiq Wenlong Dai 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.