From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: Gnus search engine returns "Group nnselect:nnselect-877cqbir7v.fsf contains no messages"
Date: Wed, 30 Aug 2023 14:49:10 -0700 [thread overview]
Message-ID: <87ledsurop.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87a5udydlo.fsf@free.fr>
Julien Cubizolles <j.cubizolles@free.fr> writes:
> Julien Cubizolles <j.cubizolles@free.fr> writes:
>
>> "Loris Bennett" <loris.bennett@fu-berlin.de> writes:
>>
>>
>>> 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
>>>
>> Same problem here with Emacs 30.0.50.
>>
>> The relevant parts of my config are:
>>
>> (setq gnus-search-default-engines
>> '((nnml . gnus-search-notmuch)
>> (nntp . gnus-search-notmuch)
>> (nnimap . gnus-search-imap)
>> (nnfolder . gnus-search-notmuch)
>> (nndraft . gnus-search-notmuch)
>> (nnarchive . gnus-search-notmuch)
>> (nnselect . gnus-search-nnselect)
>> (nnmaildir . gnus-search-notmuch)))
>>
>> (setq gnus-search-use-parsed-queries t)
>>
>> (setq gnus-secondary-select-methods
>> '((nnmaildir "Academie" (directory "~/email/Maildir-mbsync/Academie")
>> (gnus-search-engine gnus-search-notmuch
>> (remove-prefix "~/email/Maildir-mbsync/Academie")))))
>>
>
> I finally got it working with :
>
> (nnmaildir "Academie"
> (directory "/home/wilk/email/Maildir-mbsync/Academie")
> (gnus-search-engine gnus-search-notmuch
> (remove-prefix "/home/wilk/email/Maildir-mbsync/Academie"))
>
> Don't know what's different except the explicit "/home/wilk/" instead of
> "~/". Maybe I tweaked something else under the hood during my various changes…
I'm glad it's working, though I sure hope that wasn't the problem, as I
went to some lengths to make it work with relative paths like this. If
at any point you confirm that this was the issue, I'd like to know so I
can go back and try again.
Thanks,
Eric
next prev parent reply other threads:[~2023-08-30 21:49 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
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 [this message]
-- 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=87ledsurop.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).