all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Dmitry Gutov <dgutov@yandex.ru>
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: Fri, 07 Mar 2014 16:04:00 -0500	[thread overview]
Message-ID: <jwvy50ld8tq.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <87y50to93u.fsf@yandex.ru> (Dmitry Gutov's message of "Sun, 02 Mar 2014 00:19:17 +0200")

> Ideally, we'd have a new kind of syntax instead of strings (native
> regexp support?), which would make font-lock fontify comments inside.

This is not completely new.  We have a similar problem for example with
TeX's math $...$ and with PostScript's strings (...(...)..).

> Or maybe a modifier on the string syntax?

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 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.


        Stefan





  parent reply	other threads:[~2014-03-07 21:04 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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwvy50ld8tq.fsf-monnier+emacsbugs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=16915@debbugs.gnu.org \
    --cc=bozhidar@batsov.com \
    --cc=dgutov@yandex.ru \
    /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.