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


View this message in rfc822 format

From: Eric Abrahamsen <eric <at> ericabrahamsen.net>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 46047 <at> debbugs.gnu.org, bronger <at> physik.rwth-aachen.de
Subject: bug#46047: 28.0.50; Namazu-based mail searching not working anymore
Date: Tue, 18 May 2021 09:50:00 -0700
Eli Zaretskii <eliz <at> gnu.org> writes:

> On May 18, 2021 11:46:52 AM GMT+03:00, Torsten Bronger
> <bronger <at> physik.rwth-aachen.de> wrote:
>> Hallöchen!
>> 
>> Eric Abrahamsen writes:
>> 
>> > [...]
>> >
>> >>> [...]
>> >>>
>> >>> 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.
>> 
>> I made some progress with this.  The buffer containing namazu’s
>> output contains trailing garbage on my system.  The tailing string
>> is: "Process search-nnml: finished".  This cannot be matched, of
>> course, which makes everything fail.
>> 
>> I don’t know where this comes from, though.
>> 
>> Regards,
>> Torsten.
>
> I think it's process exit status notification and comes from the
> process sentinel function.

Huh, I'm surprised this hasn't been an issue before, then. It looks like
that message is standard for any start-process/accept-process-output
situation. Is there any way to shut it off?

Regardless, the output parsing shouldn't be so fragile that it chokes on
this. I'll look into making it more robust.

Thanks,
Eric




This bug report was last modified 4 years and 1 day ago.

Previous Next


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