GNU bug report logs - #61403
30.0.50; C tree-sitter bug?

Previous Next

Full log

Message #23 received at 61403 <at> debbugs.gnu.org (full text, mbox):

From: Po Lu <luangruo <at> yahoo.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 61403 <at> debbugs.gnu.org, casouri <at> gmail.com
Subject: Re: bug#61403: 30.0.50; C tree-sitter bug?
Date: Sun, 12 Feb 2023 20:36:22 +0800

Eli Zaretskii <eliz <at> gnu.org> writes:

>> From: Po Lu <luangruo <at> yahoo.com>
>> Cc: casouri <at> gmail.com,  61403 <at> debbugs.gnu.org
>> Date: Sun, 12 Feb 2023 18:30:41 +0800
>> 
>> Eli Zaretskii <eliz <at> gnu.org> writes:
>> 
>> > I admit I don't understand the problem that is the subject of this
>> > bug.  Why is it wrong to fontify TEST_STATIC as a type?  CC mode also
>> > fontifies it as a type, btw.
>> 
>> Yes, but CC Mode provides `c-noise-macro-names'.  I said something
>> similar should exist in c-ts-mode at the beginning of this thread.
>
> Maybe so, but not for this case: I see absolutely no reason to
> "de-fontify" TEST_STATIC here, as it is part of the type.

It actually ``static'' on TEST builds or nothing at all, not part of the
type.  It ought not to be fontified, just as we don't fontify _Noreturn
or __attribute__ as types.

>> > The only problem I see in what c-ts-mode does is that it does NOT
>> > fontify 'char', whereas CC mode does.  So if anything needs to be done
>> > here, we need to look into why 'char' is not fontified by c-ts-mode.
>> 
>> Apparently tree-sitter thinks only TEST_STATIC is the type, and
>> everything else is a syntactic error.
>
> Whatever the reasons, we need to try to fix this part.

Yes, please.  Also the bit about _Noreturn.

Previous Next

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