GNU bug report logs - #51762
13.0.14; environment formating

Previous Next

Package: auctex;

Reported by: "Pierre L. Nageoire" <devel <at> pollock-nageoire.net>

Date: Thu, 11 Nov 2021 07:15:02 UTC

Severity: normal

Tags: confirmed

Found in version 13.0.14

Done: Ikumi Keita <ikumi <at> ikumi.que.jp>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Arash Esbati <arash <at> gnu.org>
To: Ikumi Keita <ikumi <at> ikumi.que.jp>
Cc: 51762 <at> debbugs.gnu.org, "Pierre L. Nageoire" <devel <at> pollock-nageoire.net>
Subject: bug#51762: 13.0.14; environment formating
Date: Sat, 13 Nov 2021 17:04:33 +0100
Hi Keita,

Ikumi Keita <ikumi <at> ikumi.que.jp> writes:

>>>>>> Ikumi Keita <ikumi <at> ikumi.que.jp> writes:
>> I think the attached patch fixes the problem. Could you test whether it
>> works on your side?
>
> Hmm, the patch also fails to identify the following form of code
> comment:
>  \\% This is a code comment.
> That is, a line beginning with 0 or more whitespaces, followed by even
> number of back slashes, followed by percent sign(s) and comment body.

Thank you for looking into this.  The way I understand this regexp:

  "\\([^ \r\n%\\]\\|\\\\%\\)\\([ \t]\\|\\\\\\\\\\)*"
                    ^^^^^^^

is there to exclude the control symbol \%, i.e., being parsed as comment
start.  Would it help if we generlize the control symbol idea by saying:

  "\\([^ \r\n%\\]\\|\\\\[^a-zA-Z0-9\\]\\)\\([ \t]\\|\\\\\\\\\\)*"
                        ^^^^^^^^^^^^^^

> Maybe we should give up regexp-based approach to find out code comments
> accurately.

Are you thinking about `syntax-ppss'?

Best, Arash




This bug report was last modified 3 years and 184 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.