From: Dmitry Gutov <dgutov@yandex.ru>
To: Alan Mackenzie <acm@muc.de>
Cc: 18826-done@debbugs.gnu.org
Subject: bug#18826: 24.3.94; c++-mode bad indentation after programmatic insert with locally changed syntax table
Date: Sun, 26 Oct 2014 22:09:25 +0700 [thread overview]
Message-ID: <544D0EA5.50703@yandex.ru> (raw)
In-Reply-To: <20141025232449.90894.qmail@mail.muc.de>
On 10/26/2014 06:24 AM, Alan Mackenzie wrote:
>> Because the syntax table change is temporary and its effect should be
>> limited to my code?
>
> It's no so limited. The before-change-functions and after-change-functions
> hooks will be run with that syntax table active. This is not good.
I see, thanks. Somehow, I figured that those hooks would run before or
after the current command, whereas they're triggered right near any code
that makes changes to the buffer. Question answered, closing.
On the other hand, you're doing some pretty unusual things with this. If
`c-in-sws' and `c-is-sws' were added in syntax-propertize-function
(which is called on-demand), this conflict wouldn't have manifested.
> OK. Can I suggest an alternative? In C++ (and Java) Modes, the template
> (generic) delimiters are marked with syntax-table text properties.
> Unfortunately, at the moment this is done as part of font-locking, so
> isn't done until you display. However, if you put "(sit-for 0)" into
> your code after inserting "< ... >", this will cause a redisplay,
> allowing subsequent code to use the text properties, and a backward-sexp
> will then work.
Sounds like it should be performed during `syntax-propertize' instead.
Even if you don't like this idea now, I suspect it'll happen eventually
anyway, if only for consistency with other major modes.
In that sense, the `sit-for' suggestion is not future-proof. So I'll try
only changing the syntax table around specific functions that don't
modify the buffer text, but just move point, since that was the actual goal.
> In the medium future (several weeks away), I'm hoping to fix CC Mode so
> that the text properties are applied to < ... > on an after-change
> function rather than at redisplay.
Hmm. My current workaround is to use a temporary syntax table that
inherits from c++-mode-syntax-table (but has angle brackets in the
'paren' class). Sounds like it might also create a conflict, if maybe a
more subtle one.
next prev parent reply other threads:[~2014-10-26 15:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-25 14:25 bug#18826: 24.3.94; c++-mode bad indentation after programmatic insert with locally changed syntax table Dmitry Gutov
[not found] ` <mailman.12024.1414247237.1147.bug-gnu-emacs@gnu.org>
2014-10-25 19:34 ` Alan Mackenzie
2014-10-25 22:45 ` Dmitry Gutov
[not found] ` <mailman.12048.1414277182.1147.bug-gnu-emacs@gnu.org>
2014-10-25 23:24 ` Alan Mackenzie
2014-10-26 15:09 ` Dmitry Gutov [this message]
2014-10-26 17:07 ` Stefan Monnier
2014-10-25 23:25 ` Stefan Monnier
[not found] ` <jwv61f7ohq0.fsf-monnier+emacsbugs@gnu.org>
2014-10-26 14:56 ` Dmitry Gutov
2014-10-26 14:56 ` Dmitry Gutov
2014-10-26 17:03 ` Stefan Monnier
[not found] ` <mailman.12080.1414336227.1147.bug-gnu-emacs@gnu.org>
2014-10-26 17:38 ` Alan Mackenzie
2014-10-27 1:06 ` Dmitry Gutov
2014-10-27 8:53 ` Alan Mackenzie
2014-10-27 10:21 ` 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=544D0EA5.50703@yandex.ru \
--to=dgutov@yandex.ru \
--cc=18826-done@debbugs.gnu.org \
--cc=acm@muc.de \
/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.