From: Noam Postavsky <npostavs@gmail.com>
To: dancol@dancol.org
Cc: 30964@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#30964: python-mode failing "overlapping strings" assertion lately
Date: Sun, 01 Apr 2018 21:11:26 -0400 [thread overview]
Message-ID: <87bmf2pg3l.fsf@gmail.com> (raw)
In-Reply-To: <5c3e75f096fae419224804c590805b9c.squirrel@dancol.org> (dancol's message of "Tue, 27 Mar 2018 11:09:38 -0700")
dancol@dancol.org writes:
> Has something changed in master that might be breaking python-mode? We
> keep hitting a parsing assertion.
>
> The surrounding code in python.el claims that
>
> ;; The assertion can only fail if syntax table
> ;; text properties and the `syntax-ppss' cache
> ;; are somehow out of whack. This has been
> ;; observed when using `syntax-ppss' during
> ;; narrowing.
> (cl-assert (> string-start last-string-end)
> :show-args
> "\
> Overlapping strings detected (start=%d, last-end=%d)")
>
> I can _sometimes_ repro with (while (not (eobp))
> (python-nav-forward-statement)), but I haven't found a reliable test case.
How recent is "lately"? Could it be related to [1: 14b9558752]?
[1: 14b9558752]: 2017-12-12 23:03:00 -0500
* src/syntax.c (find_defun_start): Use syntax-ppss
https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=14b95587520959c5b54356547a0a69932a9bb480
next prev parent reply other threads:[~2018-04-02 1:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 18:09 bug#30964: python-mode failing "overlapping strings" assertion lately dancol
2018-04-02 1:11 ` Noam Postavsky [this message]
2018-04-03 18:12 ` Charles A. Roelli
2018-04-03 22:06 ` Dmitry Gutov
2018-05-18 15:46 ` Clément Pit-Claudel
2018-05-18 19:18 ` Andreas Röhler
2018-05-19 1:49 ` Noam Postavsky
2018-05-19 6:49 ` Andreas Röhler
2018-05-30 0:29 ` Noam Postavsky
2018-06-02 19:03 ` Philipp Stephani
2018-06-02 20:35 ` Noam Postavsky
2018-06-16 20:55 ` Daniel Colascione
2018-06-16 22:36 ` Noam Postavsky
2018-06-17 7:33 ` Andreas Röhler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bmf2pg3l.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=30964@debbugs.gnu.org \
--cc=dancol@dancol.org \
--cc=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).