From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Philipp Stephani
Hello, Philipp.
On Thu, Mar 23, 2017 at 22:08:15 +0000, Philipp Stephani wrote:
> Philipp Stephani <p.stephani2@gmail.com> schrieb am Di.,= 28. Feb. 2017 um
> 22:32 Uhr:
> > There appears to be an edge case caused by using `syntax-ppss'= ; in a
> > narrowed buffer during JIT lock inside of Python triple-quote str= ings.
> > Unfortunately it is impossible to reproduce without manually
> > destroying the syntactic information in the Python buffer, but it= has
> > been observed in practice.=C2=A0 In that case it can happen that = the syntax
> > caches get sufficiently out of whack so that there appear to be > > overlapping strings in the buffer.=C2=A0 As Python has no nested = strings,
> > this situation is impossible and leads to an infloop in
> > `python-nav-end-of-statement'.=C2=A0 Protect against this by = checking
> > whether the search for the end of the current string makes progre= ss.
I think it's fair to say that syntax-ppss doesn't work in narrowed<= br class=3D"gmail_msg"> buffers.=C2=A0 This has been known for a long time now - I raised bug #2298= 3
about this topic over a year ago, yet despite repeated requests from
myself, there are no signs this is going to be fixed any time soon.
I "welcome" your misfortune, as it shows that the flaws in syntax= -ppss
in narrowed buffers occur in real situations, not just test cases.
Presumably, diagnosing the bug took up quite a lot of your valuable
time.
Let's get bug #22983 fixed.