From: "Wedler, Christoph" <christoph.wedler@sap.com>
To: Tom Tromey <tom@tromey.com>
Cc: "fgallina@gnu.org" <fgallina@gnu.org>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: RE: python.el patch proposal: Respect `prog-indentation-context'.
Date: Thu, 2 Jul 2015 09:13:10 +0000 [thread overview]
Message-ID: <F9C2521BBF380A4A97379009991555E685BA4D5E@DEWDFEMB17C.global.corp.sap> (raw)
In-Reply-To: <87mvziny6v.fsf@tromey.com>
Christoph> But you are right, one should aim for improvements here, too. At the
Christoph> moment, it has lesser priority for me - after all, wrong syntax
Christoph> highlighting just corrupts the appearance of the code whereas wrong
Christoph> indentation corrupts the code itself.
> I asked because it seems to me that many mode indenters look at the
> syntax to decide what to do.
You are right - I put "setting the syntax table of the inner mode" on my
TODO list as well.
> While digging around I found this in syntax.el:
>
> ;;; Todo:
> ;; - do something about the case where the syntax-table is changed.
As I bind syntax-ppss-cache and syntax-ppss-last to nil around the inner
mode indentation, this might already work - at least if I do not set the
inner mode's syntax-propertize function... (there are probably not too
many Python triple quotes strings in grammar actions...)
- Christoph
next prev parent reply other threads:[~2015-07-02 9:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 14:05 python.el patch proposal: Respect `prog-indentation-context' Wedler, Christoph
2015-06-19 20:36 ` Tom Tromey
2015-06-22 13:38 ` Wedler, Christoph
2015-06-29 18:53 ` Tom Tromey
2015-06-30 13:53 ` Stefan Monnier
2015-07-02 9:13 ` Wedler, Christoph [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-07-02 9:16 Wedler, Christoph
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=F9C2521BBF380A4A97379009991555E685BA4D5E@DEWDFEMB17C.global.corp.sap \
--to=christoph.wedler@sap.com \
--cc=emacs-devel@gnu.org \
--cc=fgallina@gnu.org \
--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 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).