From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Ihor Radchenko Newsgroups: gmane.emacs.devel Subject: Re: tree-sitter: conceptional problem solvable at Emacs' level? Date: Sat, 11 Feb 2023 09:34:42 +0000 Message-ID: <87bkm0czpp.fsf@localhost> References: <87zg9n45ig.fsf@yahoo.com> <0DDF6978-D75A-4137-9D93-6200908675B6@gmail.com> <837cwplxni.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="11961"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Yuan Fu , luangruo@yahoo.com, holgerschurig@gmail.com, Emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Feb 11 10:34:58 2023 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 1pQmHa-0002r6-AN for ged-emacs-devel@m.gmane-mx.org; Sat, 11 Feb 2023 10:34:58 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pQmGt-0004XO-KQ; Sat, 11 Feb 2023 04:34:15 -0500 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 1pQmGs-0004X8-DR for Emacs-devel@gnu.org; Sat, 11 Feb 2023 04:34:14 -0500 Original-Received: from mout01.posteo.de ([185.67.36.65]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pQmGp-000390-UB for Emacs-devel@gnu.org; Sat, 11 Feb 2023 04:34:13 -0500 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 44C7C2404DD for ; Sat, 11 Feb 2023 10:34:08 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1676108049; bh=LyzPeDG/CoMvkNcIgg/edMJ7ouQnC4NmZEfy0N4lo7s=; h=From:To:Cc:Subject:Date:From; b=HoWdGFmEPtud6y6tXcyZWjI+QtGmabUrXpznESthXbDVZnIZ17mRyc3SPpCS3Y8rW iJut1Qa6CkVQDY3L/Y7S0/JZ1ON3olxkXlbaoCnc/RXcm0WSkqi2ROuHhiSlaJiB4s fAHJzbUxrFBnI/yB0UsOQrZVryQUNK5UdeyAil/HKK0phS6dmRVsgJd7zTyXmn7aVR cc4geuWuPwI+e0JTEgV8XolD9LcUc7cNX/NHyb4h52YSBLPpUFBcOM28j9o91pp+i7 ufAv7S+dwtpQDpPEfecpzUsr0D/9CR/XpOZWwN/3Yhr6FaNuX23g5uphC+veX+5ysa tx70PUwccxXeA== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4PDQR16n7dz9rxF; Sat, 11 Feb 2023 10:34:04 +0100 (CET) In-Reply-To: <837cwplxni.fsf@gnu.org> Received-SPF: pass client-ip=185.67.36.65; envelope-from=yantar92@posteo.net; helo=mout01.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 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, RCVD_IN_DNSWL_MED=-2.3, 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.29 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:303133 Archived-At: Eli Zaretskii writes: > Another possibility is to complicate the function we pass to > tree-sitter with which to read buffer text, in a way that replaces the > text of a macro with something else (in the simplest case, just space > characters), so as to avoid errors in the parser, and again analyze > the macros in our own code. Another idea is delegating parts of buffer to Elisp/alternative parser. Tree sitter provides support to documents written using a mixture of grammars: https://tree-sitter.github.io/tree-sitter/using-parsers#multi-language-documents Macros can be considered such a "mixed" grammar with macros being a grammar of their own. AFAIU, tree sitter allows excluding certain file ranges from parsing and instead parse the excluded ranges using alternative grammar. If Elisp can somehow tell tree-sitter backend not skip parsing macro-looking lines, it should solve the problem at least partially. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at