From: Eric Abrahamsen <firstname.lastname@example.org>
Subject: Re: search engine for virtual group?
Date: Tue, 01 Feb 2022 09:29:46 -0800 [thread overview]
Message-ID: <email@example.com> (raw)
Eric S Fraga <firstname.lastname@example.org> 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
> 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
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
> 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.
next prev parent reply other threads:[~2022-02-01 17:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 8:52 Eric S Fraga
2022-02-01 16:35 ` Eric Abrahamsen
2022-02-01 16:57 ` Andreas Schwab
2022-02-01 17:23 ` Eric Abrahamsen
2022-02-01 17:11 ` Eric S Fraga
2022-02-01 17:29 ` Eric Abrahamsen [this message]
2022-02-01 17:38 ` Eric S Fraga
2022-02-01 18:46 Eric Abrahamsen
2022-02-01 22:21 ` Eric S Fraga
2022-03-03 16:56 ` dal-blazej
2022-03-07 0:39 ` Andrew Cohen
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).