unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ergus via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 71070@debbugs.gnu.org
Subject: bug#71070: 30.0.50; c++-ts-mode namespace wrong fontification.
Date: Sun, 19 May 2024 20:14:19 +0200	[thread overview]
Message-ID: <87h6et6550.fsf@aol.com> (raw)
In-Reply-To: 87h6et6550.fsf.ref@aol.com


Following up the conversation in the develops mailing list I will report
this issue still happening:

In c++-ts-mode, the namespaces are not fontified like in c++-mode

(i.e in std::string the `std` used to have font-lock-constant-face while
`string` used to have font-lock-type-face).

It seems like tresitter identifies them properly like
(namespace_identifier) and (type_identifier), but the fontification rule
is wrong.

There was an attempt to fix it in c6a5aae3da17459be7550c but the issue
is still there.

Best,
Ergus






       reply	other threads:[~2024-05-19 18:14 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 ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-05-19 18:36   ` bug#71070: 30.0.50; c++-ts-mode namespace wrong fontification 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
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=87h6et6550.fsf@aol.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=71070@debbugs.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).