unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Gregory Heytings <gregory@heytings.org>
Cc: Po Lu <luangruo@yahoo.com>, Eli Zaretskii <eliz@gnu.org>,
	emacs-devel@gnu.org
Subject: Re: CC Mode troubles and Emacs 29
Date: Tue, 10 Jan 2023 17:05:55 +0000	[thread overview]
Message-ID: <Y72a8/1Jn6a7BRO0@ACM> (raw)
In-Reply-To: <56368889cb3747e0b245@heytings.org>

Hello, Gregory.

On Tue, Jan 10, 2023 at 10:06:32 +0000, Gregory Heytings wrote:

> >> That's not a tree-sitter problem per se, it's "only" a matter of 
> >> someone taking the time to define a tree-sitter grammar for these 
> >> variants of the C language.  What is not possible is to define "one 
> >> grammar to rule them all", IOW, one grammar that would magically 
> >> recognize in which variant of the C language a given file is written.

> > CC Mode happens to do that fine.

> I fear you contradict yourself.  You cannot say, in a thread which you 
> started to explain that CC Mode fontification is broken (it "fills the 
> buffer with green splotches (making fontification useless)"), that CC Mode 
> fontification works fine.

There is no contradiction in what Po said.  The fact that CC Mode
fontification has bugs in no way contradicts its ability to parse older
variants of C as well as newer ones.

-- 
Alan Mackenzie (Nuremberg, Germany).



  reply	other threads:[~2023-01-10 17:05 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <874jt0hw7p.fsf.ref@yahoo.com>
2023-01-09  9:51 ` CC Mode troubles and Emacs 29 Po Lu
2023-01-09 12:31   ` Eli Zaretskii
2023-01-09 13:49     ` Po Lu
2023-01-09 15:48       ` Alan Mackenzie
2023-01-09 16:56         ` Eli Zaretskii
2023-01-10  1:05           ` Po Lu
2023-01-10 12:57             ` Eli Zaretskii
2023-01-10 14:13               ` Gregory Heytings
2023-01-11  1:36                 ` Po Lu
2023-01-11  1:46                   ` Po Lu
2023-01-11  9:27                   ` Gregory Heytings
2023-01-11 10:12                     ` Po Lu
2023-01-11 13:27                       ` Eli Zaretskii
2023-01-11 14:17                         ` Po Lu
2023-01-11 14:27                           ` Gregory Heytings
2023-01-10 17:37               ` Alan Mackenzie
2023-01-10 17:50                 ` Eli Zaretskii
2023-01-09 16:36       ` Eli Zaretskii
2023-01-10  9:26       ` Gregory Heytings
2023-01-10  9:49         ` Po Lu
2023-01-10 10:06           ` Gregory Heytings
2023-01-10 17:05             ` Alan Mackenzie [this message]
2023-01-09 15:52   ` 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=Y72a8/1Jn6a7BRO0@ACM \
    --to=acm@muc.de \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=gregory@heytings.org \
    --cc=luangruo@yahoo.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).