Gnus development mailing list
 help / color / mirror / Atom feed
From: "Loris Bennett" <loris.bennett@fu-berlin.de>
To: ding@gnus.org
Subject: Re: Gnus search engine returns "Group nnselect:nnselect-877cqbir7v.fsf contains no messages"
Date: Tue, 08 Aug 2023 14:59:11 +0200	[thread overview]
Message-ID: <87jzu5n10g.fsf@debian-BULLSEYE-live-builder-AMD64> (raw)
In-Reply-To: <87wmy63046.fsf@ericabrahamsen.net>

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> Husain Alshehhi <husain@alshehhi.io> writes:
>
>> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>>
>>> The search engine config is meant to go on your select method, I
>>> actually have no idea if it would take effect as a group parameter or
>>> not. But as a first step I would definitely try setting it on your
>>> select method instead.
>>
>> MU does not come with any config file that the user usually
>> manipulates. I also couldn't find examples online of users using mu with
>> gnus. I am not sure what the value would be if I were to set the config field.
>
> I just meant the "(gnus-search-engine gnus-search-mu)" config. That is
> supposed to go in your `gnus-secondary-select-methods' configuration,
> like:
>
> '(nnmaildir "foo"
>    (directory "/x/y/z")
>    (gnus-search-engine gnus-search-mu))
>
>

I am also experiencing the same error.  My configuration had been
working fine for years, but after updating Debian from 11 to 12 and
hence Emacs from 27.1 to 28.2 I now have this problem.  The issue
arises with both imap and nntp groups.

This is what appears in *Messages* with gnus-verbose set to 10:

  Retrieving newsgroup: nnselect:nnselect-87v8dpn1ch.fsf...
  Opening server fu_exchange
  Searching nnimap+fu_exchange:HPC...done
  Group nnselect:nnselect-87v8dpn1ch.fsf contains no messages

The group definitely contains messages and definitely contains messages
which contain the string I searched for.

Any ideas what I might have a look at?

Cheers,

Loris
 
-- 
This signature is currently under constuction.



  reply	other threads:[~2023-08-11  1:42 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-06  2:33 Husain Alshehhi
2023-08-07 23:26 ` Eric Abrahamsen
2023-08-08 12:59   ` Loris Bennett [this message]
2023-08-24 10:38     ` Julien Cubizolles
2023-08-25  5:58       ` Loris Bennett
2023-08-25 11:44         ` Julien Cubizolles
2023-08-25 12:30           ` Loris Bennett
2023-08-26 13:25       ` James Thomas
2023-08-26 13:51         ` James Thomas
2023-08-26 15:54           ` Eric Abrahamsen
2023-08-26 15:52       ` Eric Abrahamsen
2023-08-26 16:26       ` Julien Cubizolles
2023-08-30 21:49         ` Eric Abrahamsen
  -- strict thread matches above, loose matches on Subject: below --
2023-09-12  4:55 Husain Alshehhi
2023-08-10  3:08 Husain Alshehhi
2023-08-09  0:43 Husain Alshehhi
2023-08-09  0:42 Husain Alshehhi
2023-08-09  3:13 ` Eric Abrahamsen
2023-08-06  2:30 Husain Alshehhi
2023-08-07 23:27 ` Eric Abrahamsen
2023-08-06  2:28 Husain Alshehhi
2023-08-04  0:48 husain
2023-08-04  1:07 ` John Haman
2023-08-04  6:16 ` Gijs Hillenius
2023-08-04  8:16 ` Eric S Fraga
2023-08-04  8:23 ` Eric S Fraga
2023-08-05  1:13 ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87jzu5n10g.fsf@debian-BULLSEYE-live-builder-AMD64 \
    --to=loris.bennett@fu-berlin.de \
    --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).