Gnus development mailing list
 help / color / mirror / Atom feed
From: Andrew Cohen <acohen@ust.hk>
To: ding@gnus.org
Subject: Re: useful things with nnselect
Date: Wed, 09 Sep 2020 11:26:05 +0800	[thread overview]
Message-ID: <87k0x3y6k2.fsf@ust.hk> (raw)
In-Reply-To: <878sdj4plv.fsf@ericabrahamsen.net>


>>>>> "EA" == Eric Abrahamsen <eric@ericabrahamsen.net> writes:

[...]

    EA> I'd be curious to hear how this differs from nnir -- as far as I
    EA> know, these things were mostly already possible with nnir,
    EA> right?

In fact, no, most of these things weren't possible with nnir. Firstly,
nnir is (or I mean, used to be :)) a combination of two things:
searching, and glue to make the result of a search work as a gnus
group. This glue didn't allow for persistent groups, only ephemeral ones
(well, a long time ago I hacked something in to kind of allow it, but
the resulting groups didn't work like regular gnus groups and had
significant limitations). Also, nnir didn't originally contain any of
the logic to make changes in these groups permanent (again, I have over
time added more and more of this functionality, but it was never
complete).

The point of nnselect was to cleanly separate the searching (which is in
nnir) from what to do with the list of matches that searching
returns. nnselect is now a first-class backend---nnselect groups should
behave like any other group (can be persistent or ephemeral; all marks,
changes, etc are supported). Also, nnselect groups don't have to come
from an nnir search. The Todo group I described has nothing to do with
searches and nnir isn't used. I have a variety of groups like this that
I didn't describe because they are kind of niche. But nnselect makes
this possible.

    EA> FWIW, I'm most excited about nnselect as a hacker, as it allows
    EA> you to decouple the search process from the servers altogether
    EA> -- nnir required all searches to *start* with one or more
    EA> servers, while nnselect lets you approach the thing in a more
    EA> ad-hoc fashion.

Yes, that is the point---decoupling the search from anything
gnus-specific, and allowing the search to be its own thing (which allows
it to be server-neutral). 

    EA> One thing I'm noticing now (sorry I didn't see this earlier!) is
    EA> that ephemeral search groups don't seem 100% ephemeral: I've
    EA> searched using "G G" in the Groups buffer and "G" in the Server
    EA> buffer, and while the search groups are no longer visible when I
    EA> leave them, they seem to be updating when I hit "g" to update
    EA> everything later on: I get a bunch of Messages about
    EA> re-searching the groups that were part of the earlier search
    EA> groups.

This sounds like a bug, and isn't happening for me. When closing one of
these groups this should happen:

    (when (gnus-ephemeral-group-p group)
      (gnus-kill-ephemeral-group group)
      (setq gnus-ephemeral-servers
	    (assq-delete-all 'nnselect gnus-ephemeral-servers)))

So the ephemeral group should be really, truly, gone after exit. 




  reply	other threads:[~2020-09-09  3:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-08  1:41 Andrew Cohen
2020-09-09  3:05 ` Eric Abrahamsen
2020-09-09  3:26   ` Andrew Cohen [this message]
2020-09-09 18:12     ` Eric Abrahamsen
2020-09-09  6:23 ` Eric S Fraga
2020-09-09  6:41   ` Andrew Cohen
2020-09-09 11:31     ` Eric S Fraga
2020-09-11  0:00       ` Andrew Cohen
2020-09-11  8:25         ` Eric S Fraga

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k0x3y6k2.fsf@ust.hk \
    --to=acohen@ust.hk \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).