From: Tom Tromey <tom@tromey.com>
To: 25529@debbugs.gnu.org
Subject: bug#25529: diagnosis and one approach to a fix
Date: Sat, 04 Feb 2017 22:37:29 -0700 [thread overview]
Message-ID: <87wpd58ag6.fsf@tromey.com> (raw)
In-Reply-To: <94a72ce0-f3c5-12bb-b2c7-13f685b7d4ad@hola.org>
I think the problem here is that js-syntax-propertize-regexp is using
parse-partial-sexp to try to parse the regexp literal. However, this
gets confused by the construct [^[], because it thinks that the brackets
aren't matched.
I don't think there is a way to teach parse-partial-sexp that "^" is a
quote only in this one specific instance.
One possible fix here would be to change this function to do a simple
parse of the regexp literal. I think it would only really have to
handle parsing bracket syntax and looking for the terminating "/". The
current code also looks for balanced parens, but I don't think this is
actually needed.
Tom
next prev parent reply other threads:[~2017-02-05 5:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 7:22 bug#25529: 25.1.90; js-mode: Regexp literal with unbalanced brackets breaks font-lock Mikhail Gusarov
2017-02-05 5:37 ` Tom Tromey [this message]
2017-02-05 6:01 ` bug#25529: diagnosis and one approach to a fix Tom Tromey
2017-02-05 18:05 ` Tom Tromey
2017-02-05 18:43 ` Tom Tromey
2017-02-06 1:12 ` Dmitry Gutov
2017-02-06 17:27 ` Tom Tromey
2017-02-07 2:20 ` Dmitry Gutov
2017-02-07 13:07 ` Tom Tromey
2017-02-07 13:11 ` Dmitry Gutov
2017-02-07 14:56 ` Stefan Monnier
2017-02-11 1:52 ` Tom Tromey
2017-02-11 3:45 ` Stefan Monnier
2017-02-11 4:06 ` Tom Tromey
2017-02-11 4:22 ` Stefan Monnier
2017-02-11 15:27 ` Tom Tromey
2017-02-11 15:41 ` Stefan Monnier
2017-02-11 17:13 ` Tom Tromey
2017-02-11 19:11 ` Dmitry Gutov
2017-02-11 19:37 ` bug#25529: done Tom Tromey
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=87wpd58ag6.fsf@tromey.com \
--to=tom@tromey.com \
--cc=25529@debbugs.gnu.org \
/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.