From: Eli Zaretskii <eliz@gnu.org>
To: Ergus <spacibba@aol.com>, Yuan Fu <casouri@gmail.com>
Cc: 71784@debbugs.gnu.org
Subject: bug#71784: 31.0.50; Inconsistent fontification for field_identifier in c++-ts-mode
Date: Wed, 26 Jun 2024 18:46:04 +0300 [thread overview]
Message-ID: <8634oz9077.fsf@gnu.org> (raw)
In-Reply-To: <87pls394h0.fsf@aol.com> (bug-gnu-emacs@gnu.org)
> Date: Wed, 26 Jun 2024 16:13:47 +0200
> From: Ergus via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
> Using the c++-ts-mode I found that there is some inconsistent
> fontification for the `fields_identifier`:
>
> See the fontification in this example with `emacs -Q`.
>
> ```test.cpp
>
> std::string key;
> bool inserted;
>
> struct name_t {
> std::string key;
> bool inserted;
> };
>
> name_t keys = {"aaa", true};
>
> keys.inserted = false;
> bool a = keys.inserted;
> ```
>
> 1. The `keys.inserted` values are shown differently before or after the
> = (the inserted word is fontified is some cases, but not in all)
>
> 2. The variable names are fontified differently outside or
> inside the struct.
>
> 3. The escape sequence (\t) is fontified differently to the rest of the
> text inside the string. I don't know if that is intentional or not. If
> it is intentional, just ignore this comment.
>
> The inconsistencies 1 and 2 are not only different to c++-mode but they
> are semantically incorrect.
What does treesit-explore-mode tell you about these instances of
keys.inserted?
next prev parent reply other threads:[~2024-06-26 15:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87pls394h0.fsf.ref@aol.com>
2024-06-26 14:13 ` bug#71784: 31.0.50; Inconsistent fontification for field_identifier in c++-ts-mode Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-26 15:46 ` Eli Zaretskii [this message]
2024-06-26 22:24 ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-27 7:16 ` Yuan Fu
2024-06-27 14:33 ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-17 6:27 ` Yuan Fu
2024-08-04 7:13 ` 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=8634oz9077.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=71784@debbugs.gnu.org \
--cc=casouri@gmail.com \
--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).