infinite loop on py-indent-line
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-mode.el |
Fix Released
|
High
|
Andreas Roehler |
Bug Description
Hitting C-c C-v prints the following:
Using `python-mode' version 6.0.10
M-x emacs-version returns:
GNU Emacs 24.2.1 (x86_64-
I have a bug that pops up where I am no longer able to use python-mode to tab lines. I can't determine exactly what cases cause this problem, but it seems related to the commenting rules. Perhaps because I use a combination of comment-dwim and py-comment-region to handle my commenting.
I'm attaching a file that causes the error. The file has 4 lines, a while statement, a blank line, and two commented lines. If either or both of the commented lines are uncommented, the error disappears. In the file's uploaded state, navigating to the blank line and pressing TAB prints the following message:
py-
Running in the emacs-lisp debugger prints the following:
Debugger entered--Lisp error: (error "Variable binding depth exceeds max-specpdl-size")
syntax-ppss()
py-
py-
py-
(.)
(.)
(.)
py-
py-
py-
py-
py-
py-
py-
py-
py-
call-
Changed in python-mode: | |
milestone: | none → 6.1.2 |
assignee: | nobody → Andreas Roehler (a-roehler) |
importance: | Undecided → High |
Changed in python-mode: | |
status: | New → Fix Committed |
Changed in python-mode: | |
status: | Fix Committed → Fix Released |
Am 18.03.2013 03:43, schrieb Jarvis Schultz: pc-linux- gnu, GTK+ Version 2.24.10) of 2012-11-05 on litembilla, modified by Debian
> Public bug reported:
>
> Hitting C-c C-v prints the following:
> Using `python-mode' version 6.0.10
> M-x emacs-version returns:
> GNU Emacs 24.2.1 (x86_64-
>
> I have a bug that pops up where I am no longer able to use python-mode
> to tab lines. I can't determine exactly what cases cause this problem,
> but it seems related to the commenting rules. Perhaps because I use a
> combination of comment-dwim and py-comment-region to handle my
> commenting.
Both works here right out of the box.
If you wrote something for it, please show the code.
> of-comment: Variable binding depth exceeds max- of-comment( ) of-statement( 100 t) of-statement( 100 t) of-statement( 100 t) of-statement( 100 t) of-statement( 67 t) of-statement( 21 t) of-statement( 20 t) of-statement( ) of-statement- p() indentation( ) ely(py- indent- line nil nil)
> I'm attaching a file that causes the error. The file has 4 lines, a
> while statement, a blank line, and two commented lines. If either or
> both of the commented lines are uncommented, the error disappears. In
> the file's uploaded state, navigating to the blank line and pressing TAB
> prints the following message:
>
> py-beginning-
> specpdl-size
>
> Running in the emacs-lisp debugger prints the following:
> Debugger entered--Lisp error: (error "Variable binding depth exceeds max-specpdl-size")
> syntax-ppss()
> py-beginning-
> py-end-
> py-end-
> (.)
> (.)
> (.)
> py-end-
> py-end-
> py-end-
> py-end-
> py-end-
> py-end-
> py-beginning-
> py-compute-
> py-indent-line(nil)
> call-interactiv
>
Can't reproduce. Do the error messages occur with example file?
What I see is some issue with var py-indent-comment.
If `t', you should correct the indent of comments first.
If nil, it seems to have a bug, as TAB doesn't indent.
Andreas