From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: acm@muc.de, Yuan Fu <casouri@gmail.com>,
75226@debbugs.gnu.org, jacob.fai@gmail.com
Subject: bug#75226: [31.0.50] C++ ts-mode missing "alignof" as keyword
Date: Wed, 8 Jan 2025 14:49:46 +0000 [thread overview]
Message-ID: <Z36QigiCqQtjiHQc@MAC.fritz.box> (raw)
In-Reply-To: <867c754gi9.fsf@gnu.org>
Hello, Eli and Jacob.
On Wed, Jan 08, 2025 at 14:49:50 +0200, Eli Zaretskii wrote:
> > From: Yuan Fu <casouri@gmail.com>
> > Date: Tue, 7 Jan 2025 19:09:40 -0800
> > Cc: Jacob Faibussowitsch <jacob.fai@gmail.com>,
> > 75226@debbugs.gnu.org
> > I found that both c++-mode and c++-ts-mode fontifies C++ alternative
> > operators like and_eq, xor, etc as keywords. Maybe we should fontify
> > them in operator face (added in Emacs 29) instead?
> What do other editors do?
> Alan, WDYT about this?
For me personally, another face for "alphabetic operators" would
come dangerously close to angry fruit salad.
and_eq, xor, etc. _are_ keywords, so I think it makes sense to fontify
them as such. The keywords in C++ could be divided into several
categories, including alphabetic operators, and to give each category
its own face would, I think, overload the typical user, who wouldn't
instantly grasp what all the faces meant. This would be
counterproductive. I don't think it makes too much sense to single out
just one category of keywords for special treatment.
Currently, C++ Mode has just two faces for these things:
font-lock-keyword-face for alphabetic ones, and the default-face for
those consisting of symbol characters like =, +, ;, ..... This is
adequate, probably, for someone whose native language uses a Latin
script. Maybe users of other languages see things differently.
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2025-01-08 14:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-31 16:01 bug#75226: [31.0.50] C++ ts-mode missing "alignof" as keyword Jacob Faibussowitsch
2025-01-02 3:28 ` Yuan Fu
2025-01-02 5:06 ` Stefan Kangas
2025-01-02 6:41 ` Eli Zaretskii
2025-01-02 14:03 ` Jacob Faibussowitsch
2025-01-02 15:47 ` Eli Zaretskii
2025-01-03 8:50 ` Yuan Fu
2025-01-03 11:38 ` Eli Zaretskii
2025-01-04 7:34 ` Yuan Fu
2025-01-08 3:09 ` Yuan Fu
2025-01-08 12:49 ` Eli Zaretskii
2025-01-08 13:58 ` Jacob Faibussowitsch
2025-01-08 14:49 ` Alan Mackenzie [this message]
2025-01-08 17:12 ` Dmitry Gutov
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=Z36QigiCqQtjiHQc@MAC.fritz.box \
--to=acm@muc.de \
--cc=75226@debbugs.gnu.org \
--cc=casouri@gmail.com \
--cc=eliz@gnu.org \
--cc=jacob.fai@gmail.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).