From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Pankaj Jangid Newsgroups: gmane.emacs.devel Subject: Re: Using incremental parsing in Emacs Date: Fri, 3 Jan 2020 17:09:19 +0000 Organization: J4D Network Message-ID: <0100016f6c62014b-a0a6c998-7896-431c-b236-4864a7a5cc82-000000@email.amazonses.com> References: <83blrkj1o1.fsf@gnu.org> <91f634b6-ea3a-2681-39b8-bda6a3796399@yandex.ru> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="81416"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.60 (darwin) Cc: Eli Zaretskii , Stefan Monnier , emacs-devel@gnu.org To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jan 03 18:09:32 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 1inQS2-000Kzd-00 for ged-emacs-devel@m.gmane.org; Fri, 03 Jan 2020 18:09:30 +0100 Original-Received: from localhost ([::1]:54950 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1inQS0-0001RF-S6 for ged-emacs-devel@m.gmane.org; Fri, 03 Jan 2020 12:09:28 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:33477) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from <0100016f6c62014b-a0a6c998-7896-431c-b236-4864a7a5cc82-000000@amazonses.com>) id 1inQRu-0001Qh-9i for emacs-devel@gnu.org; Fri, 03 Jan 2020 12:09:23 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from <0100016f6c62014b-a0a6c998-7896-431c-b236-4864a7a5cc82-000000@amazonses.com>) id 1inQRt-0003M0-7j for emacs-devel@gnu.org; Fri, 03 Jan 2020 12:09:22 -0500 Original-Received: from a8-95.smtp-out.amazonses.com ([54.240.8.95]:38192) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from <0100016f6c62014b-a0a6c998-7896-431c-b236-4864a7a5cc82-000000@amazonses.com>) id 1inQRs-0003H3-W4; Fri, 03 Jan 2020 12:09:21 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=2i3gzvbgh3d3bo7yfqpvb5eru2hqctky; d=j4d.net; t=1578071360; h=From:To:Cc:Subject:References:Date:In-Reply-To:Message-ID:MIME-Version:Content-Type; bh=h37LSX4BnKh+PK+DcosYTiUNilU23caSRMmUVkt5MWo=; b=HDVdngJyXcMtDTx8gQomna7FTvMuO5XrzUJ9AUzhqP4WywyPsDhaoDm0H2EzTCgg /cqjvXpzNOJ0h+7NPxiBRLUManZ0Zn0GJBhRfrviqop2Z02sbNnkSkKstZuGdMvlR2C kI3YmYZNNLEnUgZgdmwRYp3vpvr0mfhJUvAuIfK4= DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1578071360; h=From:To:Cc:Subject:References:Date:In-Reply-To:Message-ID:MIME-Version:Content-Type:Feedback-ID; bh=h37LSX4BnKh+PK+DcosYTiUNilU23caSRMmUVkt5MWo=; b=Rpu7P/bIg9Qlx09NCcL8ydwfk68gx6ibSS+NYCc2T7rdcXe74Ql4NyrUZ7dF6AeX xKmF0teqtp8U8zAV2ew+j1BMGA+pAcM91P96i/P6KwWVdmiAhhzELZchitcGHjMYfGu ZpGwTJhIDS2n0M86W7XgKGc+O99f1g6w4KrGzI6A= In-Reply-To: <91f634b6-ea3a-2681-39b8-bda6a3796399@yandex.ru> (Dmitry Gutov's message of "Fri, 3 Jan 2020 19:00:39 +0300") X-SES-Outgoing: 2020.01.03-54.240.8.95 Feedback-ID: 1.us-east-1.txOs6RzEvQ8hCXYeLqJ8lVjB3e7LuQl8h6pdq90PbRQ=:AmazonSES X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 54.240.8.95 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:243897 Archived-At: > Tree-Sitter could be an example of how such new grammars could be > structured, but I think we'd need that implemented in Lisp. Not in a > foreign library that we import through modules mechanism. If it is a pure-C library then there is no harm in including it. And for performance reasons, integration must be done at C level. tree-sitter dynamically changes the syntax tree on every character-level change in the input source (it will be buffer in our case). Lisp interface must be there to support customization and integration with other packages. I guess that your intent is same as Eli's intent. But he insists that we come up with the design first.