From: Dmitry Gutov <dmitry@gutov.dev>
To: Yuan Fu <casouri@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, Ergus <spacibba@aol.com>,
71070@debbugs.gnu.org
Subject: bug#71070: 30.0.50; c++-ts-mode namespace wrong fontification.
Date: Thu, 6 Jun 2024 23:16:18 +0300 [thread overview]
Message-ID: <c2215ab1-2637-45ef-a25e-7aec754b50f7@gutov.dev> (raw)
In-Reply-To: <F1B1C8A2-0C35-4EAA-AD57-6D58AFD0147C@gmail.com>
On 06/06/2024 08:28, Yuan Fu wrote:
>> Seems like it (although some themes might use some additional colors to differentiate between these two, the default theme does not).
>>
>> Perhaps it is done so that the expression foo::class_name reads naturally (in one color).
> Am I missing something? I got the exact opposite conclusion from the screenshot: it seems the effect is that namespaces are colored differently from class names:
The class names I meant are A and B on my screenshot.
Maybe tree-sitter doesn't see them as class names specifically, just
non-primitive identifiers in type position.
next prev parent reply other threads:[~2024-06-06 20:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87h6et6550.fsf.ref@aol.com>
2024-05-19 18:14 ` bug#71070: 30.0.50; c++-ts-mode namespace wrong fontification Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-19 18:36 ` Eli Zaretskii
2024-05-19 19:00 ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-19 19:13 ` Eli Zaretskii
2024-05-19 21:36 ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-20 11:11 ` Eli Zaretskii
2024-05-21 23:27 ` Dmitry Gutov
2024-05-22 6:23 ` Yuan Fu
2024-05-22 12:17 ` Eli Zaretskii
2024-05-22 13:33 ` Dmitry Gutov
2024-06-06 5:28 ` Yuan Fu
2024-06-06 20:16 ` Dmitry Gutov [this message]
2024-06-15 8:34 ` Eli Zaretskii
2024-06-19 6:27 ` Yuan Fu
2024-06-19 11:52 ` Eli Zaretskii
2024-06-21 1:53 ` Yuan Fu
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c2215ab1-2637-45ef-a25e-7aec754b50f7@gutov.dev \
--to=dmitry@gutov.dev \
--cc=71070@debbugs.gnu.org \
--cc=casouri@gmail.com \
--cc=eliz@gnu.org \
--cc=spacibba@aol.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.