all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jacob MacDonald <jaccarmac@gmail.com>
Cc: 21629@debbugs.gnu.org
Subject: bug#21629: 25.0.50; python.el freezes up around docstrings.
Date: Tue, 06 Oct 2015 17:54:00 +0300	[thread overview]
Message-ID: <83fv1oxd2v.fsf@gnu.org> (raw)
In-Reply-To: <CACy6W0Am+6q1oxpL7nxiuM=F=YmCr2AAFm2L0Evq6CuAzcSeig@mail.gmail.com>

> From: Jacob MacDonald <jaccarmac@gmail.com>
> Date: Tue, 06 Oct 2015 04:48:50 +0000
> 
> Begin from a fresh 'emacs -Q'. Create a Python file. Insert a long
> docstring which contains a header line and then a long body which
> includes a few line breaks and spaces in it. The docstring should look
> something like this:
> 
> """test header
> 
> lorem ipsum... more text more text more text
> x10 lines
> ...
> ...
> """
> 
> Save the file and close emacs. Start a fresh 'emacs -Q'. Open dired in
> the directory which contains the Python file you created. Navigate to
> the file and try to open in from dired. Emacs will freeze indefinitely
> and eat all the system resources it can. You can break the cycle by
> pressing C-q many times, but the freeze happens again on every single
> redisplay. If you wait awhile before cancelling the redisplay, you may
> see that fontification has frozen somewhere in the middle of the docstring.

It infloops in python-nav-end-of-statement.  The loop there ends up
one position before EOB, then jumps back to string-start, and so on
and so forth, ad nauseam.

I have no idea what causes this, but I hope Python-mode experts and
perhaps Stefan (due to syntax stuff) will be able to figure this out.






  reply	other threads:[~2015-10-06 14:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-06  4:48 bug#21629: 25.0.50; python.el freezes up around docstrings Jacob MacDonald
2015-10-06 14:54 ` Eli Zaretskii [this message]
2015-10-08 14:27   ` Andreas Röhler
2015-10-08 18:22     ` Luke Powers

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=83fv1oxd2v.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=21629@debbugs.gnu.org \
    --cc=jaccarmac@gmail.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.