GNU bug report logs -
#30964
python-mode failing "overlapping strings" assertion lately
Previous Next
Reported by: dancol <at> dancol.org
Date: Tue, 27 Mar 2018 18:10:01 UTC
Severity: normal
Done: "Daniel Colascione" <dancol <at> dancol.org>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
(Hoping that emailing the bug address is enough to respond to an existing bug, and that I didn't miss recent follow-ups)
(Resending, since I apparently emailed the wrong bug number at first)
Here's a reliable repro:
def f():
"
def g():
"""That's a docstring"""
return ''
Place the point after the unclosed quote in f, and run (python-info-current-defun). You get this:
Debugger entered--Lisp error: (cl-assertion-failed ((> string-start last-string-end) "Overlapping strings detected (start=%d, last-end=%d)" 67 67))
cl--assertion-failed((> string-start last-string-end) "Overlapping strings detected (start=%d, last-end=%d)" (67 67) nil)
python-nav-end-of-statement()
python-nav-end-of-defun()
python-info-current-defun()
eval((python-info-current-defun) nil)
eval-expression((python-info-current-defun) nil nil 127)
funcall-interactively(eval-expression (python-info-current-defun) nil nil 127)
call-interactively(eval-expression nil nil)
command-execute(eval-expression)
This error triggers in the wild for me due to which-function-mode, which calls python-info-current-defun.
Clément.
[signature.asc (application/pgp-signature, attachment)]
This bug report was last modified 6 years and 344 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.