From: Serghei <egrep@protonmail.ch>
To: David Engster <deng@randomsample.de>
Cc: GNU Emacs Developers <emacs-devel@gnu.org>
Subject: Re: Font Locking issue: Need help/advice
Date: Sun, 05 Apr 2020 14:37:05 +0000 [thread overview]
Message-ID: <o_PnRS-H5GtBYAhGD3W3-xmamGsgmlXhFhVfzfI2tSLGjQAAEJgQ2mXiOzGpM-Ju-kmJSOCgSq3rlLjhHnWCIO55ashzCDHevUBbbc9G3t0=@protonmail.ch> (raw)
In-Reply-To: <877dyw2o3a.fsf@randomsample>
> > - What happens on the GIF? How I can fix this? How to avoid similar
> > in the future?
> >
>
> What happens here is that the initial font-lock goes over the whole
> currently visible section, but as soon as you edit one line, font-lock
> will be called only for the part of the buffer that has changed, and it
> seems your font-lock rules work differently in this case because the
> context has changed.
Although I didn't receive answers to all my questions in this
thread, your suggestion about inconsistent font-lock rules turned
out as a clue. I found that even if I delete all other font-lock
rules (except this one), the problem will still remain. And I
decided to refactor it from scratch. After more careful refactor of
this anchored font-lock matcher, I was able to optimize some of its
parts [1]. Now it works as expected. Thanks for the tip!
Well, parsing complex context sensitive languages with a bunch of
very weak regexes is not a good idea. Anchored font-lock matchers
certainly help but still seem like a complicated approach.
> For better understanding how font-lock actually works, I highly
> recommend using font-lock-studio
>
> https://github.com/Lindydancer/font-lock-studio
I have heard about this package several times over the past few
years. However, I still lack some simple instructions on how to
find font-lock issues using this package. Perhaps a small guide
with an example of finding font-lock problems would help.
[1]: https://github.com/zephir-lang/zephir-mode/pull/28/commits/52ff40451b565d3f4a10b30e9c71e136b7d60021
--
Serghei
prev parent reply other threads:[~2020-04-05 14:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 12:29 Font Locking issue: Need help/advice Serghei Iakovlev
2020-04-03 18:27 ` Stephen Leake
2020-04-03 22:20 ` Serghei
2020-04-04 0:21 ` Stephen Leake
2020-04-03 22:36 ` David Engster
2020-04-03 23:48 ` Yuan Fu
2020-04-05 14:37 ` Serghei [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='o_PnRS-H5GtBYAhGD3W3-xmamGsgmlXhFhVfzfI2tSLGjQAAEJgQ2mXiOzGpM-Ju-kmJSOCgSq3rlLjhHnWCIO55ashzCDHevUBbbc9G3t0=@protonmail.ch' \
--to=egrep@protonmail.ch \
--cc=deng@randomsample.de \
--cc=emacs-devel@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.