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, 04 Jan 2020 10:23:50 +0200 Message-ID: <83o8vjhbop.fsf@gnu.org> References: <83blrkj1o1.fsf@gnu.org> <86zhf4gwhl.fsf@stephe-leake.org>,<83tv5cgvar.fsf@gnu.org> Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="130428"; mail-complaints-to="usenet@blaine.gmane.org" Cc: stephen_leake@stephe-leake.org, emacs-devel@gnu.org To: arthur miller Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jan 04 09:24:17 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane.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 1inejJ-000Xno-I9 for ged-emacs-devel@m.gmane.org; Sat, 04 Jan 2020 09:24:17 +0100 Original-Received: from localhost ([::1]:60530 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1inejH-0001LU-SJ for ged-emacs-devel@m.gmane.org; Sat, 04 Jan 2020 03:24:15 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:60392) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ineis-0000wq-CX for emacs-devel@gnu.org; Sat, 04 Jan 2020 03:23:51 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:49428) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ineir-0004qr-80; Sat, 04 Jan 2020 03:23:49 -0500 Original-Received: from [176.228.60.248] (port=4245 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1ineiq-000060-Me; Sat, 04 Jan 2020 03:23:49 -0500 In-reply-to: (message from arthur miller on Fri, 3 Jan 2020 22:21:16 +0000) 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.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:243909 Archived-At: > From: arthur miller > CC: "emacs-devel@gnu.org" > Date: Fri, 3 Jan 2020 22:21:16 +0000 > > When it comes to tree-sitter which you linked to, I didn't understand from their website how they deal with > compile time dependencies and various configuration options that are usually passed via configure & co. You can ask them a question, but in general, some jobs related to this don't need to understand that stuff. E.g., our font-lock doesn't, and it still does a pretty decent job. > Another thing is, about "speed-wise", if Enacs core implemented support for creating language servers, or > plugging in them, as well as clients, then maybe it would be possible to use share memory for passing round > those big json files that lsp-mode like to play with. That might also let Emacs reuse existing tools like > lsp-mode. I think they are using sockets now, I am not sure though. Using JSON as the middleware adds a non-trivial processing overhead, so if we can avoid that, we should.