Subject: Re: bug#63535: Master branch: Error in forw_comment (syntax.c) handling of escaped LFs

From: Eli Zaretskii <[email-masked]>
Date: Tue, 16 May 2023 19:29:26 +0300

> Date: Tue, 16 May 2023 16:15:24 +0000
> Cc: [email-masked]
> From: Alan Mackenzie <[email-masked]>
> 
> > >    && !(comment_end_can_be_escaped && char_quoted (from, from_byte))
> 
> > > ..  Checking char_quoted is wrong.  Instead the function should check the
> > > current parse state.
> 
> > Why not both?  IOW, please explain why char_quoted is not TRT here.
> 
> Because parse-partial-sexp is not scanning the backslash.  The scan
> starts one character after the backslash, and the syntactic effect of
> that backslash is not in the OLDSTATE argument to parse-partial-sexp.

Sorry, I still don't follow: char_quoted doesn't call
parse-partial-sexp, AFAICT.  So why does it matter what
parse-partial-sexp does when we are discussing why char_quoted is not
TRT?