From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Clément Pit--Claudel" <clement.pitclaudel@live.com>
Cc: 25672@debbugs.gnu.org
Subject: bug#25672: Font-locking issues when font-lock-fontified is nil
Date: Wed, 30 Oct 2019 17:09:59 +0100 [thread overview]
Message-ID: <8736farz8o.fsf@gnus.org> (raw)
In-Reply-To: <877e4mrzdd.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 30 Oct 2019 17:07:10 +0100")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> I think this was fixed last year-ish if I'm reading the change log
> correctly.
Oh, I didn't. This is the definition of that function:
(defun font-lock-fontify-region (beg end &optional loudly)
"Fontify the text between BEG and END.
If LOUDLY is non-nil, print status messages while fontifying.
This works by calling `font-lock-fontify-region-function'."
(font-lock-set-defaults)
(funcall font-lock-fontify-region-function beg end loudly))
which is indeed font-lock-default-fontify-region, which is what was
requested to have changed.
I think?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-10-30 16:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 21:22 bug#25672: Font-locking issues when font-lock-fontified is nil (Was: What to do when font-lock-flush + font-lock-ensure do less than font-lock-fontify-buffer? on emacs-devel) Clément Pit--Claudel
2019-10-30 16:07 ` bug#25672: Font-locking issues when font-lock-fontified is nil Lars Ingebrigtsen
2019-10-30 16:09 ` Lars Ingebrigtsen [this message]
2021-08-14 14:17 ` bug#25672: Font-locking issues when font-lock-fontified is nil (Was: What to do when font-lock-flush + font-lock-ensure do less than font-lock-fontify-buffer? on emacs-devel) Lars Ingebrigtsen
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=8736farz8o.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=25672@debbugs.gnu.org \
--cc=clement.pitclaudel@live.com \
/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).