From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Using incremental parsing in Emacs Date: Sat, 11 Jan 2020 14:29:49 +0200 Message-ID: <83r2066urm.fsf@gnu.org> References: <83blrkj1o1.fsf@gnu.org> <838smfahbx.fsf@gnu.org> <83h8128m4r.fsf@gnu.org> Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="59448"; mail-complaints-to="usenet@blaine.gmane.org" Cc: arthur.miller@live.com, emacs-devel@gnu.org To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Jan 11 13:30:42 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iqFuQ-000820-Df for ged-emacs-devel@m.gmane-mx.org; Sat, 11 Jan 2020 13:30:30 +0100 Original-Received: from localhost ([::1]:57094 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iqFuO-0002rP-TJ for ged-emacs-devel@m.gmane-mx.org; Sat, 11 Jan 2020 07:30:28 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:58586) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iqFtk-00027m-Oi for emacs-devel@gnu.org; Sat, 11 Jan 2020 07:29:50 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:47587) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1iqFtk-0006tD-6E; Sat, 11 Jan 2020 07:29:48 -0500 Original-Received: from [176.228.60.248] (port=1407 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1iqFti-0001cn-MA; Sat, 11 Jan 2020 07:29:47 -0500 In-reply-to: (message from Dmitry Gutov on Sat, 11 Jan 2020 15:24:37 +0300) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] 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.org gmane.emacs.devel:244196 Archived-At: > Cc: arthur.miller@live.com, emacs-devel@gnu.org > From: Dmitry Gutov > Date: Sat, 11 Jan 2020 15:24:37 +0300 > > On 11.01.2020 9:53, Eli Zaretskii wrote: > > > Yes, users who want to compile their own parsers, or recompile > > existing ones, will have to have a C compiler installed. Which is a > > downside, but not a serious one in this case, IMO, because most users > > will use existing parser tables. I'd expect most if not all of such > > tables to come together with the Emacs-adapted Tree-Sitter package, or > > be available on ELPA, or even (gasp!) in core. > > ELPA won't solve the necessity to have this code compiled for different > platforms. It will if distros include them. > If we go this route, then Tree-Sitter and some core grammars will have > to be in the core for sure, I'm just worried about the ease of improving > or developing new ones. > > Our users, compared to other editors, are probably the most spoiled (in > a good way) in regards to development iteration speed. > > So, as outlined previously, we might even prefer 10x slower parsing > speed if it comes with faster development cycle. These are all valid concerns, but I'd defer dealing with them once we have the infrastructure for using incremental parsers. Right now, doing so is just a pipe dream, and I think we need to make it more practical.