GNU bug report logs -
#18462
Emacs freeze with python mode and M-q
Previous Next
Reported by: Gaetan Kenway <gaetank <at> gmail.com>
Date: Fri, 12 Sep 2014 16:43:02 UTC
Severity: normal
Done: Stefan Monnier <monnier <at> iro.umontreal.ca>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 18462 in the body.
You can then email your comments to 18462 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#18462
; Package
emacs
.
(Fri, 12 Sep 2014 16:43:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Gaetan Kenway <gaetank <at> gmail.com>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Fri, 12 Sep 2014 16:43:03 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)]
I ran across a odd bug the other day. Essentially, when M-q is run with an
open bracket in python mode, emacs will freeze.
To replicate the error:
$ emacs test.py
type:
def test(
then hit M-q
The version of emacs I'm using is:
GNU Emacs 24.3.1 (x86_64-pc-linux-gnu, GTK+ Version 3.10.7)
of 2014-03-07 on lamiak, modified by Debian
Its not a huge deal, it just struck me as odd since it generally really
difficult to get emacs to crash.
Thanks,
Gaetan
[Message part 2 (text/html, inline)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#18462
; Package
emacs
.
(Tue, 30 Sep 2014 20:44:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 18462 <at> debbugs.gnu.org (full text, mbox):
The second loop in python-fill-paren moves the point until the syntax
context changes. If it doesn't find a close-paren before the end of
the buffer, it loops forever.
ChangeLog entry:
* lisp/progmodes/python.el (python-fill-paren): Break
end-of-region loop when it reaches point-max.
Patch:
=== modified file 'lisp/progmodes/python.el'
*** lisp/progmodes/python.el 2014-09-29 18:14:08 +0000
--- lisp/progmodes/python.el 2014-09-30 20:14:37 +0000
*************** JUSTIFY should be used (if applicable) a
*** 3300,3306 ****
(end-of-line)
(when (not (python-syntax-context 'paren))
(skip-syntax-backward "^)")))
! (while (python-syntax-context 'paren)
(goto-char (1+ (point-marker))))
(point-marker)))
(let ((paragraph-start "\f\\|[ \t]*$")
--- 3300,3307 ----
(end-of-line)
(when (not (python-syntax-context 'paren))
(skip-syntax-backward "^)")))
! (while (and (python-syntax-context 'paren)
! (< (point) (point-max)))
(goto-char (1+ (point-marker))))
(point-marker)))
(let ((paragraph-start "\f\\|[ \t]*$")
Reply sent
to
Stefan Monnier <monnier <at> iro.umontreal.ca>
:
You have taken responsibility.
(Tue, 30 Sep 2014 23:02:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Gaetan Kenway <gaetank <at> gmail.com>
:
bug acknowledged by developer.
(Tue, 30 Sep 2014 23:02:05 GMT)
Full text and
rfc822 format available.
Message #13 received at 18462-done <at> debbugs.gnu.org (full text, mbox):
> The second loop in python-fill-paren moves the point until the syntax
> context changes. If it doesn't find a close-paren before the end of
> the buffer, it loops forever.
Thanks, looks good, installed (using eobp).
Stefan
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Wed, 29 Oct 2014 11:24:04 GMT)
Full text and
rfc822 format available.
This bug report was last modified 10 years and 239 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.