GNU bug report logs - #16915
24.3.50; [ruby-mode] Comments in regexps using the extended syntax are not font-locked properly

Previous Next

Full log

Message #8 received at 16915 <at> debbugs.gnu.org (full text, mbox):

From: Dmitry Gutov <dgutov <at> yandex.ru>
To: Bozhidar Batsov <bozhidar <at> batsov.com>
Cc: 16915 <at> debbugs.gnu.org
Subject: Re: 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

Bozhidar Batsov <bozhidar <at> 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.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.