From: Lars Ingebrigtsen <larsi@gnus.org>
To: Richard Stanton <rhstanton@berkeley.edu>
Cc: 54996@debbugs.gnu.org
Subject: bug#54996: Emacs hangs when editing Python code with debug-on-error set to t
Date: Sun, 17 Apr 2022 22:43:00 +0200 [thread overview]
Message-ID: <87k0bnmoff.fsf@gnus.org> (raw)
In-Reply-To: <A2D3C21C-5002-4E2C-B5EF-ABDAABCA66F8@berkeley.edu> (Richard Stanton's message of "Sun, 17 Apr 2022 13:16:26 -0700")
Richard Stanton <rhstanton@berkeley.edu> writes:
> Put the cursor right at the start of the file, on the first double
> quote, and press ‘, the single quote character. On my machine, Emacs
> now hangs and doesn’t respond to the keyboard. Without debug-on-error,
> this works just fine.
I can reproduce this, too (on Debian/bookworm). `C-g' does work to
break it, but then it just hangs again almost immediately, so I guess
it's a problem in font-locking.
But it's bizarre that the debug-on-error setting should affect this.
I've skimmed through python.el looking for anything obvious (like a
`condition-case-unless-debug' but can't find anything).
The culprit must be in python-syntax-stringify -- if I just remove that,
the hang is gone. But there's no odd error handling there that I can
see (unless it's hiding in syntax-ppss)... anybody got any ideas?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-04-17 20:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-17 20:16 bug#54996: Emacs hangs when editing Python code with debug-on-error set to t Richard Stanton
2022-04-17 20:43 ` Lars Ingebrigtsen [this message]
2022-04-18 5:46 ` Eli Zaretskii
2022-04-18 9:45 ` Lars Ingebrigtsen
2022-04-18 10:02 ` Eli Zaretskii
2022-04-18 11:07 ` Lars Ingebrigtsen
2022-04-18 11:18 ` Lars Ingebrigtsen
2022-04-18 14:17 ` Philipp Stephani
2022-04-18 14:23 ` Lars Ingebrigtsen
2022-04-18 10:56 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87k0bnmoff.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=54996@debbugs.gnu.org \
--cc=rhstanton@berkeley.edu \
/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.