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 00:19:17 +0200 [thread overview]
Message-ID: <87y50to93u.fsf@yandex.ru> (raw)
In-Reply-To: <m2bnxqujtx.fsf@batsov.com> (Bozhidar Batsov's message of "Sat, 01 Mar 2014 15:31:06 +0200")
Bozhidar Batsov <bozhidar@batsov.com> writes:
> In most editors/IDEs code like this
>
> regexp = /
> start # some text
> \s # white space char
> (group) # first group
> (?:alt1|alt2) # some alternation
> end
> /x
>
> will have the comments font-locked as comments, because comments are
> allowed in the extended regexp literal syntax (/x). It would be nice
> if this was taken into account in ruby-mode as well.
Not sure how to implement it best.
Ideally, we'd have a new kind of syntax instead of strings (native
regexp support?), which would make font-lock fontify comments inside.
Or maybe a modifier on the string syntax?
Of course, we could just scan the contents of every regexp, look for any
hash character that doesn't look like it starts interpolation, and
forcibly fontify the text from it till the end of line.
next prev parent reply other threads:[~2014-03-01 22:19 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 [this message]
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
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=87y50to93u.fsf@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).