GNU bug report logs -
#62325
Python quotes/apostrophes can cause hang
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 62325 in the body.
You can then email your comments to 62325 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#62325
; Package
emacs
.
(Tue, 21 Mar 2023 08:30:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Gabriel Brown <gabriel.h.brown <at> gmail.com>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Tue, 21 Mar 2023 08:30:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Hi, all. First bug report for me. I've searched to see if there are
other reports of my issue, but turned up empty handed.
--- Summary ---
It seems when there are three or more python docstrings (each bordered
by two lines of triple quotes """) and each containing an apostrophe,
then the next time a quote docstring is to be inserted Emacs hangs.
I have included a minimum viable example file that reproduces this
behavior on my machine. Simply replace the angle bracket line
containing the instructions with triple quotes, and Emacs should hang.
(In case file attachments don't work I have included the text of the
file at the end of the email.)
--- Additional information ---
Emacs version: 28.2 (via pacman package manager)
machine: EndeavourOS Linux x86_64 (kernel: 6.2.2-arch1-1)
reply email: gabriel.h.brown <at> gmail.com
--- start of example file ---
def f_0():
# inline comment
< try replacing with triple quotes >
return 4
def f_1():
"""
ghbrown's first comment
"""
return 1
def f_2():
"""
ghbrown's second comment
"""
return 1
def f_3():
"""
ghbrown's third comment
"""
return 1
--- end of example file ---
[Message part 2 (text/html, inline)]
[mve.py (text/x-python, attachment)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#62325
; Package
emacs
.
(Tue, 21 Mar 2023 10:06:01 GMT)
Full text and
rfc822 format available.
Message #8 received at 62325 <at> debbugs.gnu.org (full text, mbox):
>
> It seems when there are three or more python docstrings (each bordered
> by two lines of triple quotes """) and each containing an apostrophe,
> then the next time a quote docstring is to be inserted Emacs hangs.
>
Thanks for your bug report. I can reproduce that bug with Emacs 27 and
28, but not with Emacs 29.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#62325
; Package
emacs
.
(Tue, 21 Mar 2023 11:46:01 GMT)
Full text and
rfc822 format available.
Message #11 received at 62325 <at> debbugs.gnu.org (full text, mbox):
Gabriel Brown wrote:
> It seems when there are three or more python docstrings (each bordered by two lines of triple quotes """) and each
> containing an apostrophe, then the next time a quote docstring is to be inserted Emacs hangs.
Hi Gabriel,
From my testing of your example, the problem appears to be fixed with
the #58780 fix. Can you test with the latest Emacs in emacs-29 branch
or master branch? Or you can try the patch attached in #58780.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#62325
; Package
emacs
.
(Wed, 05 Apr 2023 07:32:03 GMT)
Full text and
rfc822 format available.
Message #14 received at 62325 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Apologies for the delay. I finally came into some time to switch Emacs
versions, and using the makepkg branch for Emacs 29 I no longer see the
issue I reported.
Thanks again!
On Tue, Mar 21 2023 at 08:45:28 PM +09:00:00, kobarity
<kobarity <at> gmail.com> wrote:
>
> Gabriel Brown wrote:
>> It seems when there are three or more python docstrings (each
>> bordered by two lines of triple quotes """) and each
>> containing an apostrophe, then the next time a quote docstring is
>> to be inserted Emacs hangs.
>
> Hi Gabriel,
>
> From my testing of your example, the problem appears to be fixed with
> the #58780 fix. Can you test with the latest Emacs in emacs-29 branch
> or master branch? Or you can try the patch attached in #58780.
[Message part 2 (text/html, inline)]
Reply sent
to
Eli Zaretskii <eliz <at> gnu.org>
:
You have taken responsibility.
(Wed, 05 Apr 2023 08:37:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Gabriel Brown <gabriel.h.brown <at> gmail.com>
:
bug acknowledged by developer.
(Wed, 05 Apr 2023 08:37:02 GMT)
Full text and
rfc822 format available.
Message #19 received at 62325-done <at> debbugs.gnu.org (full text, mbox):
> Cc: 62325 <at> debbugs.gnu.org
> Date: Tue, 04 Apr 2023 18:23:29 -0500
> From: Gabriel Brown <gabriel.h.brown <at> gmail.com>
>
> Apologies for the delay. I finally came into some time to switch Emacs versions, and using the makepkg
> branch for Emacs 29 I no longer see the issue I reported.
Thanks, I'm therefore closing this bug.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Wed, 03 May 2023 11:24:05 GMT)
Full text and
rfc822 format available.
This bug report was last modified 2 years and 11 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.