From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: emacs-devel@gnu.org
Subject: Re: What to do when font-lock-flush + font-lock-ensure do less than font-lock-fontify-buffer?
Date: Wed, 24 Feb 2016 21:17:14 +0200 [thread overview]
Message-ID: <838u29hq9x.fsf@gnu.org> (raw)
In-Reply-To: <jwv1t829byc.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Wed, 24 Feb 2016 13:55:42 -0500)
> From: Stefan Monnier <monnier@IRO.UMontreal.CA>
> Cc: emacs-devel@gnu.org
> Date: Wed, 24 Feb 2016 13:55:42 -0500
>
> > Actually, in this particular case I think this is a bug in
> > prettify-symbols-mode: it should define its own
> > font-lock-ensure-function. The default value doesn't cover the kind
> > of stuff that this mode uses font-lock for.
>
> Hmm... I don't see any reason why that should be the case.
> IOW I think that if a change is needed it should be font-lock.el because
> prettify-symbols-mode seems to be using font-lock in a "normal" way.
I'm not sure about this (this machinery and its implications were
never sufficiently documented, and what I think I know is the result
of a desperate attempt to document it). However, please explain why
font-lock-ensure-function calls font-lock-DEFAULT-fontify-buffer. If
it's supposed to be good for any mode, why does it call the default
fontification?
As a matter of fact, if I replace the font-lock-default-fontify-buffer
call with a call to font-lock-fontify-buffer, the problem described by
the OP goes away. That is why I said what I said.
next prev parent reply other threads:[~2016-02-24 19:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 4:55 What to do when font-lock-flush + font-lock-ensure do less than font-lock-fontify-buffer? Clément Pit--Claudel
2016-02-22 8:56 ` Anders Lindgren
2016-02-22 13:49 ` Clément Pit--Claudel
2016-02-22 15:53 ` Anders Lindgren
2016-02-22 16:13 ` Eli Zaretskii
2016-02-22 16:29 ` Clément Pit--Claudel
2016-02-22 16:35 ` Kaushal Modi
2016-02-22 16:40 ` Eli Zaretskii
2016-02-22 17:28 ` Clément Pit--Claudel
2016-02-23 16:57 ` Eli Zaretskii
2016-02-23 18:08 ` Clément Pit--Claudel
2016-02-24 3:52 ` Stefan Monnier
2016-02-24 17:12 ` Eli Zaretskii
2016-02-24 18:55 ` Stefan Monnier
2016-02-24 19:17 ` Eli Zaretskii [this message]
2016-02-24 20:09 ` Stefan Monnier
2016-04-09 18:59 ` Clément Pit--Claudel
2016-04-09 19:37 ` Eli Zaretskii
2016-04-09 19:54 ` Clément Pit--Claudel
2016-04-10 20:10 ` Stefan Monnier
[not found] ` <<jwv1t829byc.fsf-monnier+emacs@gnu.org>
[not found] ` <<838u29hq9x.fsf@gnu.org>
2016-02-24 19:20 ` Drew Adams
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=838u29hq9x.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
/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).