unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Colin Walters <walters@gnu.org>
Subject: Re: new text property
Date: 10 Jun 2002 01:46:22 -0400	[thread overview]
Message-ID: <1023687982.1593.1326.camel@space-ghost> (raw)
In-Reply-To: <87y9dnycw8.fsf@tleepslib.sk.tsukuba.ac.jp>

On Mon, 2002-06-10 at 00:29, Stephen J. Turnbull wrote:

> Er, as I understood that thread, the rationale is that font-lock is
> too heavy (aka "slow and broken") to be used by modes that just want
> some "light-weight" highlighting.  Is that not so?  Are there other
> advantages to not using font-lock to do font-locking?<wink>

The font-lock you are thinking of is regexp and search-based
fontification, both of which can be slow (and in the case of regexps
quite often broken).  

But typing 'M-x font-lock-mode' is a nice *interface* to enabling and
disabling fontification.  It doesn't mean the mode has to use regexp or
search-based fontification.  In Emacs we now have "font-core.el", which
just defines the bare bones of `font-lock-mode' and
`global-font-lock-mode'.  It allows a mode (like `occur') which uses the
new `font-lock-face' to allow its fontification to be toggled via M-x
font-lock-mode, without loading all of the regexp and other machinery of
font-lock.el.

> I think we should look into allowing all highlighting to be done by
> font-lock by making font-lock performance better.  

The performance of `font-lock-face' in Emacs is essentially equivalent
to that of the `face' property; i.e. it is not an issue.  I suspect you
could easily achieve the same results in XEmacs.

  parent reply	other threads:[~2002-06-10  5:46 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-09  7:22 new text property Colin Walters
2002-06-10  4:29 ` Stephen J. Turnbull
     [not found] ` <87y9dnycw8.fsf@tleepslib.sk.tsukuba.ac.jp>
2002-06-10  5:12   ` Miles Bader
2002-06-10  5:46   ` Colin Walters [this message]
     [not found]   ` <buod6uzbtun.fsf@mcspd15.ucom.lsi.nec.co.jp>
2002-06-10  6:38     ` Stephen J. Turnbull
     [not found]     ` <87bsajy6y8.fsf@tleepslib.sk.tsukuba.ac.jp>
2002-06-10  6:53       ` Colin Walters
2002-06-10 14:30       ` Stefan Monnier
     [not found]       ` <200206101431.g5AEV0G28267@rum.cs.yale.edu>
2002-06-10 17:35         ` Adrian Aichner
2002-06-11  5:07           ` Eli Zaretskii
2002-06-11  8:24         ` Stephen J. Turnbull
2002-06-10  8:50 ` Hrvoje Niksic
2002-06-10 11:16   ` Kai Großjohann
2002-06-10 12:07     ` Hrvoje Niksic
2002-06-10 12:26       ` Miles Bader
2002-06-10 13:32         ` Hrvoje Niksic
2002-06-10 14:28           ` Stefan Monnier
2002-06-10 15:08           ` Kai Großjohann
2002-06-10 18:51           ` Colin Walters
     [not found]           ` <1023735066.26240.14.camel@space-ghost>
2002-06-11 11:40             ` Hrvoje Niksic
2002-06-11 19:47               ` Colin Walters
2002-06-11 20:40                 ` Hrvoje Niksic
2002-06-12  8:18                   ` Kai Großjohann
2002-06-12  9:05                     ` Miles Bader
2002-06-12  1:14                 ` Stephen J. Turnbull
     [not found]                 ` <877kl5pabc.fsf@tleepslib.sk.tsukuba.ac.jp>
2002-06-12  3:11                   ` Colin Walters
2002-06-12  8:16                     ` Stephen J. Turnbull
2002-06-12 17:46                       ` Adrian Aichner
2002-06-10 15:03       ` Kai Großjohann
     [not found]       ` <vaf1ybf18hp.fsf@INBOX.auto.emacs.devel.tok.lucy.cs.uni-dortmund.de>
2002-06-10 15:13         ` Hrvoje Niksic

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=1023687982.1593.1326.camel@space-ghost \
    --to=walters@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 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).