From: Mike Mattie <codermattie@gmail.com>
Subject: Re: font-lock support mode in emacs 22
Date: Tue, 5 Dec 2006 08:23:02 -0800 [thread overview]
Message-ID: <20061205082302.08a477fd@reforged> (raw)
In-Reply-To: <1165328561.281870.161210@73g2000cwn.googlegroups.com>
[-- Attachment #1.1: Type: text/plain, Size: 787 bytes --]
On 5 Dec 2006 06:22:41 -0800
"spamfilteraccount@gmail.com" <spamfilteraccount@gmail.com> wrote:
> I just checked in cvs
> (http://cvs.savannah.gnu.org/viewcvs/emacs/lisp/font-lock.el?rev=1.308&root=emacs&view=auto)
> that font-lock-support-mode is still 'jit-lock-mode in emacs 22.
>
> Is this still necessary? I mean we have pretty fast machines in these
> days, so couldn't emacs perform the fontification in realtime? Did the
> subject come up on emacs-devel during development of emacs 22?
I have a reasonably fast machine and it is still very necessary. Without
tuning jit emacs was unusable for me.
> _______________________________________________
> help-gnu-emacs mailing list
> help-gnu-emacs@gnu.org
> http://lists.gnu.org/mailman/listinfo/help-gnu-emacs
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 152 bytes --]
_______________________________________________
help-gnu-emacs mailing list
help-gnu-emacs@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gnu-emacs
next prev parent reply other threads:[~2006-12-05 16:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-05 14:22 font-lock support mode in emacs 22 spamfilteraccount
2006-12-05 16:23 ` Mike Mattie [this message]
2006-12-06 6:23 ` martin rudalics
2007-05-15 11:33 ` moueza
2006-12-06 18:12 ` Robert Thorpe
[not found] <mailman.1589.1165386266.2155.help-gnu-emacs@gnu.org>
2006-12-06 7:28 ` spamfilteraccount
-- strict thread matches above, loose matches on Subject: below --
2007-05-16 6:19 martin rudalics
[not found] <mailman.727.1179297182.32220.help-gnu-emacs@gnu.org>
2007-05-19 21:17 ` Ian J Cottee
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=20061205082302.08a477fd@reforged \
--to=codermattie@gmail.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.
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).