From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: cohen@bu.edu, 37871@debbugs.gnu.org
Subject: bug#37871: 27.0.50; Merge feature/gnus-select2
Date: Tue, 22 Oct 2019 11:26:59 -0700 [thread overview]
Message-ID: <87pniok558.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87sgnklkct.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 22 Oct 2019 20:13:06 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> Hi all, Andy Cohen's nnselect Gnus backend looks ready to merge -- he
>> wrote to emacs.devel but it occurs to me it might be better to start
>> here. His original message is here, and I've pasted the full text below
>> the link:
>>
>> https://lists.gnu.org/archive/html/emacs-devel/2019-10/msg00689.html
>
> Sounds nice. Is there any impact on Gnus itself, or is it all
> constrained to the new backend?
It shifts nnir over to use nnselect for holding search results, I think
that's all. It makes nnir much easier to use (in the hacking sense,
should be transparent for users). It also let me write the unified
gnus-search interface on top of it, which wasn't possible with the
current implementation of nnir.
next prev parent reply other threads:[~2019-10-22 18:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-22 16:14 bug#37871: 27.0.50; Merge feature/gnus-select2 Eric Abrahamsen
2019-10-22 18:13 ` Lars Ingebrigtsen
2019-10-22 18:26 ` Eric Abrahamsen [this message]
2019-10-22 18:31 ` Lars Ingebrigtsen
2019-10-22 19:39 ` Eric Abrahamsen
2020-07-19 15:35 ` Lars Ingebrigtsen
2020-07-20 5:26 ` Eric Abrahamsen
2020-09-05 1:31 ` Eric Abrahamsen
2020-09-05 12:58 ` Lars Ingebrigtsen
2020-09-05 15:44 ` Eric Abrahamsen
2020-09-06 15:33 ` Basil L. Contovounesios
2020-09-06 22:53 ` Andrew Cohen
2020-10-15 16:04 ` Eric Abrahamsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pniok558.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=37871@debbugs.gnu.org \
--cc=cohen@bu.edu \
--cc=larsi@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).