From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: search engine for virtual group?
Date: Tue, 01 Feb 2022 08:35:06 -0800 [thread overview]
Message-ID: <87pmo6ilz9.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <877dafj7ey.fsf@ucl.ac.uk>
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> Hello all,
>
> I have an nnvirtual group that combines a number of nnml groups. I
> would like gnus search to work on that folder using notmuch but gnus
> does not seem to allow setting the search engine for a virtual group.
> Any suggestions?
Interesting question! 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 all. You'll have to use the nnselect backend, which can do everything
that nnvirtual can do. Steps would be:
- Recreating the basic virtual setup using nnselect instead. I'm not
100% how this should look, but I know it's doable. We may have to rope
Andy in for advice. There should probably be a special interactive
command to make this use-case easier.
- Searching the group: I _think_ this should work transparently, with no
additional configuration. nnselect knows which component groups make
up a virtual group, knows how to get a list of the servers that own
those groups, and should be able to route the same search query to
each of those servers. In theory you should be able to have a virtual
group made of some groups from an IMAP server and some from a nnml
server that uses notmuch, and results will be returned transparently
from the two different search engines. I've never actually tried this,
though (making an nnselect group from an nnselect group), so it might
take a little tweaking. Basically I was waiting for someone to ask :)
> PS - I was confused by this description of a variable:
>
> gnus-search-engine is a variable without a source file.
>
> This variable is obsolete since 25.1; use 'gnus-search-engine
> instead
Some of this very confusing stuff (the byte compiler would produce
similarly nonsensical complaints) has been fixed recently. Though not
completely; when I do `describe-variable' I get:
gnus-search-engine’s value is ‘gnus-search-engine’
Abstract base class for Gnus search engines.
This variable is obsolete since 25.1;
use \='gnus-search-engine instead
:(
next prev parent reply other threads:[~2022-02-01 16:35 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 [this message]
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
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
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=87pmo6ilz9.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).