GNU bug report logs - #46047
28.0.50; Namazu-based mail searching not working anymore

Previous Next

Package: emacs;

Reported by: Torsten Bronger <bronger <at> physik.rwth-aachen.de>

Date: Sat, 23 Jan 2021 05:09:01 UTC

Severity: normal

Found in version 28.0.50

Done: Eric Abrahamsen <eric <at> ericabrahamsen.net>

Bug is archived. No further changes may be made.

Full log


Message #56 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Eric Abrahamsen <eric <at> ericabrahamsen.net>
To: bug-gnu-emacs <at> gnu.org
Subject: Re: bug#46047: 28.0.50; Namazu-based mail searching not working
 anymore
Date: Mon, 17 May 2021 11:53:27 -0700
Torsten Bronger <bronger <at> 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.




This bug report was last modified 4 years ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.