GNU bug report logs -
#77732
grep-edit-buffer errors with incionsistent behaviour
Previous Next
Full log
View this message in rfc822 format
> From: Visuwesh <visuweshm <at> gmail.com>
> Cc: johann.hoechtl <at> gmail.com, 77732 <at> debbugs.gnu.org
> Date: Fri, 11 Apr 2025 21:42:51 +0530
>
> [வெள்ளி ஏப்ரல் 11, 2025] Eli Zaretskii wrote:
>
> >> From: Visuwesh <visuweshm <at> gmail.com>
> >> Cc: Johann Höchtl <johann.hoechtl <at> gmail.com>,
> >> 77732 <at> debbugs.gnu.org
> >> Date: Fri, 11 Apr 2025 18:01:27 +0530
> >>
> >> I inserted a few message statements (see patch below), and I cannot
> >> figure out where the sudden addition in the compilation-message is
> >> coming from.
> >
> > Which addition is that? I'm afraid you lost me here.
>
> Oops, I butchered the statement: after the second time you type 'e', the
> "Grep finished..." message attains a non-nil compilation-message
> text-property.
>
> > Can you explain which line of code causes the error, and why?
>
> That's what I tried to figure out by adding the message statements but I
> fail to understand how the compilation-message text-property is being
> Added. The relevant bits from *Messages* is at the end.
>
> When I say 'e' for the first time then go back to grep-mode with C-c
> C-c, there's no extra compilation-message text-property.
>
> 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)?
Maybe you should do something with font-lock-extra-managed-props?
This bug report was last modified 24 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.