unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ergus <spacibba@aol.com>
To: emacs-devel@gnu.org
Subject: A few questions about c++-ts-mode.
Date: Wed, 8 May 2024 00:59:40 +0200	[thread overview]
Message-ID: <fakigaygsqcunvvbm2zscn7qlkxi234f574ul3hl5vrhymm22k@syjmsievkpp3> (raw)
In-Reply-To: fakigaygsqcunvvbm2zscn7qlkxi234f574ul3hl5vrhymm22k.ref@syjmsievkpp3

Hi

There are a few differences between c++-ts-mode and c++-mode that I
don't know if should be reported or they are like that due to some
design choice.

1. 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 properly them
   like (namespace_identifier) and (type_identifier)

2. Doc string comments are fontified like normal comments. It looks like
   treesiter does not recognize them at all. Is this something we need to
   report to treesitter or we need to workaround it in emacs side?

3. macros like `#if defined(something)` fontifies the whole macro with
   same font (the `identifier` used to have no colors in c++-mode)


Somehow related:

Now that there is treesitter, eglot, project.el, improved xref and
completions + flymake... does anyone still use CEDET? If not... is there
some plan to remove it in the future? There is few documentation around
mentioning it and created confusion in new users...

Thanks in advance,
Ergus



       reply	other threads:[~2024-05-07 22:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fakigaygsqcunvvbm2zscn7qlkxi234f574ul3hl5vrhymm22k.ref@syjmsievkpp3>
2024-05-07 22:59 ` Ergus [this message]
2024-05-08  0:19   ` A few questions about c++-ts-mode Yuan Fu
2024-05-08  1:26     ` Ergus
2024-05-09  4:29       ` Yuan Fu
2024-05-09  6:18         ` Filippo Argiolas
2024-05-12 20:11         ` Ergus
2024-05-08 13:35     ` Eli Zaretskii
2024-05-08 21:05       ` Ergus
2024-05-09  0:16         ` Yuan Fu
2024-05-09  5:17           ` Eli Zaretskii
2024-05-09  5:03         ` Eli Zaretskii
2024-05-09  5:34           ` Filippo Argiolas
2024-05-09  5:53             ` Eli Zaretskii
2024-05-09  6:11               ` Filippo Argiolas
2024-05-09  7:03                 ` Eli Zaretskii
2024-05-13  6:23               ` Filippo Argiolas
2024-05-13  8:10                 ` Filippo Argiolas

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=fakigaygsqcunvvbm2zscn7qlkxi234f574ul3hl5vrhymm22k@syjmsievkpp3 \
    --to=spacibba@aol.com \
    --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).