From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: useful things with nnselect
Date: Wed, 09 Sep 2020 11:12:25 -0700 [thread overview]
Message-ID: <87363qom46.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87k0x3y6k2.fsf@ust.hk>
Andrew Cohen <acohen@ust.hk> writes:
>>>>>> "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.
Cool, thanks for clarifying!
next prev parent reply other threads:[~2020-09-09 18:12 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
2020-09-09 18:12 ` Eric Abrahamsen [this message]
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=87363qom46.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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).