GNU bug report logs - #77732
grep-edit-buffer errors with incionsistent behaviour

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: "Paul D. Nelson" <ultrono <at> gmail.com>
Cc: johann.hoechtl <at> gmail.com, 77732 <at> debbugs.gnu.org, visuweshm <at> gmail.com
Subject: bug#77732: grep-edit-buffer errors with incionsistent behaviour
Date: Sat, 19 Apr 2025 17:18:10 +0300

> From: "Paul D. Nelson" <ultrono <at> gmail.com>
> Cc: visuweshm <at> gmail.com, johann.hoechtl <at> gmail.com, 77732 <at> debbugs.gnu.org
> Date: Sun, 13 Apr 2025 10:01:25 +0200
> 
> Here's a reliable recipe that produces what I suspect is the key issue:
> 
> ----------------------------------------
> emacs -Q
> 
> Disable global-font-lock-mode.
> 
> Use rgrep in any situation that returns some match.  (The emacs source
> tree works, as does a dummy folder containing "test.txt" with a single
> line "foo".)
> 
> In the *grep* buffer, press n.
> ----------------------------------------
> 
> After this, the line "Grep finished ..." has the compilation-message
> text property, which should not happen.
> 
> The erroneous property gets added in compilation-parse-errors in the
> final "add-text-properties", apparently because the regexp used to
> detect matches picks up the "Grep finished..." line.

Thanks, but can you be more specific?  Which regexp is that, and why
does it match "Grep finished..." only sometimes?

Previous Next

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