From: "Richard M. Stallman" <rms@gnu.org>
To: Daniel Colascione <dan.colascione@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Better parse-partial-sexp; multiple major modes (was: Idea for syntax-ppss)
Date: Mon, 01 Sep 2008 02:10:51 -0400 [thread overview]
Message-ID: <E1Ka2cl-000592-JM@fencepost.gnu.org> (raw)
In-Reply-To: <CD8754BE-CF3A-4339-8291-1D8DE10B6610@gmail.com> (message from Daniel Colascione on Sun, 31 Aug 2008 04:37:53 -0400)
Maybe a core solution could be something like this: in a given buffer,
each character has a chunk-name character property. You'd buffer-
locally map chunk names to major modes. For each chunk name, create a
buffer containing just the text assigned to that chunk.
That is elegant but very expensive. Making so many buffers display as
one buffer, or keeping them in sync, would mean major changes at a low
level. Even coming up with a spec for how insertion and deletion should
work in such a scheme is hard.
We are much better off with MuMaMo.
next prev parent reply other threads:[~2008-09-01 6:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-26 21:44 Idea for syntax-ppss. Is it new? Could it be any good? Alan Mackenzie
2008-07-27 0:36 ` Lennart Borgman (gmail)
2008-07-27 1:34 ` Stefan Monnier
2008-07-27 14:50 ` Alan Mackenzie
2008-07-27 15:51 ` Stefan Monnier
2008-07-27 19:20 ` Alan Mackenzie
2008-07-27 20:17 ` Stefan Monnier
2008-07-28 2:27 ` Richard M Stallman
2008-07-28 4:08 ` Stefan Monnier
2008-07-28 21:47 ` Richard M Stallman
2008-08-31 8:37 ` Better parse-partial-sexp; multiple major modes (was: Idea for syntax-ppss) Daniel Colascione
2008-08-31 15:02 ` Better parse-partial-sexp; multiple major modes Lennart Borgman (gmail)
2008-09-01 6:10 ` Richard M. Stallman [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-08-31 9:39 Better parse-partial-sexp; multiple major modes (was: Idea for syntax-ppss) Daniel Colascione
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=E1Ka2cl-000592-JM@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=dan.colascione@gmail.com \
--cc=emacs-devel@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.
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.