From: Perry Smith <pedz@easesoftware.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: State-machine based syntax highlighting
Date: Thu, 7 Dec 2006 14:24:25 -0600 [thread overview]
Message-ID: <2FCD3A38-5454-4F04-B4F3-E3E3AFC65F81@easesoftware.com> (raw)
In-Reply-To: <1165517838.526624.171950@f1g2000cwa.googlegroups.com>
[-- Attachment #1.1: Type: text/plain, Size: 1168 bytes --]
On Dec 7, 2006, at 12:57 PM, Robert Thorpe wrote:
> spamfilteraccount@gmail.com wrote:
>> Stefan Monnier wrote:
>>>
>>> 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.
>>
>> Good to know. I thought font-lock was implemented in elisp and didn't
>> bother to check.
>
> Precisely speaking...
> The code that determines what rules are used to font-lock text is in
> Elisp.
> The regexp engine that finds the things to be font-locked is in the
> core of Emacs.
> The colourisation is implemented in the Emacs core.
Instead of a state machine, how about a lalr parser? It would be a fun
project to take the lalr table generation logic from bison, smash it
into emacs, along with some predefined actions and hooks back
into emacs. The grammers could be loaded when needed.
Perry Smith ( pedz@easesoftware.com )
Ease Software, Inc. ( http://www.easesoftware.com )
Low cost SATA Disk Systems for IBMs p5, pSeries, and RS/6000 AIX systems
[-- Attachment #1.2: Type: text/html, Size: 6796 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-07 20:24 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
[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 [this message]
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=2FCD3A38-5454-4F04-B4F3-E3E3AFC65F81@easesoftware.com \
--to=pedz@easesoftware.com \
--cc=help-gnu-emacs@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.
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).