From: Dmitry Gutov <dgutov@yandex.ru>
To: Bozhidar Batsov <bozhidar@batsov.com>
Cc: 16915@debbugs.gnu.org
Subject: bug#16915: 24.3.50; [ruby-mode] Comments in regexps using the extended syntax are not font-locked properly
Date: Sun, 02 Mar 2014 17:03:10 +0200 [thread overview]
Message-ID: <5313482E.3050706@yandex.ru> (raw)
In-Reply-To: <CFD6EE423DDE468AAC847DE8772540BD@gmail.com>
On 02.03.2014 13:03, Bozhidar Batsov wrote:
> Native regexp support is preferable IMO. After all - regexps are not
> strings. If they were treated differently we’d also be able to have
> extra highlighting for things like named groups, quantifiers, regexp
> classes, etc. I guess, however, that this would require a lot of work.
Since the regexp syntax can be different between languages, we probably
won't get all of that automatically. The direct benefits from the native
support I can see is highlighting comments (for regexps with appropriate
modifiers, in languages that support that), new faces for regexp itself,
and maybe for groups, quantifiers, etc.
The highlighting of the elements inside regexp would probably have to be
done the old-fashioned way, in font-lock-keywords (although that code
could be shared between many languages). We could implement something
like it right now, the main difference is just the lack of standard faces.
next prev parent reply other threads:[~2014-03-02 15:03 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 [this message]
2014-03-04 10:02 ` Bozhidar Batsov
2014-03-07 21:04 ` Stefan Monnier
2014-03-10 7:21 ` Dmitry Gutov
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
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=5313482E.3050706@yandex.ru \
--to=dgutov@yandex.ru \
--cc=16915@debbugs.gnu.org \
--cc=bozhidar@batsov.com \
/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).