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 20788 invoked from network); 1 Feb 2022 17:30:10 -0000 Received: from mx1.math.uh.edu (129.7.128.32) by inbox.vuxu.org with ESMTPUTF8; 1 Feb 2022 17:30:10 -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 1nEwym-006rE4-78 for ml@inbox.vuxu.org; Tue, 01 Feb 2022 11:30:08 -0600 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 1nEwyl-003mvr-NG for ml@inbox.vuxu.org; Tue, 01 Feb 2022 11:30:07 -0600 Received: from mx2.math.uh.edu ([129.7.128.33]) by lists1.math.uh.edu with esmtp (Exim 4.94.2) (envelope-from ) id 1nEwyk-003mvl-QA for ding@lists.math.uh.edu; Tue, 01 Feb 2022 11:30:06 -0600 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 1nEwyi-00Egtr-T0 for ding@lists.math.uh.edu; Tue, 01 Feb 2022 11:30:06 -0600 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Content-Type:Mime-Version:References:Message-ID:Date:Subject: From:To:Sender:Reply-To:Cc:Content-Transfer-Encoding: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=C3hS7AA/5/6T8TIVhAaJufEz/XhUrVC0lcmq5wLJk30=; b=NFoHbHUI4IzS/OMPPkaRHke562 npQKFLwmWCkJb1vkUyPdMA0gxPCawW/OSRo8L/UJIDN8cD6nfvmWP7INpXG8jkard3Ym4ig3gHqkp ML4BzW+w7DdrYz+BINZEizFSBh86QIxCoILboO9BzFWjtwtQ/ZueEnxolL0eB0yE+Gjg=; 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 1nEwyb-0001Zk-FK for ding@gnus.org; Tue, 01 Feb 2022 18:30:00 +0100 Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1nEwyX-0006H8-OE for ding@gnus.org; Tue, 01 Feb 2022 18:29:53 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: ding@gnus.org From: Eric Abrahamsen Subject: Re: search engine for virtual group? Date: Tue, 01 Feb 2022 09:29:46 -0800 Message-ID: <87h79iijg5.fsf@ericabrahamsen.net> References: <877dafj7ey.fsf@ucl.ac.uk> <87pmo6ilz9.fsf@ericabrahamsen.net> <87bkzqfr5v.fsf@ucl.ac.uk> Mime-Version: 1.0 Content-Type: text/plain User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cancel-Lock: sha1:KPeWXPeDJWRTWxZzheBTqTvG6qA= List-ID: Precedence: bulk Eric S Fraga writes: > Hello Eric, > > On Tuesday, 1 Feb 2022 at 08:35, Eric Abrahamsen wrote: >> First of all I don't think it will ever work with nnvirtual, as >> there's no integration of search and the nnvirtual backend at >> all. > > I was afraid this would be the case. Thank you for confirming. > >> You'll have to use the nnselect backend, which can do everything that >> nnvirtual can do. > > I did try this back when you released nnselect (FTR that was Andy Cohen's work, not mine) > but couldn't achieve the same functionality. I don't completely > remember the details but I think it was that when the groups (that > were brought together into a single nnselect group) were refreshed, > i.e. fetching new mail, the virtual group did not get refreshed. Does > this make sense? That does make sense, and it's something to think about and possibly address. So you had to M-g on the nnselect group in particular to get it to refresh? I don't think nnvirtual is going anywhere, possibly ever, so if you've got a setup that works you should stick with it. But I'd like to get the nnselect stuff as usable as possible, because in the end it's a more versatile tool. > In any case, not being able to search the virtual group is not a deal > breaker: I've put all the constituent groups into their own topic and I > can simply search the topic! That's a good solution, I actually had forgotten you could do that.