From: Theodor Thornhill <theo@thornhill.no>
To: Stefan Monnier <monnier@iro.umontreal.ca>, Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, dev@rjt.dev
Subject: Re: feature/tree-sitter: Where to Put C/C++ Stuff
Date: Tue, 01 Nov 2022 16:36:53 +0100 [thread overview]
Message-ID: <B294EBA0-2076-4851-B8F3-C0A5FAD328F8@thornhill.no> (raw)
In-Reply-To: <jwv8rkuzpsd.fsf-monnier+emacs@gnu.org>
On 1 November 2022 16:09:39 CET, Stefan Monnier <monnier@iro.umontreal.ca> wrote:
>> Sorry for being blunt, but you've presented a plan for Emacs 32 if
>> not 42.
>
>Huh? What makes you think that?
>
>On the contrary it's a plan that lets us get quickly a working
>tree-sitter-based C-mode. Not one that's a strict superset of CC-mode's
>`c-mode`, but a quite decent `c-mode` nevertheless.
>
No matter what we'll decide on, I'll make these modes and submit it for review in some weeks time. I'm no c++ expert, so I'm bound to make mistakes there, but the others I think I have an idea of how to do.
>
>> Not unless you somehow can summon a team of talented and motivated
>> individuals to work on it starting today. The only practical way
>> I see is by _evolution_, gradually replacing CC Mode's features with
>> tree-sitter supported ones where that makes sense, and at first as
>> opt-in. And yes, this means no "breaking out of CC-mode", at least
>> not as part of this particular effort: it simply is too much, too high
>> a bar to jump. It could well enough kill the effort, for all
>> practical purposes.
>
I'll try to prove you wrong. It seems someone is trying to add it to the proposed cc-treesit.el, so maybe we can have the cake and eat it too ;-)
>
>I don't foresee "all of the stuff" to be done immediately, no.
>[ Tho I do think the filling code at least can be extracted from CC-mode
>within a month (or at least, an important subset of it). ]
>
I think I'll try to make a tree-sitter powered auto-fill.
>Which is why users will have to choose (and we'll stick to CC-mode by
>default, of course).
>
Of course.
Theo
next prev parent reply other threads:[~2022-11-01 15:36 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 2:30 feature/tree-sitter: Where to Put C/C++ Stuff Randy Taylor
2022-11-01 5:44 ` Theodor Thornhill
2022-11-01 7:24 ` Eli Zaretskii
2022-11-01 7:55 ` Theodor Thornhill
2022-11-01 9:22 ` Yuan Fu
2022-11-01 9:41 ` Theodor Thornhill
2022-11-01 9:57 ` Eli Zaretskii
2022-11-01 11:53 ` Theodor Thornhill
2022-11-01 12:28 ` Eli Zaretskii
2022-11-01 13:05 ` Theodor Thornhill
2022-11-01 13:10 ` Eli Zaretskii
2022-11-01 13:27 ` Theodor Thornhill
2022-11-01 13:49 ` Eli Zaretskii
2022-11-01 13:54 ` Theodor Thornhill
2022-11-01 14:03 ` Eli Zaretskii
2022-11-01 14:12 ` Theodor Thornhill
2022-11-01 16:09 ` tomas
2022-11-01 13:12 ` Manuel Uberti
2022-11-04 14:49 ` Benjamin Riefenstahl
2022-11-04 16:17 ` Pascal Quesseveur
2022-11-01 13:32 ` Stefan Monnier
2022-11-01 14:02 ` Eli Zaretskii
2022-11-01 15:09 ` Stefan Monnier
2022-11-01 15:36 ` Theodor Thornhill [this message]
2022-11-01 16:43 ` Eli Zaretskii
2022-11-02 20:43 ` João Távora
2022-11-01 7:20 ` Eli Zaretskii
2022-11-01 12:10 ` 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=B294EBA0-2076-4851-B8F3-C0A5FAD328F8@thornhill.no \
--to=theo@thornhill.no \
--cc=dev@rjt.dev \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).