From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Britt Anderson <britt@uwaterloo.ca>
Cc: Britt Anderson <britt@b3l.xyz>,
"66885@debbugs.gnu.org" <66885@debbugs.gnu.org>
Subject: bug#66885: 29.1; gnus search with mu always returns empty
Date: Sun, 19 Nov 2023 11:46:43 -0800 [thread overview]
Message-ID: <87y1eto7a4.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87il65g1uz.fsf@uwaterloo.ca> (Britt Anderson's message of "Mon, 13 Nov 2023 14:33:07 +0000")
Britt Anderson <britt@uwaterloo.ca> writes:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> Your configuration looks correct (your configuration also reveals an
>> annoying redundancy in gnus-search, which is that most nnmail
>> backends have a "directory" value that can and should be used as the
>> value of remove-prefix).
>>
>> Basically, if you're seeing "a maildir "y2023" that lives in archives"
>> as a Gnus group, then this is just a bug in gnus-search's mu handling,
>> plain and simple.
>
> I think the bug starts on line 1952 of gnus-search.el.gz (when opened in
> emacs). It is in the definition of the method for
(Thank you for continuing to bug-hunt, this looks promising, I've just
gotten back from traveling and will set this up to test soon...)
next prev parent reply other threads:[~2023-11-19 19:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 15:01 bug#66885: 29.1; gnus search with mu always returns empty Britt Anderson
2023-11-01 19:19 ` Eric Abrahamsen
2023-11-01 19:28 ` Britt Anderson
2023-11-02 14:10 ` Eric Abrahamsen
2023-11-03 14:33 ` Britt Anderson
2023-11-03 23:32 ` Eric Abrahamsen
2023-11-06 21:33 ` Britt Anderson
2023-11-07 3:47 ` Eric Abrahamsen
2023-11-13 14:33 ` Britt Anderson
2023-11-19 19:46 ` Eric Abrahamsen [this message]
2024-01-01 2:53 ` Eric Abrahamsen
[not found] ` <ZZgtJ8-cgJKEaE-D@joy>
2024-01-09 21:29 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y1eto7a4.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=66885@debbugs.gnu.org \
--cc=britt@b3l.xyz \
--cc=britt@uwaterloo.ca \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).