unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: State-machine based syntax highlighting
Date: Thu, 07 Dec 2006 12:42:29 -0500	[thread overview]
Message-ID: <jwvpsav8v22.fsf-monnier+gnu.emacs.help@gnu.org> (raw)
In-Reply-To: <1165510932.276718.251220@73g2000cwn.googlegroups.com> (spamfilteraccount@gmail.com's message of "7 Dec 2006 09\:02\:12 -0800")

>> > I did a quick search and found this page
>> > http://harmonia.cs.berkeley.edu/harmonia/projects/harmonia-mode/doc/index.html
>> > with a demo xemacs package with syntax highlighting and stuff. Looked
>> > interesting.
>> Interesting.
> I wondered why they supported xemacs only, so I downloaded the source.
> Seems they wrote xemacs extensions in c which have to be compiled into
> xemacs.

> Not a usual way to extend an emacs, but probably advantageous from a
> performance point of view.

> The idea already occured to me that font locking should be implemented
> in pure c in emacs for speed, but I guess it's kind of against the
> extensible editor concept or something.

Actually, font-locking *is* implemented in C.  The elisp part usually takes
a negligible amount of time.  The problem start appearing when the
functionality of the C code is not sufficient and you start trying to parse
the code in elisp, which is slow.


        Stefan

  reply	other threads:[~2006-12-07 17:42 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-07  6:14 State-machine based syntax highlighting spamfilteraccount
2006-12-07 10:53 ` Robert Thorpe
2006-12-07 11:56   ` spamfilteraccount
2006-12-07 12:42     ` Robert Thorpe
2006-12-07 14:27       ` spamfilteraccount
2006-12-07 14:39         ` Robert Thorpe
2006-12-07 17:02           ` spamfilteraccount
2006-12-07 17:42             ` Stefan Monnier [this message]
     [not found]             ` <mailman.1644.1165513359.2155.help-gnu-emacs@gnu.org>
2006-12-07 18:35               ` spamfilteraccount
2006-12-07 18:57                 ` Robert Thorpe
2006-12-07 20:24                   ` Perry Smith
2006-12-08  7:33                   ` spamfilteraccount
2006-12-08  8:10                     ` Tim X
2006-12-08  8:36                       ` spamfilteraccount
2006-12-08 16:17                         ` Robert Thorpe
2006-12-08 21:14                           ` spamfilteraccount
2006-12-09  2:08                             ` Stefan Monnier
2006-12-09  2:06                           ` Stefan Monnier
2006-12-09  3:24                             ` Lennart Borgman
2006-12-08 13:14                       ` Leo
2006-12-08 14:00                       ` Robert Thorpe
2006-12-09  2:10                         ` Stefan Monnier
     [not found]                       ` <mailman.1672.1165586758.2155.help-gnu-emacs@gnu.org>
2006-12-08 14:17                         ` Robert Thorpe
2006-12-08 21:17                       ` spamfilteraccount
     [not found]                   ` <mailman.1653.1165523111.2155.help-gnu-emacs@gnu.org>
2006-12-08 10:01                     ` Robert Thorpe
2006-12-07 19:02                 ` Stefan Monnier
2006-12-07 19:29                   ` spamfilteraccount
2006-12-08 14:43                     ` Robert Thorpe

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=jwvpsav8v22.fsf-monnier+gnu.emacs.help@gnu.org \
    --to=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.
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).