GNU bug report logs - #39598
26.3; Emacs is extremely unresponsive on a trivial python file

Previous Next

Package: emacs;

Reported by: Ivan Oreshnikov <oreshnikov.ivan <at> gmail.com>

Date: Fri, 14 Feb 2020 10:50:01 UTC

Severity: normal

Tags: fixed

Found in version 26.3

Fixed in version 28.1

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


Message #32 received at 39598 <at> debbugs.gnu.org (full text, mbox):

From: Ivan Oreshnikov <oreshnikov.ivan <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 39598 <at> debbugs.gnu.org
Subject: Re: bug#39598: 26.3; Emacs is extremely unresponsive on a trivial
 python file
Date: Sat, 15 Feb 2020 20:31:45 +0100
[Message part 1 (text/plain, inline)]
> Why do you need that intermediate buffer to be in Python mode?

That's an intermediate state of the buffer where the rest of the migration
code is. I was not trying to hit a corner case, this is just the way I
happen to write code -- sometimes a paste text into the the buffer where
the rest of the code is and then I edit it until it becomes a valid data
structure. I am pretty sure I am not the only one who does this.

> I guess because the code is tuned to support valid Python code, not
something that shouldn't happen in Python sources?

That example *is* a valid python code. And the behavior I see *is* a bug.
And honestly, I don't think that this was a design choice along the lines
"we're going to write an optimal parser for this subset of the language but
we will occasionally hang up on this one".
[Message part 2 (text/html, inline)]

This bug report was last modified 4 years and 302 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.