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 autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 5534 invoked from network); 9 Sep 2020 03:06:04 -0000 Received: from lists1.math.uh.edu (129.7.128.208) by inbox.vuxu.org with ESMTPUTF8; 9 Sep 2020 03:06:04 -0000 Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by lists1.math.uh.edu with smtp (Exim 4.94) (envelope-from ) id 1kFqQG-00Coz0-N2; Tue, 08 Sep 2020 22:05:24 -0500 Received: from mx2.math.uh.edu ([129.7.128.33]) by lists1.math.uh.edu with esmtps (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.94) (envelope-from ) id 1kFqQB-00Cox8-UU for ding@lists.math.uh.edu; Tue, 08 Sep 2020 22:05:19 -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) (envelope-from ) id 1kFqQ9-008RCQ-PQ for ding@lists.math.uh.edu; Tue, 08 Sep 2020 22:05:19 -0500 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=73sCS7om2/RV273Wg/oL2hgQzw82dCgscTjXler4SHM=; b=A8pimXKSijTQ27XsKXwxz8/1I8 DtBxFgPxrRmkdkiQoHusGkgXbjoCNEXlTSQabM/Vma2acvSL6yKOr69DdcWL9+KMaPDC8bw9c20HV v82jgSJOXBugpBndb8JVwFgmcetpwjCFv1+pPpu8B9w/aZDaSoZx/lv3TVWuuOWMGP6M=; Received: from static.214.254.202.116.clients.your-server.de ([116.202.254.214] helo=ciao.gmane.io) by quimby with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kFqQ0-0003qO-NW for ding@gnus.org; Wed, 09 Sep 2020 05:05:12 +0200 Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1kFqPw-000ABp-Tr for ding@gnus.org; Wed, 09 Sep 2020 05:05:04 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: ding@gnus.org From: Eric Abrahamsen Subject: Re: useful things with nnselect Date: Tue, 08 Sep 2020 20:05:00 -0700 Message-ID: <878sdj4plv.fsf@ericabrahamsen.net> References: <87imcp9ha5.fsf@ust.hk> Mime-Version: 1.0 Content-Type: text/plain User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cancel-Lock: sha1:nwvUlQftU2VRmXV5hCWUmrhK3yM= List-ID: Precedence: bulk Andrew Cohen writes: > Now that I've finally found a few moments to push the nnselect backend > to master (with some unfortunate formatting and doc errors along the > way, and a failure to provide aliases for some obsolete variables and > functions :() I thought I would write a longer email to this group about > how I am using it and why it might be right for some of you too. Glad to see it in! > I unfortunately have 4 email accounts (3 work and 1 personal) spread out > on 3 servers, including outlook and gmail (all imap, > fortunately). Together these accounts have about 100k messages. I also > use gmane a bit. Handling all of this is not, uh, > straightforward. Previously I used gnus to sort things into many groups, > and relied heavily on searching to make things manageable. However this > still left me with groups that contained tens of thousands of messages, > and visiting a whole such group is too slow. It ended up being far too > cumbersome. > > I have now switched to a different paradigm. I keep all of my messages > in a small number of groups. I do very little sorting (none, actually) > into these groups (for example, all of my gmail is in a single > group). But I have a large number of virtual nnselect groups for all > sorts of things. Since these are collecting messages from only a small > number of sources, they are very, very fast. And its easy to construct > new ones on the fly. Thread referral makes it easy to look at message > chains as needed. And since the number of messages in these groups is > not too large, I can enter the whole group and use limiting and > group-searching (not nnir-searching) very effectively, and its > practically instantaneous. > > For example, I have groups which contain all messages from certain > people. I have groups for the (small number) of mailing lists I > subscribe to (I used to sort these, but I no longer bother). I have a > group "Recent" that contains all email from the past 7 days from all 4 > accounts (this is the group I use most often; its kind of like having > expiration without any actual expiring :)). I have another group of all > flagged messages from my work accounts. And so on. I'd be curious to hear how this differs from nnir -- as far as I know, these things were mostly already possible with nnir, right? FWIW, I'm most excited about nnselect as a hacker, as it allows you to decouple the search process from the servers altogether -- nnir required all searches to *start* with one or more servers, while nnselect lets you approach the thing in a more ad-hoc fashion. One thing I'm noticing now (sorry I didn't see this earlier!) is that ephemeral search groups don't seem 100% ephemeral: I've searched using "G G" in the Groups buffer and "G" in the Server buffer, and while the search groups are no longer visible when I leave them, they seem to be updating when I hit "g" to update everything later on: I get a bunch of Messages about re-searching the groups that were part of the earlier search groups. Eric