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: cc-mode fontification feels random Date: Sat, 12 Jun 2021 19:53:27 +0200 Message-ID: References: <83im2lbqmv.fsf@gnu.org> <179f6e4fa40.2816.cc5b3318d7e9908e2c46732289705cb0@dancol.org> <83fsxpbpn9.fsf@gnu.org> <83k0n09tkp.fsf@gnu.org> <837dj09p0e.fsf@gnu.org> <20210611232535.b4dyu3a2yxvdixys@Ergus> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="15496"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Ergus , Eli Zaretskii , dancol@dancol.org, acm@muc.de, rudalics@gmx.at, emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Jun 12 19:54:47 2021 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 1ls7qI-0003o1-KJ for ged-emacs-devel@m.gmane-mx.org; Sat, 12 Jun 2021 19:54:46 +0200 Original-Received: from localhost ([::1]:35036 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ls7qH-00020r-M3 for ged-emacs-devel@m.gmane-mx.org; Sat, 12 Jun 2021 13:54:45 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:41878) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ls7p7-0001II-I0 for emacs-devel@gnu.org; Sat, 12 Jun 2021 13:53:33 -0400 Original-Received: from out1.migadu.com ([2001:41d0:2:863f::]:19744) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ls7p5-0005Az-LC; Sat, 12 Jun 2021 13:53:33 -0400 X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=thornhill.no; s=key1; t=1623520408; 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: in-reply-to:in-reply-to:references:references; bh=msVbmlDJbAt0yOyKMWR7t31mdJeE7aFKjTDHH31ZcjY=; b=lRMZfsLm3OT/tvrrPfAGfJ6eez5BDUGCPXryGF2n2x/owd6VNo7hoizMQEL+myXZ4loK9j C1CJZo5EihrHNqtpyzngB6HihxPUw+ZPv4CN8sC5u4+VQ/hmD/vzQJhTEXuHHkh9ADl4xN BZwuA9razDgvB5bdjENrjskqy7oiwwjZ2vikB1+RqpDJ1zNrZb+1lXnFNtQsmJfXZjO7TH oi8pkm9H149qlqPqCqhGdS2Fz7YN5m60d2RdgcEtH55aKdyQHHOsV+PA8wq+DmQJKNN9sC M3GDlKwXvDD0XGAqMy9jVsLjv1pKNMcPU2L82tKsxtwUPCFpTjEMEhCE98CDEw== In-Reply-To: X-Migadu-Flow: FLOW_OUT X-Migadu-Auth-User: theo@thornhill.no Received-SPF: pass client-ip=2001:41d0:2:863f::; envelope-from=theo@thornhill.no; helo=out1.migadu.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=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.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:270777 Archived-At: Stefan Monnier writes: >>> Agreed. Maybe a first step would be to get copyright assignments and >>> include the tree sitter module in GNU ELPA? >> If I read some of these mails correctly it seems like that wouldn't be >> possible due to interest from some of the parties involved in the main >> package. I don't know the details on that, though. > > Before we start a parallel effort, we definitely should make every effort > to get copyright assignments for the existing code. Maybe we can't take > the package as-is because some contributors won't accept to sign the > paperwork, but we can probably get paperwork for a significant fraction > of the code. Sure - I can open an issue and see where we're at. > >> And Eli seems unhappy with what's there. > > That doesn't mean we have to start over from scratch. > No, absolutely. >> As for making a little more concrete proposal for how to move forward, >> would this be something like what we want? >> - create/use c or rust bindings > > I think we'd want to link to the C API of tree-sitter. > There's no point going through Rust at this point, AFAICT. > >> - create an elisp-layer for interaction with the parse tree >> - hook fontification and indentation into that elisp-layer > > Sounds about right. > Ok good! -- Theo