[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#63535: Master branch: Error in forw_comment (syntax.c) handling of e
From: |
Eli Zaretskii |
Subject: |
bug#63535: Master branch: Error in forw_comment (syntax.c) handling of escaped LFs |
Date: |
Tue, 16 May 2023 19:29:26 +0300 |
> Date: Tue, 16 May 2023 16:15:24 +0000
> Cc: 63535@debbugs.gnu.org
> From: Alan Mackenzie <acm@muc.de>
>
> > > && !(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?