From: Eli Zaretskii <eliz@gnu.org>
To: Yuan Fu <casouri@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Mode names for C-like tree-sitter modes
Date: Mon, 14 Nov 2022 21:04:44 +0200 [thread overview]
Message-ID: <831qq5jr1v.fsf@gnu.org> (raw)
In-Reply-To: <3C23FEAC-6550-48BE-91A3-443B44717C40@gmail.com> (message from Yuan Fu on Sun, 13 Nov 2022 17:16:13 -0800)
> From: Yuan Fu <casouri@gmail.com>
> Date: Sun, 13 Nov 2022 17:16:13 -0800
>
> I think it’s fair to make C, C++ and Java modes independent, since all the cc-mode options are invalidated when we use tree-sitter. However, their name could be improved, IMO. But I can’t think of anything better than c-ts-mode :-)
>
> (neo-c-mode… just saying)
I don't object to better names, but they should be better.
"neo-SOMETHING" doesn't strike me as better, because being "new" is a
momentary state.
> CSS and JSON could be merged with current modes, I think. Css-ts-mode could merge with css-mode, and json-ts-mode could be merged with js-json-mode. Or we can just have a dedicated json-mode.
If they can be joined, I'd prefer that, as explained in another mail I
just sent.
next prev parent reply other threads:[~2022-11-14 19:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 1:16 Mode names for C-like tree-sitter modes Yuan Fu
2022-11-14 6:34 ` Theodor Thornhill
2022-11-14 9:09 ` Yuan Fu
2022-11-14 9:49 ` Theodor Thornhill
2022-11-14 10:07 ` Theodor Thornhill
2022-11-14 10:17 ` Simen Heggestøyl
2022-11-15 2:49 ` Stefan Monnier
2022-11-14 19:04 ` Eli Zaretskii [this message]
2022-11-15 4:17 ` Richard Stallman
2022-11-15 6:33 ` Theodor Thornhill
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=831qq5jr1v.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=casouri@gmail.com \
--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).