From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp11.migadu.com ([2001:41d0:303:e16b::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms8.migadu.com with LMTPS id WExkKYe6bWWeLgEA9RJhRA:P1 (envelope-from ) for ; Mon, 04 Dec 2023 12:39:51 +0100 Received: from aspmx1.migadu.com ([2001:41d0:303:e16b::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp11.migadu.com with LMTPS id WExkKYe6bWWeLgEA9RJhRA (envelope-from ) for ; Mon, 04 Dec 2023 12:39:51 +0100 Received: from mail.notmuchmail.org (yantan.tethera.net [IPv6:2a01:4f9:c011:7a79::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 42A9F41CFB for ; Mon, 4 Dec 2023 12:39:51 +0100 (CET) Authentication-Results: aspmx1.migadu.com; dkim=none; dmarc=none; spf=pass (aspmx1.migadu.com: domain of notmuch-bounces@notmuchmail.org designates 2a01:4f9:c011:7a79::1 as permitted sender) smtp.mailfrom=notmuch-bounces@notmuchmail.org ARC-Seal: i=1; s=key1; d=yhetil.org; t=1701689991; a=rsa-sha256; cv=none; b=fW+YWYuuBcakRqBhYxxycQhG0oh6Ysbe573/KRNbgHOitLBDg45zIM+W75p+jbpx6qZ2R8 8M1d4mZLElINs0NFcpNZDu28+xNmc45RLj9eSDAushMNSxbjzmAwHEbIXHFXq6fWCL/rGs tZeSDRSrAtZBf3C6AckrC8wo2LLiD3Bsw5QRv3iV2+GzYCFTk5dIHUG8HEGDKzpGdxoDQe m2kuV++qAd7hpE45S9paKLUEylZ9vgWD7RL5Axdr3e7B/dzt72FQz0WLWfucWrHlR8Mywj Z48UNPEQT6Mi70RMIZ20d9E6XbdpVoHq5NycNEY8XPJ6kfrFCfqZpatOEBmQyA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=none; dmarc=none; spf=pass (aspmx1.migadu.com: domain of notmuch-bounces@notmuchmail.org designates 2a01:4f9:c011:7a79::1 as permitted sender) smtp.mailfrom=notmuch-bounces@notmuchmail.org ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1701689991; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-owner:list-unsubscribe:list-subscribe:list-post; bh=BaCwu8XFo5y1wnoKIF71tbmHZkNIDhxqbWjOt1cwMBg=; b=XdwnnhOzxVMa70rw1TZNLUne0wGMwRzSRORWTbbuMm85xefHsvCTFmOcjOw7zykAsEhMor qAz3esqu67JndyAByp2x44eDjti/RpdOEWIlfD3Hap9WtIeZGPE6pTLsCCG/zbgd08oL8R HPssdCqQCgWTGDDP8M0x5z8zWQmGAGpvXvzNvjZAMZsXt4CgVKXSBm8vyo995dZEQdRBuZ 9Fbilc/4MYnvCDDF30NN29GJidgkTHtcyrafXLOiNWHuOy/cTZdCxj5q9xo6r5OryYypl9 QOSgsLaNKR8Op/2o1P1SwuSHjGkr/2GCUfP9nKBi72ku9J6ezze/Lo07dHncbw== Received: from yantan.tethera.net (localhost [127.0.0.1]) by mail.notmuchmail.org (Postfix) with ESMTP id D19BA5F6BC; Mon, 4 Dec 2023 11:39:48 +0000 (UTC) Received: from phubs.tethera.net (phubs.tethera.net [IPv6:2607:5300:60:3a9d::1]) by mail.notmuchmail.org (Postfix) with ESMTPS id 8EE505E526 for ; Mon, 4 Dec 2023 11:39:46 +0000 (UTC) Received: from tethera.net (fctnnbsc51w-159-2-185-147.dhcp-dynamic.fibreop.nb.bellaliant.net [159.2.185.147]) by phubs.tethera.net (Postfix) with ESMTPS id BA633180066; Mon, 4 Dec 2023 07:39:44 -0400 (AST) Received: (nullmailer pid 292381 invoked by uid 1000); Mon, 04 Dec 2023 11:39:43 -0000 From: David Bremner To: io Subject: Re: Advanced search with wildcard using notmuch for mutt In-Reply-To: References: <87jzpzqsew.fsf@tethera.net> Date: Mon, 04 Dec 2023 06:39:43 -0500 Message-ID: <87edg2gps0.fsf@tethera.net> MIME-Version: 1.0 Message-ID-Hash: KIRUSCQHTYRNVYXJ6T7UWV72OGYHZRWS X-Message-ID-Hash: KIRUSCQHTYRNVYXJ6T7UWV72OGYHZRWS 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; digests; suspicious-header CC: notmuch@notmuchmail.org, xapian-discuss@lists.xapian.org X-Mailman-Version: 3.3.3 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Migadu-Country: DE X-Migadu-Flow: FLOW_IN X-Migadu-Scanner: mx13.migadu.com X-Migadu-Spam-Score: 1.36 X-Spam-Score: 1.36 X-Migadu-Queue-Id: 42A9F41CFB X-TUID: W3FhV/ZVi3G9 io writes: > what xapian 'indexing system' did was to index the entire sentence > 'xxx_yyy' and you will not be able to find any sentence which contain > the word 'yyy'? I'm curious that you refer to xxx_yyy as a sentence. In the contexts I am familiar with, the point of _ is to join things together into one word (or one identifier/token). Other than that your understanding seems correct. > xapian should have this simple wildcard feature which 'grep'(search) > offer. ($grep '*word*' file). It is strange that xapian restrict the > search to 'trailing wildcard' only. I guess the restriction is based on what is easy to do efficiently with the Xapian database (find prefixes). If I remember correctly there was some work in progress to support leading wildcards in Xapian. I can't find relevant discussion now, but I CC'ed the Xapian list in case someone remembers that. > Novice user who get introduce to notmuch just want to run the search > and get the result straight away. Generally the focus of Xapian (and thus notmuch) is on words and phrases like "bob ate my pizza". I agree this is disappointing for someone who wants "all the flexibility of grep, but faster".