From: Dmitry Gutov <dgutov@yandex.ru>
To: Tom Tromey <tom@tromey.com>
Cc: 25529@debbugs.gnu.org, Stefan Monnier <monnier@IRO.UMontreal.CA>
Subject: bug#25529: diagnosis and one approach to a fix
Date: Tue, 7 Feb 2017 15:11:13 +0200 [thread overview]
Message-ID: <0c64a77a-fc01-e1dc-54d2-5564dde3f17f@yandex.ru> (raw)
In-Reply-To: <87a89y87zv.fsf@tromey.com>
On 07.02.2017 15:07, Tom Tromey wrote:
> Dmitry> I'm not sure. Normally, that helps deal with multiline literals, but
> Dmitry> regexps in JavaScript are single-line. Maybe Stefan remembers.
>
> Based on discussion in the multi-mode thread, I'm thinking perhaps it
> handles the case where the start of the regexp literal was syntax-ified
> but not the end.
That's the idea, but syntax-propertize runs
syntax-propertize-extend-region-functions, which extends to the
beginning of the line of the edited region.
So if we made an edit inside a line containing a regexp, START should be
at the beginning of that line.
There could be some edge cases, though.
next prev parent reply other threads:[~2017-02-07 13:11 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 ` bug#25529: diagnosis and one approach to a fix Tom Tromey
2017-02-05 6:01 ` 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 [this message]
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=0c64a77a-fc01-e1dc-54d2-5564dde3f17f@yandex.ru \
--to=dgutov@yandex.ru \
--cc=25529@debbugs.gnu.org \
--cc=monnier@IRO.UMontreal.CA \
--cc=tom@tromey.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 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.