From: Alan Mackenzie <acm@muc.de>
To: Lars Ingebrigtsen <larsi@gnus.org>,
bug-cc-mode@gnu.org, emacs-devel@gnu.org
Subject: Re: Emacs revision #107149
Date: Mon, 13 Feb 2012 21:35:58 +0000 [thread overview]
Message-ID: <20120213213558.GD26954@acm.acm> (raw)
In-Reply-To: <85ipjbv96s.fsf@iznogoud.viz>
'evening, Wolfgang.
On Mon, Feb 13, 2012 at 02:00:43AM +0100, Wolfgang Jenkner wrote:
> On Sun, Feb 12 2012, Alan Mackenzie wrote:
> > But, do you actually have to suppress these support modes? They're there
> > to fontify text screens faster. Why disable them? Nowadays, with faster
> > HW than ever, it seems pointless even to bother.
> The buffer where the fontification happens is not displayed, instead its
> content is inserted in a buffer with a different major-mode, and in
> between emacs stays never idle for the font-lock support functions to
> kick in.
I'm not sure I've fully understood you here. Certainly in JIT lock mode
(the default under GNU Emacs), and probably under lazy-lock too, "no"
runtime is consumed until the buffer is displayed.
font-lock-fontify-buffer (without a support mode) will take some time,
sometimes quite a lot.
> Wolfgang
Alan Mackenzie (Nürnberg).
next prev parent reply other threads:[~2012-02-13 21:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 23:20 Emacs revision #107149 Alan Mackenzie
2012-02-11 15:56 ` Lars Ingebrigtsen
2012-02-11 18:07 ` Wolfgang Jenkner
2012-02-11 19:59 ` Alan Mackenzie
2012-02-12 20:42 ` Lars Ingebrigtsen
2012-02-12 22:22 ` Alan Mackenzie
2012-02-13 1:00 ` Wolfgang Jenkner
2012-02-13 21:35 ` Alan Mackenzie [this message]
2012-02-13 3:15 ` Stefan Monnier
2012-02-13 21:42 ` Alan Mackenzie
2012-02-13 22:18 ` Stefan Monnier
2012-02-13 21:03 ` Lars Ingebrigtsen
2012-02-13 22:07 ` Alan Mackenzie
2012-02-20 9:51 ` Lars Ingebrigtsen
2012-02-21 15:16 ` Alan Mackenzie
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=20120213213558.GD26954@acm.acm \
--to=acm@muc.de \
--cc=bug-cc-mode@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.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 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).