unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: emacs-devel@gnu.org
Subject: Indirect text properties
Date: Sun, 17 Nov 2019 17:05:27 +0000	[thread overview]
Message-ID: <20191117170527.GB11551@ACM> (raw)

Hello, Emacs.

This is an idea I had a couple of years ago, and has recently resurfaced
in discussions with Dmitry (Subject: Several major modes).

The idea is that there could be several alternative sets of text
properties with the same symbol simultaneously in a buffer, the Lisp
code selecting which to use by binding a dynamic variable.  This would
be most useful for the syntax-table text property.

How would this work?  In textprop.c, the code would, on any access to a
text property, check its symbol's property 'indirect-text-property, and
if that is a non-nil symbol, access it's value (another symbol) and use
that as the symbol for the text property instead.  It's easier to say in
code, which would look something like:

    #define TEXP_PROP_END_NAME(sym) \
        !NILP (itp = Fget (sym, Qindirect_text_property)) && SYMPOLP (itp) \
        && !NILP (etp = find_symbol_value (itp)) && SYMBOLP (etp) \
        ? etp : sym

.  To switch to a different set of, e.g., syntax-table text properties
it would suffice to bind the lisp variable i-t-p to, say, the gensym
syntax-table-13.  Of course low level caches, e.g. in syntax.c, would
have to be kept synchronised, too.

So, what use would it be?  What I have proposed to Dmitry is having a
distinct set of syntax-table properties for each major mode chunk of an
MMM Mode ("multiple major mode") buffer.  Say syntax-table-13 would be
the set for a CC Mode chunk.  Outside of that chunk, every character
would be given a space syntax-table-13 text property.  This is the
critical thing.

Thus all actions dependent upon syntax (and there are a LOT), could be
performed by CC Mode in the chunk without the other chunks getting in
the way.  It may not even be necessary to narrow to the chunk.

The necessary juggling with the various syntax-table-13s would be done
by MMM Mode.  This might well allow arbitrary major modes to be used in
MMM Mode with minimal, if any, modification.

Thoughts?

-- 
Alan Mackenzie (Nuremberg, Germany).



             reply	other threads:[~2019-11-17 17:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-17 17:05 Alan Mackenzie [this message]
2019-11-17 22:55 ` Indirect text properties Dmitry Gutov
2019-11-18 18:06   ` Alan Mackenzie
2019-11-18 18:11 ` Lars Ingebrigtsen

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=20191117170527.GB11551@ACM \
    --to=acm@muc.de \
    --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 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).