From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: 18826@debbugs.gnu.org
Cc: dgutov@yandex.ru
Subject: bug#18826: 24.3.94; c++-mode bad indentation after programmatic insert with locally changed syntax table
Date: Sun, 26 Oct 2014 13:07:24 -0400 [thread overview]
Message-ID: <jwv8uk2n4mc.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <544D0EA5.50703@yandex.ru> (Dmitry Gutov's message of "Sun, 26 Oct 2014 22:09:25 +0700")
> 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.
;-)
> 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.
Rather than using a hack like `sit-for', and while waiting for cc-mode
to use syntax-propertize for that, you can use `font-lock-ensure' to
make sure that the corresponding part of the code has been font-locked.
Stefan
next prev parent reply other threads:[~2014-10-26 17:07 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
2014-10-26 17:07 ` Stefan Monnier [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwv8uk2n4mc.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=18826@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).