unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Alan Mackenzie <acm@muc.de>, Yuan Fu <casouri@gmail.com>
Cc: 64830@debbugs.gnu.org
Subject: bug#64830: 30.0.50 C++ treesitter mode no coloration
Date: Thu, 15 Aug 2024 08:25:34 +0300	[thread overview]
Message-ID: <868qwy8ii9.fsf@gnu.org> (raw)
In-Reply-To: <ZrzqybAS3GVfrvX0@ACM> (message from Alan Mackenzie on Wed, 14 Aug 2024 17:35:05 +0000)

> Date: Wed, 14 Aug 2024 17:35:05 +0000
> From: Alan Mackenzie <acm@muc.de>
> 
> Hello, Emacs.
> 
> In my emacs-30 build (updated earlier today), C++ source in c++-ts-mode
> is not getting fontified, except for comments and preprocessor
> constructs.

I cannot reproduce this, at least not with a random C++ source file I
tried to.  Does this happen for you in "emacs -Q" and for every C++
file?

If this happens with any file and in 'emacs -Q", do you see redisplay
error messages in *Messages*?  If so, what are those messages?

> I think I'm using tree-sitter-cpp version 0.22.2 as downloaded from the
> Gentoo repository.  Is there an easy way to check this from inside
> Emacs?

No, not AFAIK.  And the problem is not the version of tree-sitter, it
is usually the version of the C++ grammar library.  Do you know the
version of that one you have installed?

> This would appear to be bug 64818/64830, which are still open in
> debbugs.  Shouldn't they be closed before the first/next emacs-30
> pretest?

Those bugs were fixed.  The reason they are not closed is that we
raised a more general issue there, and that is not yet resolved.





  reply	other threads:[~2024-08-15  5:25 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-24  9:13 bug#64830: 29.1; C++ treesitter mode no coloration David Come
2023-07-24 12:32 ` Eli Zaretskii
2024-08-14 17:35 ` bug#64830: 30.0.50 " Alan Mackenzie
2024-08-15  5:25   ` Eli Zaretskii [this message]
2024-08-16 16:44     ` Alan Mackenzie
2024-08-16 17:40       ` Eli Zaretskii
2024-08-16 17:45         ` Eli Zaretskii
2024-08-16 18:06           ` Alan Mackenzie
2024-08-16 18:27             ` Eli Zaretskii
2024-08-20  3:46               ` Yuan Fu
2024-08-24 18:35                 ` Yuan Fu
2024-08-24 19:38                   ` Alan Mackenzie
2024-08-24 20:43                     ` Yuan Fu
2024-08-25  2:19                       ` Alan Mackenzie
2024-08-25  4:54                         ` Eli Zaretskii
2024-08-25 12:08                           ` Alan Mackenzie
2024-08-25 12:17                             ` Eli Zaretskii
2024-08-25 22:40                         ` Yuan Fu
2024-08-26 17:25                           ` Alan Mackenzie
2024-08-26 17:51                             ` Eli Zaretskii
2024-08-26 19:50                               ` Alan Mackenzie
2024-08-26 22:25                                 ` Stefan Kangas
2024-08-27  1:58                                   ` Yuan Fu
2024-08-27 12:09                                     ` Eli Zaretskii
2024-08-28  5:36                                       ` Yuan Fu
2024-08-28 12:33                                         ` Eli Zaretskii
2024-08-29  4:54                                           ` Yuan Fu
2024-08-29  6:01                                             ` Eli Zaretskii
2024-09-11  5:09                                               ` Yuan Fu
2024-09-11 12:09                                                 ` Eli Zaretskii
2024-09-12  8:06                                                   ` Yuan Fu
2024-08-27 12:01                                 ` Eli Zaretskii
2024-08-27 11:03                             ` 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=868qwy8ii9.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=64830@debbugs.gnu.org \
    --cc=acm@muc.de \
    --cc=casouri@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).