From: immerrr again <immerrr@gmail.com>
To: Daniel Colascione <dancol@dancol.org>
Cc: 21657@debbugs.gnu.org, Dima Kogan <dima@secretsauce.net>,
Luke Powers <luke.powers@openx.com>
Subject: bug#21657: 25.0.50; Python mode goes into an infinite loop
Date: Tue, 13 Oct 2015 07:58:07 +0300 [thread overview]
Message-ID: <CAERznn_ncadbMtNWXyCZ0HG44SLXfprgKO19gu5Jn=bWjCSFLg@mail.gmail.com> (raw)
In-Reply-To: <561C78BE.6070109@dancol.org>
There's a patch to fix this in #21671.
On Tue, Oct 13, 2015 at 6:21 AM, Daniel Colascione <dancol@dancol.org> wrote:
> 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.
>
next prev parent reply other threads:[~2015-10-13 4:58 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
2015-10-13 4:58 ` immerrr again [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAERznn_ncadbMtNWXyCZ0HG44SLXfprgKO19gu5Jn=bWjCSFLg@mail.gmail.com' \
--to=immerrr@gmail.com \
--cc=21657@debbugs.gnu.org \
--cc=dancol@dancol.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 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.