From: Yuan Fu <casouri@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Tree-sitter C grammar moves to support K&R C
Date: Fri, 18 Aug 2023 22:08:32 -0700 [thread overview]
Message-ID: <661DC453-000E-4469-B38F-D0E5A3BCC1D4@gmail.com> (raw)
In-Reply-To: <83r0o7cxzs.fsf@gnu.org>
> On Aug 12, 2023, at 10:28 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>
> See
>
> https://github.com/tree-sitter/tree-sitter-c/commit/b493a9c6be23e05a85d500ebc83da7bda1ec2f56
>
> Yuan, do we need to change anything in our c-ts-mode to take advantage
> of this support?
From what I can see, no. The grammar changes are internal, it’s just function_definition now recognizes K&R styles of definitions.
Yuan
next prev parent reply other threads:[~2023-08-19 5:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-13 5:28 Tree-sitter C grammar moves to support K&R C Eli Zaretskii
2023-08-19 5:08 ` Yuan Fu [this message]
2023-08-19 6:35 ` 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=661DC453-000E-4469-B38F-D0E5A3BCC1D4@gmail.com \
--to=casouri@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.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).