From: Daniel Colascione <dancol@dancol.org>
To: Luke Powers <luke.powers@openx.com>, Dima Kogan <dima@secretsauce.net>
Cc: 21657@debbugs.gnu.org
Subject: bug#21657: 25.0.50; Python mode goes into an infinite loop
Date: Mon, 12 Oct 2015 20:21:34 -0700 [thread overview]
Message-ID: <561C78BE.6070109@dancol.org> (raw)
In-Reply-To: <CACOeLr5-57z37i3Mk98tynucb+ohnSNQ+pR_2ahFhXZbSbZtOg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 981 bytes --]
On 10/09/2015 04:16 PM, Luke Powers wrote:
> There are a couple issues out there with similar reports (21646 21629
> 21628).
>
> Revert to 818f06eaa72d8e4f9ba314c1c2855613bf89f396 if you want to work
> around the issue.
I think I know what's going on. Stefan's change moved some of the
syntax-propertize stuff from Lisp into C. Now Emacs core has a variable
called syntax-propertize--done, known in C as syntax_propertize__done.
We make it buffer-local using Fmake_variable_buffer_local, but that
makes the variable buffer-local when it's _set_. Until it's set, the
variable retains its global value, which lives in the C variable
syntax_propertize__done. So if we syntax-propertize 1000 characters of
buffer A, then find-file in buffer B, we think we've syntax-propertized
up to position 1000 (the value of syntax_propertize__done) until we set
it to something else. In the case of Python, if we have a triple quote
in the first 1000 characters, we infloop.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-10-13 3:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-09 22:22 bug#21657: 25.0.50; Python mode goes into an infinite loop Dima Kogan
2015-10-09 23:16 ` Luke Powers
2015-10-13 3:21 ` Daniel Colascione [this message]
2015-10-13 4:58 ` immerrr again
2015-10-13 5:05 ` Daniel Colascione
2015-10-13 5:42 ` immerrr again
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=561C78BE.6070109@dancol.org \
--to=dancol@dancol.org \
--cc=21657@debbugs.gnu.org \
--cc=dima@secretsauce.net \
--cc=luke.powers@openx.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).