From: "Eric M. Ludlam" <eric@siege-engine.com>
To: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
Cc: sdl.web@gmail.com, emacs-devel@gnu.org, monnier@iro.umontreal.ca,
jasonr@gnu.org
Subject: Re[2]: Multiple major modes
Date: Tue, 12 Jun 2007 16:14:20 -0400 [thread overview]
Message-ID: <200706122014.l5CKEKV1021902@projectile.siege-engine.com> (raw)
In-Reply-To: <466EEA71.2070700@gmail.com> (lennart.borgman@gmail.com)
[ ... ]
>>> "Lennart Borgman (gmail)" <lennart.borgman@gmail.com> seems to think that:
>Stefan Monnier wrote:
>>> and something that should be addressed without imposing restrictions on
>>> specialized major modes.
>>
>> Actually, I think that in order to address it well, we will need to impose
>> restrictions on major modes (though only on the ones involved in
>> multiple-major-mode buffers) and maybe also on minor modes.
My parsing tool (semantic, referenced earlier) solved some problems w/
lots of mode-specific configurations via 'mode-local' variables and
methods. David Ponce wrote this, and suggested it here once before.
I don't recall what the end resolution was on it.
A multi-mode style thing would likely be simplified if key behaviors
were all defined via mode-local configurations, as that would allow
the multi-mode manager to get a complete query list of all
configuration differences without running the major-mode function.
http://cedet.cvs.sourceforge.net/cedet/cedet/common/mode-local.el?view=log
This tools has a spiff macro `with-mode-local', which lets you run a
bunch of code as if some other mode were active. This is used in our
grammar file so we can operate on grammar syntax w/ lisp syntax mixed
in. We can also operate on tags from other buffers by momentarily
using features of the originating major-mode.
Enjoy
Eric
>I think so to. I have seen some areas where some form of coherence is
>necessary:
>
>- fontification
>- indentation
>- parsing
>
>I think nxml-mode is a very good candidate for those that can be used in
>a multiple-major-mode buffers, since a mix of for example XHTML and PHP
>is common.
>
>This might seem impossible, since such code could not be valid XHTML.
>Actually it is not, the rng parser used in nxhtml-mode is quite good on
>guessing an apropriate state for completion. (But do not ask me what the
>rng parser does, I do not understand it.)
>
--
Eric Ludlam: zappo@gnu.org, eric@siege-engine.com
Home: http://www.ludlam.net Siege: www.siege-engine.com
Emacs: http://cedet.sourceforge.net GNU: www.gnu.org
next prev parent reply other threads:[~2007-06-12 20:14 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-11 23:27 Should nXML be included Leo
2007-06-12 10:50 ` Lennart Borgman (gmail)
2007-06-12 11:21 ` Jason Rumney
2007-06-12 12:57 ` Lennart Borgman (gmail)
2007-06-12 13:42 ` Peter Heslin
2007-06-12 14:20 ` Jason Rumney
2007-06-12 15:06 ` Multiple major modes (was: Should nXML be included) Stefan Monnier
2007-06-12 15:15 ` Multiple major modes Leo
2007-06-12 18:48 ` Lennart Borgman (gmail)
2007-06-12 20:14 ` Eric M. Ludlam [this message]
2007-06-12 21:04 ` Lennart Borgman (gmail)
2007-06-12 23:10 ` Stefan Monnier
2007-06-13 16:22 ` Richard Stallman
2007-06-13 16:22 ` Richard Stallman
2007-06-19 2:09 ` Re[2]: " Eric M. Ludlam
2007-06-24 14:41 ` Richard Stallman
2007-06-25 14:04 ` Re[2]: " Eric M. Ludlam
2007-07-01 20:40 ` Richard Stallman
2007-07-05 2:29 ` Re[2]: " Eric M. Ludlam
2007-07-05 20:34 ` Richard Stallman
2007-07-01 20:40 ` Richard Stallman
2007-07-04 16:35 ` T. V. Raman
2007-07-04 17:01 ` David Kastrup
2007-07-05 1:31 ` Richard Stallman
2007-07-05 14:49 ` Stefan Monnier
2007-07-06 4:38 ` Richard Stallman
2007-07-06 6:01 ` Stephen J. Turnbull
2007-07-07 13:07 ` Richard Stallman
2007-07-07 14:13 ` Lennart Borgman (gmail)
2007-07-08 16:56 ` Richard Stallman
2007-09-04 9:03 ` Highlight advice (was: Multiple major modes) Johan Bockgård
2007-07-07 17:43 ` Multiple major modes Stephen J. Turnbull
2007-07-06 16:00 ` Stefan Monnier
2007-07-06 16:10 ` Drew Adams
2007-07-07 13:06 ` Richard Stallman
2007-07-07 17:21 ` Stephen J. Turnbull
2007-07-08 16:55 ` Richard Stallman
2007-07-09 5:29 ` Stephen J. Turnbull
2007-07-09 17:21 ` Richard Stallman
2007-07-07 0:48 ` Johan Bockgård
2007-07-05 1:44 ` Re[2]: " Eric M. Ludlam
2007-07-08 22:23 ` Richard Stallman
2007-07-09 0:49 ` Re[2]: " Eric M. Ludlam
2007-07-09 17:21 ` Richard Stallman
2007-06-12 13:26 ` Should nXML be included Stefan Monnier
2007-06-12 13:16 ` Peter Heslin
2007-06-12 13:11 ` Leo
2007-06-12 13:59 ` joakim
2007-06-12 14:17 ` Peter Heslin
2007-06-12 14:14 ` David Kastrup
2007-06-12 15:11 ` Stefan Monnier
2007-06-13 8:06 ` Richard Stallman
2007-06-13 17:45 ` Claus
2007-06-14 16:19 ` Richard Stallman
2007-06-14 16:28 ` Leo
2007-06-15 19:21 ` Richard Stallman
2007-06-14 17:44 ` Eric Hanchrow
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=200706122014.l5CKEKV1021902@projectile.siege-engine.com \
--to=eric@siege-engine.com \
--cc=emacs-devel@gnu.org \
--cc=jasonr@gnu.org \
--cc=lennart.borgman@gmail.com \
--cc=monnier@iro.umontreal.ca \
--cc=sdl.web@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.
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).