GNU bug report logs - #64063
smerge-mode highlight gets stuck if buffer autoreverted "delicately"

Previous Next

Full log

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

From: Konstantin Kharlamov <hi-angel <at> yandex.ru>
To: 64063 <at> debbugs.gnu.org
Cc: mardani29 <at> yahoo.es, emacs-devel <at> gnu.org
Subject: smerge-mode highlight gets stuck if buffer autoreverted "delicately"
Date: Sat, 17 Jun 2023 03:16:32 +0300

On Thu, 2023-06-01 at 13:35 +0200, Daniel Martín wrote:
> > So, my question is, what "on change" hooks smerge-mode uses to detect that a
> > change to the buffer has been made to check whether conflict markers are still
> > in place? I tried searching for the word "hook" over the smerge-mode.el but
> > didn't find anything relevant.
>
> If font-lock is enabled, smerge-mode uses it to fontify the conflicting
> regions.  See smerge-font-lock-keywords.  So perhaps the regular
> font-lock debugging techniques might help you investigate this issue in
> more detail.

So, I think the problem is that the highlight that gets stuck does not use font-lock,
or at least not through means of `smerge-font-lock-keywords`. Whatever is defined in
`smerge-font-lock-keywords` gets unhighlighted correctly. But the part that gets
stuck instead is an overlay.

So I presume besides font-lock-mode there's some other highlight management ongoing,
the one that decides whether to put/remove overlays over some text.

Previous Next

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