From: Yuan Fu <casouri@gmail.com>
To: Dmitry Gutov <dmitry@gutov.dev>
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: Wed, 5 Jun 2024 22:28:30 -0700 [thread overview]
Message-ID: <F1B1C8A2-0C35-4EAA-AD57-6D58AFD0147C@gmail.com> (raw)
In-Reply-To: <75899b79-dfec-44dc-adfc-389f046bcd7b@gutov.dev>
[-- Attachment #1: Type: text/plain, Size: 1172 bytes --]
> On May 22, 2024, at 6:33 AM, Dmitry Gutov <dmitry@gutov.dev> wrote:
>
> On 22/05/2024 15:17, Eli Zaretskii wrote:
>>> Date: Wed, 22 May 2024 02:27:08 +0300
>>> Cc:casouri@gmail.com,71070@debbugs.gnu.org
>>> From: Dmitry Gutov<dmitry@gutov.dev>
>>>
>>>> I understand all that, but still: can you (or someone else) answer my
>>>> question about the accepted practices of IDEs in this matter: do they
>>>> highlight the namespace identifiers differently than other
>>>> identifiers, or do they use the same highlighting?
>>> Does the attached screenshot answer the question? It's from VS Code.
>> Thanks. Not sure I get it completely. It seems like namespace names
>> are fontified like class names? They are not fontified like
>> constants.
>
> 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:
[-- Attachment #2: Screenshot 2024-06-05 at 10.27.31 PM.png --]
[-- Type: image/png, Size: 21703 bytes --]
[-- Attachment #3: Type: text/plain, Size: 6 bytes --]
Yuan
next prev parent reply other threads:[~2024-06-06 5:28 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 [this message]
2024-06-06 20:16 ` Dmitry Gutov
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
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=F1B1C8A2-0C35-4EAA-AD57-6D58AFD0147C@gmail.com \
--to=casouri@gmail.com \
--cc=71070@debbugs.gnu.org \
--cc=dmitry@gutov.dev \
--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 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).