From: Erik Charlebois <erikcharlebois@gmail.com>
To: emacs-devel@gnu.org
Subject: multi-character syntactic entities in syntax tables
Date: Fri, 26 Apr 2013 13:28:42 -0400 [thread overview]
Message-ID: <CAC+abJbzNH7fNy=M3Spm6XxNTTqpU1VsCdmbZHV+yGHD+tMcbg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1033 bytes --]
One of the items in etc/TODO is:
** Beefed-up syntax-tables.
*** recognize multi-character syntactic entities like `begin' and `end'.
Lately I'm using languages where this would be quite useful and would be
interested in adding support. Before I dive in, are there any strong
opinions about how this should be implemented?
The approach I was thinking of taking is defining a new syntax character
class (let's say, *) which inherits from the previous character
(recursively if the previous character is *). The important distinction is
that they would not be treated as a new instance of that syntax class, so
point movement by syntax class or paren matching would work (e.g. begin
would be (****, and would only add 1 level of paren nesting).
A mode would use a syntax-propertize-function to tag keywords with
appropriate text properties. So something like Ruby:
class Foo
def Bar
if condition
...
end
end
end
would have syntax classes like:
(**** www
(** www
(* wwwwwwwww
...
)**
)**
)**
[-- Attachment #2: Type: text/html, Size: 1637 bytes --]
next reply other threads:[~2013-04-26 17:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 17:28 Erik Charlebois [this message]
2013-04-26 18:53 ` multi-character syntactic entities in syntax tables Dmitry Gutov
2013-04-26 19:22 ` Erik Charlebois
2013-04-26 20:57 ` Dmitry Gutov
2013-04-26 19:26 ` Stefan Monnier
2013-04-26 21:37 ` Erik Charlebois
2013-04-27 4:15 ` Stefan Monnier
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='CAC+abJbzNH7fNy=M3Spm6XxNTTqpU1VsCdmbZHV+yGHD+tMcbg@mail.gmail.com' \
--to=erikcharlebois@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.