From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: eLisp fontlock with mmm-mode
Date: Wed, 03 Sep 2003 11:02:38 -0600 [thread overview]
Message-ID: <3F561EAE.3030506@yahoo.com> (raw)
In-Reply-To: 151bebc0.0309030659.7ff80bb@posting.google.com
Joe Kelsey wrote:
> Aside from that, support for mixed-mode buffers suffers in Emacs due
> to limitations on the ability of using syntax tables for multiple
> purposes in a buffer. The design of syntax tables implies that a
> single syntax table controls an entire buffer in a single style.
> mmm-mode attempts to get around this by "dynamically" switching syntax
> tables as the point moves through various areas of a buffer. One very
> noticable side effect involves the fact that when you set up the
> syntax table for a particular sub-buffer, it changes the entire buffer
> view. Until someone comes up with a way to regionalize syntax tables,
> you just have to live with the "bleeding" of syntax table-based
> font-locks between buffer regions.
I thought that had already been done; from the Special Properties node
of the Emacs Lisp manual:
| Properties with Special Meanings
| --------------------------------
|
| Here is a table of text property names that have special built-in
| meanings. The following sections list a few additional special property
| names that control filling and property inheritance. All other names
| have no standard meaning, and you can use them as you like.
...
| `syntax-table'
| The `syntax-table' property overrides what the syntax table says
| about this particular character. *Note Syntax Properties::.
--
Kevin Rodgers
next prev parent reply other threads:[~2003-09-03 17:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.34.1062553939.18171.help-gnu-emacs@gnu.org>
2003-09-03 14:59 ` eLisp fontlock with mmm-mode Joe Kelsey
2003-09-03 17:02 ` Kevin Rodgers [this message]
2003-09-05 15:02 ` Joe Kelsey
2003-09-11 22:28 ` Alan Mackenzie
2003-09-12 15:46 ` Joe Kelsey
2003-09-12 21:55 ` Alan Mackenzie
2003-09-12 22:39 ` Stefan Monnier
2003-09-03 0:41 Sam Vilain
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=3F561EAE.3030506@yahoo.com \
--to=ihs_4664@yahoo.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).