From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-2.1 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 1318 invoked from network); 22 Mar 2022 15:11:33 -0000 Received: from mx1.math.uh.edu (129.7.128.32) by inbox.vuxu.org with ESMTPUTF8; 22 Mar 2022 15:11:33 -0000 Received: from lists1.math.uh.edu ([129.7.128.208]) by mx1.math.uh.edu with esmtps (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1nWgAU-0058Kz-8n for ml@inbox.vuxu.org; Tue, 22 Mar 2022 10:11:30 -0500 Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by lists1.math.uh.edu with smtp (Exim 4.94.2) (envelope-from ) id 1nWgAT-0066UR-ME for ml@inbox.vuxu.org; Tue, 22 Mar 2022 10:11:29 -0500 Received: from mx2.math.uh.edu ([129.7.128.33]) by lists1.math.uh.edu with esmtp (Exim 4.94.2) (envelope-from ) id 1nWgAR-0066UI-EF for ding@lists.math.uh.edu; Tue, 22 Mar 2022 10:11:27 -0500 Received: from quimby.gnus.org ([95.216.78.240]) by mx2.math.uh.edu with esmtps (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1nWgAP-00AXFi-9X for ding@lists.math.uh.edu; Tue, 22 Mar 2022 10:11:27 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Content-Transfer-Encoding:Content-Type:Mime-Version:References :Message-ID:Date:Subject:From:To:Sender:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=m76M0ehlT8CQw23VfRn6mw6OSIj7NH+d3mIdvp7M5B0=; b=PuKMJHIZcEsScLZzS61c/FBWIE A+X8r3PdhB5vjx0kih6tnOVSARhLD3fty0yuS1KQnVkYv0WF7o3+opws4IyMTlBvPEmfRGSFiHQDb 5Ee2IZcPoyuA+hqPL+8BwjUX0LH0ftXTz9+a8zSCaFSUQxGb0EjBoGzWh2bPq9m+TOpk=; Received: from ciao.gmane.io ([116.202.254.214]) by quimby.gnus.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nWgAG-0007Dx-KD for ding@gnus.org; Tue, 22 Mar 2022 16:11:20 +0100 Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1nWgAF-000374-8F for ding@gnus.org; Tue, 22 Mar 2022 16:11:15 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: ding@gnus.org From: Eric Abrahamsen Subject: Re: gnus-search configuration example for notmuch Date: Tue, 22 Mar 2022 08:11:08 -0700 Message-ID: <87o81yja43.fsf@ericabrahamsen.net> References: <87pmmfl20w.fsf@free.fr> <874k3qlw39.fsf@ericabrahamsen.net> <87a6di2yim.fsf@free.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cancel-Lock: sha1:pEe7p6LWh/oWfdc+LoQKqSp5JE8= List-ID: Precedence: bulk Julien Cubizolles writes: > Eric Abrahamsen writes: > >> Julien Cubizolles writes: >> >>> I can't get gnus-search to use notmuch as its search engine for a >>> maildir synced by offlineimap. Every search with G-G returns >> >> Hi! >> >> It's not possible to use notmuch to index an nnimap server. notmuch >> returns its search results as filenames, and nnimap needs its search >> results as message ids. > > Thank you, it all makes sense now. Maybe that's also why it doesn't work > on nnml and nndraft either. > > What backend can you use gnus-search-notmuch with then ? And what search > engines should you use with nnml and nndraft ? Am I right in assuming > that with the right gnus-search-engines set up gnus-search could search > through all backends and return the matching messages in a single > nnselect group ? To add to what everyone else has said: most of the mail backends (nnml, nnmaildir, etc) keep their messages as files on the file system, so any search engine that indexes files and gives you full filenames back as search results (including notmuch, namazu, mairix) will work with them. It's really nnimap that is a special case, as you're not supposed to know or care where/how it stores its messages, and instead use the client/server interface. And yes, the whole point of gnus-search and nnselect is that you can search any number of groups and servers, using a single search query and getting the results in a single group.