Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <>
Cc: Andrew Cohen <>
Subject: Re: search engine for virtual group?
Date: Tue, 01 Feb 2022 10:46:49 -0800	[thread overview]
Message-ID: <> (raw)

Eric S Fraga <> writes:

> On Tuesday,  1 Feb 2022 at 09:29, Eric Abrahamsen wrote:
>> (FTR that was Andy Cohen's work, not mine)
> Ah, yes, sorry Andy!
>> 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
>> to refresh?
> I've been re-reading the documentation and it does state you can set it
> for automatic rescan.  The problem now is figuring out how to create the
> group I want.  nnvirtual is very good for this as it's straightforward.
> nnselect is somewhat opaque.
> How do I create a group that combines all those nnml groups with the
> following pattern, for instance:
>    nnml\\+somename:mail\\.*
> ?

Right, that's what I was saying in my original message: I'm pretty sure
this is possible, but I don't know the correct syntax. Once that's
sorted out, then we could add a convenience function that makes
"virtual" style select groups easier to create.

I just fooled around with this and couldn't get it to work, so I'm
cc'ing Andy to see what he thinks.

Andy, do you have a recommendation for how to make an nnselect group
that works just the same as an nnvirtual group: i.e. simply collects
several other groups and dumps them into one big one?

I tried doing it using gnus-search, like this:

 "family" nil '((nnselect-specs
      (nnselect-function . gnus-search-run-query)
        (query . "*"))
        ("nnimap:NEA" "family.Dad" "family.Mom"))))))

But it gave me:

nnselect-request-update-info: Wrong type argument: consp, nil

Which I haven't looked into further. But maybe the right approach is a
custom 'nnselect-function, where the `nnselect-args is the list of
groups to combine, and then the function just... returns all the
articles in those groups? Or something?

Thanks for any hints!


             reply	other threads:[~2022-02-01 18:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-01 18:46 Eric Abrahamsen [this message]
2022-02-01 22:21 ` Eric S Fraga
2022-03-03 16:56   ` dal-blazej
2022-03-07  0:39     ` Andrew Cohen
  -- strict thread matches above, loose matches on Subject: below --
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
2022-02-01 17:38       ` 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:

* 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).