From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 23443@debbugs.gnu.org
Subject: bug#23443: 25.0.93; Temporary change to syntax-table is in effect during syntax-propertize
Date: Sun, 8 May 2016 14:58:24 -0400 [thread overview]
Message-ID: <CAM-tV-_pc6OWy2SuczWRd2zTBo=zL6m_M3rLK+HHhg6diPxXMg@mail.gmail.com> (raw)
In-Reply-To: <318abec3-4ff6-f647-5754-dc061be63eaf@yandex.ru>
On Sun, May 8, 2016 at 2:53 PM, Dmitry Gutov <dgutov@yandex.ru> wrote:
> On 05/08/2016 09:51 PM, Noam Postavsky wrote:
>
>> So yasnippet mustn't use scan-sexps whilst the syntax-table has been
>> changed?
>
>
> I don't know the whole issue, but it should be possible to reorganize the
> code that when scan-sexps is called, the current syntax table is the
> appropriate one.
>
> But I don't know why you're changing it in the first place.
That scan-sexps is being to parse the snippet syntax, which is why
it's not using the major-mode's syntax table. I suppose the proper way
to fix this is to parse the whole snippet before inserting it into the
buffer, but I was hoping to put off the code reorganization that would
entail for a while longer.
next prev parent reply other threads:[~2016-05-08 18:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-04 10:41 bug#23443: 25.0.93; Temporary change to syntax-table is in effect during syntax-propertize Noam Postavsky
2016-05-08 0:58 ` Dmitry Gutov
2016-05-08 18:51 ` Noam Postavsky
2016-05-08 18:53 ` Dmitry Gutov
2016-05-08 18:58 ` Noam Postavsky [this message]
2016-05-08 19:12 ` Dmitry Gutov
2016-05-12 10:05 ` Noam Postavsky
2016-05-13 5:49 ` Andreas Röhler
2016-05-16 18:28 ` Dmitry Gutov
2016-05-13 5:55 ` Andreas Röhler
2016-05-10 17:34 ` Andreas Röhler
2016-05-10 20:42 ` Dmitry Gutov
2016-05-11 5:20 ` Andreas Röhler
2016-05-11 9:20 ` Dmitry Gutov
2016-05-11 12:13 ` Andreas Röhler
2016-05-11 12:31 ` Dmitry Gutov
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='CAM-tV-_pc6OWy2SuczWRd2zTBo=zL6m_M3rLK+HHhg6diPxXMg@mail.gmail.com' \
--to=npostavs@users.sourceforge.net \
--cc=23443@debbugs.gnu.org \
--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.