From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: c-ts-mode: (eq treesit-font-lock-level 2) doesn't fontify parameter names.
Date: Sat, 4 Feb 2023 16:36:25 +0000 [thread overview]
Message-ID: <Y96Jifq6JcqY8Hlg@ACM> (raw)
In-Reply-To: <83o7q9tqta.fsf@gnu.org>
Hello, Eli.
On Sat, Feb 04, 2023 at 17:04:33 +0200, Eli Zaretskii wrote:
> > Date: Sat, 4 Feb 2023 14:49:15 +0000
> > From: Alan Mackenzie <acm@muc.de>
> > Setting treesit-font-lock-level to 2 for c-ts-mode fontifies variable
> > definitions, but not parameter definitions.
> Thanks for the report, but please report this as a bug, and please
> provide a reproducer (what are "parameter definitions"?).
Done.
> > There appears to be no (documented) way to get traditional C Mode
> > fontification back. Perhaps there should be.
> How can one know what are "traditional C Mode fontifications"? Is
> there any concise description of those, in terms of C language
> grammar? If there is such a description, can you point us to it? And
> if it doesn't exist, could you perhaps produce one?
My saying "traditional C Mode fontification" was just a pompous way of
saying "parameters fontified as well as variables", but avoiding
repetition. Sorry for the misunderstanding.
There is no such description, and I can't see that it would be very
helpful to anybody, particularly considering the time taken to write it.
It would be thoroughly unreasonable to expect c-ts-mode to fontify
identically to C Mode in every respect. But I think having declarations
of both parameters and variables fontified, but not their uses, is a
worthwhile strategy.
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2023-02-04 16:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-04 14:49 c-ts-mode: (eq treesit-font-lock-level 2) doesn't fontify parameter names Alan Mackenzie
2023-02-04 15:04 ` Eli Zaretskii
2023-02-04 16:36 ` Alan Mackenzie [this message]
2023-02-04 16:59 ` Eli Zaretskii
2023-02-04 17:32 ` Dmitry Gutov
2023-02-04 18:13 ` Eli Zaretskii
2023-02-04 18:16 ` Dmitry Gutov
2023-02-04 18:19 ` Eli Zaretskii
2023-02-04 18:44 ` Dmitry Gutov
2023-02-04 20:09 ` Alan Mackenzie
2023-02-04 20:19 ` Eli Zaretskii
2023-02-04 20:42 ` Alan Mackenzie
2023-02-05 5:33 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y96Jifq6JcqY8Hlg@ACM \
--to=acm@muc.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).