From: Tom Tromey <tom@tromey.com>
To: "Wedler\, Christoph" <christoph.wedler@sap.com>
Cc: "fgallina@gnu.org" <fgallina@gnu.org>,
Tom Tromey <tom@tromey.com>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: python.el patch proposal: Respect `prog-indentation-context'.
Date: Mon, 29 Jun 2015 12:53:28 -0600 [thread overview]
Message-ID: <87mvziny6v.fsf@tromey.com> (raw)
In-Reply-To: <F9C2521BBF380A4A97379009991555E685BA071B@DEWDFEMB17C.global.corp.sap> (Christoph Wedler's message of "Mon, 22 Jun 2015 13:38:00 +0000")
>>>>> "Christoph" == Wedler, Christoph <christoph.wedler@sap.com> writes:
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.
While digging around I found this in syntax.el:
;;; Todo:
;; - do something about the case where the syntax-table is changed.
So I suppose it is just a known problem.
The basic idea, I think, would be to let the mode(s) change the syntax
table when needed; and to have these changes be recorded by syntax.el so
that syntax-ppss and friends could use the correct syntax table for a
given region.
Tom
next prev parent reply other threads:[~2015-06-29 18:53 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 [this message]
2015-06-30 13:53 ` Stefan Monnier
2015-07-02 9:13 ` Wedler, Christoph
-- 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mvziny6v.fsf@tromey.com \
--to=tom@tromey.com \
--cc=christoph.wedler@sap.com \
--cc=emacs-devel@gnu.org \
--cc=fgallina@gnu.org \
/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.