unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Colascione <dancol@dancol.org>, Alan Mackenzie <acm@muc.de>
Cc: 62339@debbugs.gnu.org
Subject: bug#62339: cc-mode fontifies variables incorrectly when const follows type
Date: Wed, 22 Mar 2023 17:12:52 +0200	[thread overview]
Message-ID: <83ttyc6cqz.fsf@gnu.org> (raw)
In-Reply-To: <87y1no6f6d.fsf@dancol.org> (message from Daniel Colascione on Wed, 22 Mar 2023 10:19:55 -0400)

> From: Daniel Colascione <dancol@dancol.org>
> Cc: 62339@debbugs.gnu.org
> Date: Wed, 22 Mar 2023 10:19:55 -0400
> 
> This problem reproduces for me on latest master with emacs -Q:
> 
> ```
> TEST(Foo, Bar) {
>   NamedTemporaryDirectory const test_directory;
> }
> ```

Thanks.  What I see with Emacs built from master is that
test_directory in the above example gets font-lock-type-face in
c++-mode (but not in c-mode).  With Emacs built from emacs-29, both
modes produce correct fontification.

Alan, can you please look into this?





  reply	other threads:[~2023-03-22 15:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-21 15:14 bug#62339: cc-mode fontifies variables incorrectly when const follows type Daniel Colascione
2023-03-21 17:39 ` Eli Zaretskii
2023-03-22 14:19   ` Daniel Colascione
2023-03-22 15:12     ` Eli Zaretskii [this message]
2023-03-22 22:14       ` Alan Mackenzie
2023-03-22 22:17         ` Daniel Colascione
2023-03-23  0:42           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-23  2:02             ` Daniel Colascione
2023-03-23  5:45               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-23  7:22                 ` Eli Zaretskii
2023-03-23 14:40           ` Alan Mackenzie
2023-04-05 15:53             ` Alan Mackenzie
2023-04-06  3:16               ` Daniel Colascione
2023-04-06  9:26                 ` Alan Mackenzie

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=83ttyc6cqz.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=62339@debbugs.gnu.org \
    --cc=acm@muc.de \
    --cc=dancol@dancol.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).