Re: Bug #22983 (syntax-ppss returns wrong result) is still open. Could we fix it before the release, please.

[Stefan Monnier]

> That one thing is to determine, possibly from a cache, the equivalent to

>     (parse-partial-sexp "1" pos)

> , where "1" may take non-canonical values.

> Use cases for font-lock-dont-widen, existing or not, HAVE NO BEARING on
> that determination of the parse-partial-sexp equivalent.  So why are we
> talking about them here?

We're talking about them because the cases where font-lock-dont-widen is
needed are conceptually the same as those where syntax-ppss would need
something else than 1, so we'd like to come up with something that can
cover both uses at the same time, so as to have a single setting rather
than code that sets font-lock-dont-widen, jit-lock-dont-widen,
syntax-ppss-base, widen-user-limit, and whatnot.


        Stefan