From: Dmitry Gutov <dgutov@yandex.ru>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 16915@debbugs.gnu.org, Bozhidar Batsov <bozhidar@batsov.com>
Subject: bug#16915: 24.3.50; [ruby-mode] Comments in regexps using the extended syntax are not font-locked properly
Date: Mon, 10 Mar 2014 09:21:02 +0200 [thread overview]
Message-ID: <531D67DE.4030200@yandex.ru> (raw)
In-Reply-To: <jwvy50ld8tq.fsf-monnier+emacsbugs@gnu.org>
On 07.03.2014 23:04, Stefan Monnier wrote:
> My preference would be to think about it as a "multi-mode" case, and
> hence make it possible to specify a different syntax-table to use within
> the regexp.
I remember this idea, but have a hard time viewing it in the context of
our latest discussion on the subject of multi-modes.
First, why only syntax-table? For this specific case, a syntax table
change is not required, we only need to be able to view the text between
/'s as a separate context (but - and this is a change from certain other
multi-mode uses - still fontify uncommented text inside them with the
regexp face). But in the general case, we would at least want to be able
to change font-lock-keywords, too.
> I think of it along the lines of a new syntax-class, applied to the "/"
> char, which would change the syntax-table for the subsequent text.
How would this interact with a new hook that would `syntax-ppss' would
run on the cached entries?
Would its default value look for the chars bearing the new syntax class?
next prev parent reply other threads:[~2014-03-10 7:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-01 13:31 bug#16915: 24.3.50; [ruby-mode] Comments in regexps using the extended syntax are not font-locked properly Bozhidar Batsov
2014-03-01 22:19 ` Dmitry Gutov
2014-03-02 11:03 ` Bozhidar Batsov
2014-03-02 15:03 ` Dmitry Gutov
2014-03-04 10:02 ` Bozhidar Batsov
2014-03-07 21:04 ` Stefan Monnier
2014-03-10 7:21 ` Dmitry Gutov [this message]
2014-03-10 14:40 ` Stefan Monnier
2014-03-12 7:48 ` Dmitry Gutov
2014-03-12 14:25 ` 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=531D67DE.4030200@yandex.ru \
--to=dgutov@yandex.ru \
--cc=16915@debbugs.gnu.org \
--cc=bozhidar@batsov.com \
--cc=monnier@iro.umontreal.ca \
/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.