From: "Daniel Martín" <mardani29@yahoo.es>
To: Konstantin Kharlamov <hi-angel@yandex.ru>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Which "on change" hooks `smerge-mode` hooks up to?
Date: Thu, 01 Jun 2023 13:35:00 +0200 [thread overview]
Message-ID: <m1r0qvfmaj.fsf@yahoo.es> (raw)
In-Reply-To: <6a3912855e18f2e6307e996996c4b19603568f9e.camel@yandex.ru> (Konstantin Kharlamov's message of "Wed, 31 May 2023 16:26:18 +0300")
Konstantin Kharlamov <hi-angel@yandex.ru> writes:
> I spent some hours trying to debug a problem with highlight getting stuck and I
> figured, might just ask at this point more acknowledgeable people.
>
> Problem I debug is basically, that in certain conditions a conflict marker
> highlight gets stuck even after the marker was removed.
>
> I figured that I probably need smerge-mode to rescan the buffer if the buffer
> was reverted (that only happens when autorevert is enabled). I presume smerge-
> mode already does it because it usually removes highlight upon manually removing
> conflict markers. And that logic probably has some bug in it.
>
> 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.
Also, if you have some steps to reproduce it, you could also create a
bug report by using M-x report-emacs-bug. Thanks.
next prev parent reply other threads:[~2023-06-01 11:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 13:26 Which "on change" hooks `smerge-mode` hooks up to? Konstantin Kharlamov
2023-06-01 11:35 ` Daniel Martín [this message]
2023-06-14 11:49 ` Konstantin Kharlamov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m1r0qvfmaj.fsf@yahoo.es \
--to=mardani29@yahoo.es \
--cc=emacs-devel@gnu.org \
--cc=hi-angel@yandex.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).