From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: 46047@debbugs.gnu.org
Subject: bug#46047: 28.0.50; Namazu-based mail searching not working anymore
Date: Mon, 17 May 2021 11:53:27 -0700 [thread overview]
Message-ID: <87o8d9xkd4.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87pmxpdhjb.fsf@physik.rwth-aachen.de> (Torsten Bronger's message of "Mon, 17 May 2021 08:02:32 +0200")
Torsten Bronger <bronger@physik.rwth-aachen.de> writes:
> Hallöchen!
>
> Eric Abrahamsen writes:
>
>> [...]
>>
>> I'm assuming you've also got `gnus-search-namazu-raw-queries-p'
>> set to t, otherwise you would have hit an error earlier than this.
>
> No, but I did now.
Oh, maybe you just had `gnus-search-use-parsed-queries' set to nil. One
way or another, the query must not be getting parsed. But that's fine!
>> [...]
>>
>> Earlier in the day I pushed a change to Emacs master to use
>> `condition-case-unless-debug' in `nnselect-run'. If you're in the
>> habit of running a recent Emacs, would you pull from source and
>> rebuild, then `toggle-debug-on-error' and run this search again,
>> posting the backtrace?
>
> Debugger entered--Lisp error: (wrong-type-argument stringp nil)
> file-readable-p(nil)
This just means that when namazu returns its search results, this
function fails to find a filename. In other words, the (match-string 4)
returns nil.
(cl-defmethod gnus-search-indexed-extract ((_engine gnus-search-namazu))
"Extract a single message result for Namazu.
Namazu provides a little more information, for instance a score."
(when (re-search-forward
"^\\([0-9,]+\\.\\).*\\((score: \\([0-9]+\\)\\))\n\\([^ ]+\\)"
nil t)
(forward-line 1)
(list (match-string 4)
(match-string 3))))
Using the example results that you send me (the bash script) the file
names are found correctly. Is there a way you can find and show me the
filename that isn't being found by this regexp? I assume it's a filename
that doesn't start with a digit. I'm not sure where this regexp came
from, originally.
next prev parent reply other threads:[~2021-05-17 18:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-23 5:07 bug#46047: 28.0.50; Namazu-based mail searching not working anymore Torsten Bronger
2021-01-23 17:42 ` Eric Abrahamsen
2021-01-23 20:17 ` Torsten Bronger
2021-01-23 22:14 ` Eric Abrahamsen
2021-01-23 22:26 ` Eric Abrahamsen
2021-01-25 10:10 ` Torsten Bronger
2021-02-07 22:02 ` Eric Abrahamsen
2021-02-12 13:53 ` Torsten Bronger
2021-02-12 15:25 ` Torsten Bronger
2021-04-21 3:19 ` Stefan Kangas
2021-05-09 14:21 ` Torsten Bronger
2021-05-12 18:18 ` Eric Abrahamsen
2021-05-16 17:24 ` Eric Abrahamsen
2021-05-16 19:43 ` Torsten Bronger
2021-05-16 22:11 ` Eric Abrahamsen
2021-05-17 6:02 ` Torsten Bronger
2021-05-17 18:53 ` Eric Abrahamsen [this message]
2021-05-18 8:46 ` Torsten Bronger
2021-05-18 9:08 ` Eli Zaretskii
2021-05-18 16:50 ` Eric Abrahamsen
2021-05-18 16:55 ` Eli Zaretskii
2021-05-21 17:47 ` Eric Abrahamsen
2021-05-21 19:10 ` Torsten Bronger
2021-05-21 20:38 ` Eric Abrahamsen
2021-01-23 22:30 ` 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=87o8d9xkd4.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=46047@debbugs.gnu.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.
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).