unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>
Cc: acm@muc.de, 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 20:44:52 +0200	[thread overview]
Message-ID: <fc53378e-1fe9-e35d-2318-62ca765a408c@yandex.ru> (raw)
In-Reply-To: <838rhdthsl.fsf@gnu.org>

On 04/02/2023 20:19, Eli Zaretskii wrote:
>> Date: Sat, 04 Feb 2023 20:13:20 +0200
>> From: Eli Zaretskii<eliz@gnu.org>
>> Cc:acm@muc.de,emacs-devel@gnu.org
>>
>>> Date: Sat, 4 Feb 2023 19:32:11 +0200
>>> From: Dmitry Gutov<dgutov@yandex.ru>
>>>
>>> On 04/02/2023 16:49, Alan Mackenzie wrote:
>>>> Setting treesit-font-lock-level to 2 for c-ts-mode fontifies variable
>>>> definitions, but not parameter definitions.
>>> The patch below seems to fix that (the functionality was basically
>>> implemented already). I suggest we install it on emacs-29, for
>>> consistency with other modes, among other things.
>> AFAIU, this patch will fontify variables in function parameter lists
>> at level 1, not 2, but I don't mind.
> Btw, we should probably do the same for C++ and Java.

AFAICS, Java has this already, and c++-ts-mode will be affected by the 
proposed patch (c and c++ share c-ts-mode--font-lock-settings).



  reply	other threads:[~2023-02-04 18:44 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
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 [this message]
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=fc53378e-1fe9-e35d-2318-62ca765a408c@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=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).