From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Britt Anderson <britt@b3l.xyz>
Cc: 66885@debbugs.gnu.org
Subject: bug#66885: 29.1; gnus search with mu always returns empty
Date: Wed, 01 Nov 2023 12:19:04 -0700 [thread overview]
Message-ID: <877cn19t93.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87sf5ppkx9.fsf@b3l.xyz> (Britt Anderson's message of "Wed, 01 Nov 2023 11:01:02 -0400")
Britt Anderson <britt@b3l.xyz> writes:
> Using gnus and the mu search engine always returns an empty search. This
> is despite the fact that mu on the command line works, and that search
> in mu4e works.
Thanks for the report.
> I noted that there was a bug report for something similar in #54162 for
> notmuch search, but that was apparently due to an empty server name,
> which is not the case for me.
>
> I will note that if I run from the command line a command like:
>
> mu find --clearlinks --format=links --linksdir=/home/britt/.local/share/mail/search/ 55214
Gnus' code will construct a command line like this:
mu find --nocolor --muhome=~/.cache/mu <QUERY HERE> --format=plain --fields=l
Would you try running this with a sample query, and sending a sample
output (I hope it's just a list of file names). That should help narrow
down whether it's a problem sending the query in, or a problem parsing
the output.
Thanks,
Eric
next prev parent reply other threads:[~2023-11-01 19:19 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 [this message]
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
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=877cn19t93.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=66885@debbugs.gnu.org \
--cc=britt@b3l.xyz \
/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).