From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Alexandr Vityazev <avityazev@posteo.org>
Cc: ding@gnus.org
Subject: Re: Help testing gnus-search fixups
Date: Sat, 24 Jul 2021 15:16:39 -0700 [thread overview]
Message-ID: <87h7gj9x2w.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87bl6sual8.fsf@posteo.org> (Alexandr Vityazev's message of "Fri, 23 Jul 2021 18:52:19 +0000")
On 07/23/21 18:52 PM, Alexandr Vityazev wrote:
> On 2021-07-23, 08:18 -0700, Eric Abrahamsen <eric@ericabrahamsen.net> wrote:
>
>> On 07/23/21 13:12 PM, Alexandr Vityazev wrote:
>>> Hi!
>>>
>>> GNU Emacs 28.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.24,
>>> cairo version 1.16.0). Gnus v5.13.
>>>
>>> I tested the new version of gnus-search-indexed-parse-output yesterday
>>> and the search with notmuch completely fails. gnus-verbose is set to
>>> 10. press GG and type any search query, with the patch, I get:
>>>
>>> Doing /home/akagi/.guix-profile/bin/notmuch query on
>>> (nnmaildir+posteo:Drafts nnmaildir+posteo:Inbox nnmaildir+posteo:Sent
>>> nnmaildir+posteo:Trash nnmaildir+posteo:Notes)...
>>> Group nnselect:nnselect-87lf5xus2s.fsf contains no messages
>>
>> Hi, thanks for the report. Would you mind running your query on the
>> command line (using the same syntax as gnus-search does, mostly
>> output=files), and sending me the resulting list of file names
>> (off-list, if you prefer). I'll try to find out why the parsing process
>> is failing.
>>
>>
> notmuch search --output=files test
>
>
>
> in *Group* GG with "test" query, I get:
>
> Doing /home/akagi/.guix-profile/bin/notmuch query on
> (nnmaildir+posteo:Drafts nnmaildir+posteo:Inbox nnmaildir+posteo:Sent
> nnmaildir+posteo:Trash nnmaildir+posteo:Notes nnmaildir+posteo:Junk)...
> Group nnselect:nnselect-87czr8uasp.fsf contains no messages
Hmm, I'm not able to reproduce this: it's a little difficult since I
don't actually have the files on my machine, but as far as I can tell
the search results are being parsed correctly. Are you familiar with
edebug at all? Is there any chance I could get you to step through the
function and see where things are going off?
Thanks,
Eric
next prev parent reply other threads:[~2021-07-24 22:17 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-28 16:42 Eric Abrahamsen
2021-06-28 18:00 ` Adam Sjøgren
2021-06-28 23:15 ` Eric Abrahamsen
2021-06-29 6:04 ` Thomas Alexander Gerds
2021-06-29 9:30 ` Adam Sjøgren
2021-06-29 9:55 ` Adam Sjøgren
2021-06-29 11:03 ` Thomas Alexander Gerds
2021-06-29 11:13 ` Adam Sjøgren
2021-06-29 11:25 ` Adam Sjøgren
2021-06-30 16:58 ` Eric Abrahamsen
[not found] ` <87bl6tuqcb.fsf@posteo.org>
2021-07-23 15:18 ` Eric Abrahamsen
[not found] ` <87bl6sual8.fsf@posteo.org>
2021-07-24 22:16 ` Eric Abrahamsen [this message]
2021-07-25 11:17 ` Alexandr Vityazev
2021-07-25 22:11 ` Eric Abrahamsen
2021-07-30 18:17 ` Joseph Mingrone
2021-07-30 18:22 ` Joseph Mingrone
2021-07-30 18:47 ` Eric Abrahamsen
2021-07-30 19:29 ` Joseph Mingrone
2021-07-30 20:23 ` Eric Abrahamsen
2021-07-30 19:34 ` Alexandr Vityazev
2021-07-30 20:25 ` Eric Abrahamsen
2021-08-05 17:15 ` Eric Abrahamsen
2021-08-05 19:54 ` Alexandr Vityazev
2021-08-05 20:19 ` Joseph Mingrone
2021-08-05 21:24 ` Eric Abrahamsen
2021-08-05 21:38 ` Joseph Mingrone
2021-08-07 16:07 ` Eric Abrahamsen
2021-08-10 7:32 ` Daniel Jensen
2021-08-13 16:50 ` Eric Abrahamsen
2021-08-13 19:30 ` Daniel Jensen
2021-08-13 19:37 ` Eric Abrahamsen
2021-06-29 11:27 ` Eric S Fraga
2021-09-11 13:29 Sergey Makarov
2021-09-11 15:04 ` 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=87h7gj9x2w.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=avityazev@posteo.org \
--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).