From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Theodor Thornhill Newsgroups: gmane.emacs.devel Subject: Re: feature/tree-sitter: Where to Put C/C++ Stuff Date: Tue, 01 Nov 2022 16:36:53 +0100 Message-ID: References: <83pme7cf23.fsf@gnu.org> <83cza6db7e.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="13981"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org, dev@rjt.dev To: Stefan Monnier , Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Nov 01 18:28:26 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1opv3p-0003Mw-Uq for ged-emacs-devel@m.gmane-mx.org; Tue, 01 Nov 2022 18:28:26 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1optKL-00064z-GT; Tue, 01 Nov 2022 11:37:21 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1optKG-00062k-SS for emacs-devel@gnu.org; Tue, 01 Nov 2022 11:37:18 -0400 Original-Received: from out2.migadu.com ([2001:41d0:2:aacc::]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1optKB-0003Z3-6e; Tue, 01 Nov 2022 11:37:16 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=thornhill.no; s=key1; t=1667317027; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=hdULy2v6iW4FjtyCw0Vsi55EjOdvUZV7ajDHSTAa4Fg=; b=HXGo/5afnHvcb5j8m81QHmwZ0te8BnvZjTr8lwlp1lUP7Dfmy/+oTQ4ygQCtRNIO4bAgjP C83zC13LVcUw4Attb82/mfWzABPQaBtiDDioea7wcxWsDkzbfUDIb33vYUhuCCErqII697 yQ5mhOxR4Wjq3w+bht338uNtqyKgqjpO5SQmFl6wmde2rVqWnx6ymrLXkP/Q65S1s7Vc8G aGEk7204vCpt4ofiu9lWuiSdBpMYl9K9PdVsBjBX7NERaZkmffG8gRUQttGDCMk717niWl qWO5gWVeYf1vgwgBr6dy+JG2tjg6dV+3rcVQv6cJdwlw0m4a/AYfnlKqWCF2iA== X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. In-Reply-To: X-Migadu-Flow: FLOW_OUT Received-SPF: pass client-ip=2001:41d0:2:aacc::; envelope-from=theo@thornhill.no; helo=out2.migadu.com X-Spam_score_int: -23 X-Spam_score: -2.4 X-Spam_bar: -- X-Spam_report: (-2.4 / 5.0 requ) BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: "Emacs-devel" Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:298959 Archived-At: On 1 November 2022 16:09:39 CET, Stefan Monnier wrote: >> Sorry for being blunt, but you've presented a plan for Emacs 32 if >> not 42=2E > >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=2E Not one that's a strict superset of CC-mode'= s >`c-mode`, but a quite decent `c-mode` nevertheless=2E > No matter what we'll decide on, I'll make these modes and submit it for re= view in some weeks time=2E 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=2E=20 > >> Not unless you somehow can summon a team of talented and motivated >> individuals to work on it starting today=2E 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=2E 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=2E It could well enough kill the effort, for all >> practical purposes=2E > I'll try to prove you wrong=2E It seems someone is trying to add it to the= proposed cc-treesit=2Eel, so maybe we can have the cake and eat it too ;-)= =20 > >I don't foresee "all of the stuff" to be done immediately, no=2E >[ 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)=2E ] > I think I'll try to make a tree-sitter powered auto-fill=2E=20 >Which is why users will have to choose (and we'll stick to CC-mode by >default, of course)=2E > Of course=2E=20 Theo=20