GNU logs - #75164, boring messages

Message sent to bug-gnu-emacs@HIDDEN:

Subject: bug#75164: treesit-font-lock-fontify-region is easy to lost color on parse error. suggest to remain fontify on parse error.
Resent-From: Eval Exec <execvy@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-gnu-emacs@HIDDEN
Resent-Date: Sat, 28 Dec 2024 16:26:01 +0000
Resent-Message-ID: <handler.75164.B.173540314820673 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: 75164 <at> debbugs.gnu.org
MIME-Version: 1.0
From: Eval Exec <execvy@HIDDEN>
Date: Sun, 29 Dec 2024 00:25:24 +0800
Message-ID: <CAKfPJDq5i-WaoZ+1-=F1VGxm_2YWTqN45H+7f0Y8+BRFMnM7DQ@HIDDEN>
Content-Type: text/plain; charset="UTF-8"
Received-SPF: pass client-ip=2001:4860:4864:20::42;
 envelope-from=execvy@HIDDEN; helo=mail-oa1-x42.google.com
X-Spam_score_int: -20
X-Spam_score: -2.1
X-Spam_bar: --
X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1,
 DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001,
 RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001,
 SPF_PASS=-0.001 autolearn=ham autolearn_force=no
X-Spam_action: no action
X-Spam-Score: -1.3 (-)
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -2.3 (--)

Hello.
When I enable rust-ts-mode on a rust file, I found treesitter is easy
to make emacs buffer to lost color.
For example, on the following rust code:
```rust

struct Dog {
    name: String,
    age: u8,
}

struct ManyStruct {
    a: u8,
}

fn many_code(){
    fn fib(n: u32) -> u32 {
        if n == 0 {
            return 0;
        }
        if n == 1 {
            return 1;
        }
        fib(n - 1) + fib(n - 2)
    }
}

fn main() {
    // change below `//` to `/` to see the difference
    // {
}
```

the rust code is right, and the emacs buffer color is right on every
struct/functions.
But, if I change `// {` to `/ {`, then the rust code is wrong, this
buffer will lost all colors.
You can see the change on bellow images:

https://imgur.com/a/4Tnv0GJ

I suggest emacs can remain colors even if the code is wrong.

My emacs version info: GNU Emacs 31.0.50

Message sent:

Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailer: MIME-tools 5.505 (Entity 5.505)
Content-Type: text/plain; charset=utf-8
X-Loop: help-debbugs@HIDDEN
From: help-debbugs@HIDDEN (GNU bug Tracking System)
To: Eval Exec <execvy@HIDDEN>
Subject: bug#75164: Acknowledgement (treesit-font-lock-fontify-region is
 easy to lost color on parse error. suggest to remain fontify on parse
 error.)
Message-ID: <handler.75164.B.173540314820673.ack <at> debbugs.gnu.org>
References: <CAKfPJDq5i-WaoZ+1-=F1VGxm_2YWTqN45H+7f0Y8+BRFMnM7DQ@HIDDEN>
X-Gnu-PR-Message: ack 75164
X-Gnu-PR-Package: emacs
Reply-To: 75164 <at> debbugs.gnu.org
Date: Sat, 28 Dec 2024 16:26:02 +0000

Thank you for filing a new bug report with debbugs.gnu.org.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 bug-gnu-emacs@HIDDEN

If you wish to submit further information on this problem, please
send it to 75164 <at> debbugs.gnu.org.

Please do not send mail to help-debbugs@HIDDEN unless you wish
to report a problem with the Bug-tracking system.

--=20
75164: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=3D75164
GNU Bug Tracking System
Contact help-debbugs@HIDDEN with problems

Message sent to bug-gnu-emacs@HIDDEN:

Subject: bug#75164: treesit-font-lock-fontify-region is easy to lost color on parse error. suggest to remain fontify on parse error.
Resent-From: Charalampos Mitrodimas <charmitro@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-gnu-emacs@HIDDEN
Resent-Date: Mon, 30 Dec 2024 00:30:03 +0000
Resent-Message-ID: <handler.75164.B75164.173551855023446 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: Eval Exec <execvy@HIDDEN>
Cc: 75164 <at> debbugs.gnu.org
From: Charalampos Mitrodimas <charmitro@HIDDEN>
In-Reply-To: <CAKfPJDq5i-WaoZ+1-=F1VGxm_2YWTqN45H+7f0Y8+BRFMnM7DQ@HIDDEN>
 (Eval Exec's message of "Sun, 29 Dec 2024 00:25:24 +0800")
References: <CAKfPJDq5i-WaoZ+1-=F1VGxm_2YWTqN45H+7f0Y8+BRFMnM7DQ@HIDDEN>
Date: Mon, 30 Dec 2024 00:28:58 +0000
Message-ID: <m21pxqggj9.fsf@HIDDEN>
MIME-Version: 1.0
Content-Type: text/plain
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

Hi,

Eval Exec <execvy@HIDDEN> writes:

> Hello.
> When I enable rust-ts-mode on a rust file, I found treesitter is easy
> to make emacs buffer to lost color.
> For example, on the following rust code:
> ```rust
>
> struct Dog {
>     name: String,
>     age: u8,
> }
>
>
> struct ManyStruct {
>     a: u8,
> }
>
> fn many_code(){
>     fn fib(n: u32) -> u32 {
>         if n == 0 {
>             return 0;
>         }
>         if n == 1 {
>             return 1;
>         }
>         fib(n - 1) + fib(n - 2)
>     }
> }
>
> fn main() {
>     // change below `//` to `/` to see the difference
>     // {
> }
> ```
>
> the rust code is right, and the emacs buffer color is right on every
> struct/functions.
> But, if I change `// {` to `/ {`, then the rust code is wrong, this
> buffer will lost all colors.

Thanks for reporting this.

I attempted to reproduce this, using your example, when I change `// {`
to `/{` only "main" from `fn main()` loses color. The rest of the syntax
highlighting remains intact in my setup.

                            C. Mitrodimas

> You can see the change on bellow images:
>
> https://imgur.com/a/4Tnv0GJ
>
> I suggest emacs can remain colors even if the code is wrong.
>
> My emacs version info: GNU Emacs 31.0.50

Message sent to bug-gnu-emacs@HIDDEN:

Subject: bug#75164: treesit-font-lock-fontify-region is easy to lost color on parse error. suggest to remain fontify on parse error.
Resent-From: Yuan Fu <casouri@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-gnu-emacs@HIDDEN
Resent-Date: Tue, 31 Dec 2024 21:05:02 +0000
Resent-Message-ID: <handler.75164.B75164.17356790481681 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: Charalampos Mitrodimas <charmitro@HIDDEN>
Cc: Eval Exec <execvy@HIDDEN>, 75164 <at> debbugs.gnu.org
Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51\))
From: Yuan Fu <casouri@HIDDEN>
In-Reply-To: <m21pxqggj9.fsf@HIDDEN>
Date: Tue, 31 Dec 2024 13:02:52 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <3E789578-4ECC-4D96-BA59-F0B400EF32DF@HIDDEN>
References: <CAKfPJDq5i-WaoZ+1-=F1VGxm_2YWTqN45H+7f0Y8+BRFMnM7DQ@HIDDEN>
 <m21pxqggj9.fsf@HIDDEN>
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>



> On Dec 29, 2024, at 4:28=E2=80=AFPM, Charalampos Mitrodimas =
<charmitro@HIDDEN> wrote:
>=20
> Hi,
>=20
> Eval Exec <execvy@HIDDEN> writes:
>=20
>> Hello.
>> When I enable rust-ts-mode on a rust file, I found treesitter is easy
>> to make emacs buffer to lost color.
>> For example, on the following rust code:
>> ```rust
>>=20
>> struct Dog {
>>    name: String,
>>    age: u8,
>> }
>>=20
>>=20
>> struct ManyStruct {
>>    a: u8,
>> }
>>=20
>> fn many_code(){
>>    fn fib(n: u32) -> u32 {
>>        if n =3D=3D 0 {
>>            return 0;
>>        }
>>        if n =3D=3D 1 {
>>            return 1;
>>        }
>>        fib(n - 1) + fib(n - 2)
>>    }
>> }
>>=20
>> fn main() {
>>    // change below `//` to `/` to see the difference
>>    // {
>> }
>> ```
>>=20
>> the rust code is right, and the emacs buffer color is right on every
>> struct/functions.
>> But, if I change `// {` to `/ {`, then the rust code is wrong, this
>> buffer will lost all colors.
>=20
> Thanks for reporting this.
>=20
> I attempted to reproduce this, using your example, when I change `// =
{`
> to `/{` only "main" from `fn main()` loses color. The rest of the =
syntax
> highlighting remains intact in my setup.

It=E2=80=99s indeed strange to see the whole buffer lost fontification. =
I don=E2=80=99t see it either.

Yuan=

Last modified: Sun, 12 Jan 2025 05:45:02 UTC

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