From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Lennart Borgman <lennart.borgman.073@student.lu.se>,
Michael Shulman <shulman@math.uchicago.edu>,
emacs-devel@gnu.org
Subject: Re: PHP mode and mmm-mode
Date: Tue, 02 May 2006 23:43:10 -0400 [thread overview]
Message-ID: <87wtd3epz4.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <m3iroo5fxr.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Tue, 02 May 2006 22:29:04 +0200")
> Well, that's to be expected, but if a convention for telling modes
> what regions belongs to what modes, then these things can be fixed in
> the relevant major modes.
> We're not talking about hundreds of modes, either -- the number of
> modes where mixing types is likely is probably pretty low. Say
> 10 to 20.
Even if that's not true, it's not a problem: there is simply no other way to
to fix each mode one by one anyway, and every mode that's adjusted is
a step forward.
> I just had a gross idea. Before calling any of the major-mode
> functions (in response to, say, `TAB'), you'd make all the text that's
> not in the current major mode invisible and intangible. Then each
> major mode function would believe there was nothing but its own type
> of text in the buffer.
I'd rather play with syntax-tables to mark them as comments. Or use
narrowing (together with some convention for how to transfer
parse-state-info from one chunk to another). The `intangible' property is
just extremely difficult to live with.
Stefan
next prev parent reply other threads:[~2006-05-03 3:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-02 4:24 PHP mode and mmm-mode Michael Shulman
2006-05-02 8:10 ` martin rudalics
2006-05-02 14:57 ` Stefan Monnier
2006-05-02 20:29 ` Lars Magne Ingebrigtsen
2006-05-02 23:44 ` Nic
2006-05-03 3:11 ` David Hansen
2006-05-03 3:43 ` Stefan Monnier [this message]
2007-01-01 2:11 ` Richard Stallman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wtd3epz4.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=lennart.borgman.073@student.lu.se \
--cc=shulman@math.uchicago.edu \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.