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

Previous Next

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Visuwesh <visuweshm <at> gmail.com>
Cc: johann.hoechtl <at> gmail.com, 77732 <at> debbugs.gnu.org
Subject: Re: bug#77732: grep-edit-buffer errors with incionsistent behaviour
Date: Sun, 13 Apr 2025 09:03:56 +0300

> From: Visuwesh <visuweshm <at> gmail.com>
> Cc: johann.hoechtl <at> gmail.com,  77732 <at> debbugs.gnu.org
> Date: Sat, 12 Apr 2025 20:23:45 +0530
> 
> [சனி ஏப்ரல் 12, 2025] Eli Zaretskii wrote:
> 
> > [...]
> >> >> When I say 'e' for the second time around, till the end of
> >> >> grep-change-to-grep-edit-mode, there's no extra compilation-message
> >> >> text-property (lines marked with *).  But in the gap between
> >> >> grep-change-to-grep-edit-mode and me saying C-c C-c (with no other
> >> >> action being done by me in between), the extra compilation-message
> >> >> text-property is added to the "Grep finished..." line.
> >> >
> >> > I'm guessing this is font-lock (called via jit-lock mechanism)?
> >> 
> >> That may be the case...
> >> 
> >> > Maybe you should do something with font-lock-extra-managed-props?
> >> 
> >> Just pushing 'compilation-message to font-lock-extra-managed-props did
> >> not help.  Unfortunately, I do not know enough to debug this one.
> >
> > And it doesn't help that it is a heisenbug: I could only reproduce it
> > once, even with your recipe.
> 
> I can reproduce it every time I repeat the recipe.  Does it help to use
> M-x rgrep instead?

No.

Previous Next

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