From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stephen Leake Newsgroups: gmane.emacs.devel Subject: Re: How to add pseudo vector types Date: Thu, 29 Jul 2021 16:01:59 -0700 Message-ID: <8635rwpvvc.fsf@stephe-leake.org> References: <83h7gw6pyj.fsf@gnu.org> <8335s64v10.fsf@gnu.org> <5380C92B-6C15-4490-A1E0-1C3132DBB16A@gmail.com> <83k0li2shw.fsf@gnu.org> <86wnpg82v3.fsf@stephe-leake.org> <83lf5wyn0z.fsf@gnu.org> <86pmv66yqg.fsf@stephe-leake.org> <83a6maw705.fsf@gnu.org> <83r1fluikh.fsf@gnu.org> <88007ACB-31E5-440F-876D-9F43C8EE02CC@gmail.com> <86fsw05lom.fsf@stephe-leake.org> <8A3823DD-5D5A-4A33-8EF9-93F05497CE4C@gmail.com> <864kcf5cmv.fsf_-_@stephe-leake.org> <18D745F5-DBB1-46CC-91D3-4ADAA9D37AB9@gmail.com> <834kcetmly.fsf@gnu.org> <831r7itjc8.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="18841"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (windows-nt) Cc: Yuan Fu , emacs-devel@gnu.org, cpitclaudel@gmail.com, monnier@iro.umontreal.ca To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Jul 30 01:03:39 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 1m9F3y-0004ip-6j for ged-emacs-devel@m.gmane-mx.org; Fri, 30 Jul 2021 01:03:38 +0200 Original-Received: from localhost ([::1]:59052 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1m9F3w-0002Cs-Eo for ged-emacs-devel@m.gmane-mx.org; Thu, 29 Jul 2021 19:03:36 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:47782) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1m9F2W-00015l-6P for emacs-devel@gnu.org; Thu, 29 Jul 2021 19:02:08 -0400 Original-Received: from gateway34.websitewelcome.com ([192.185.149.105]:43632) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1m9F2U-0005d4-6H for emacs-devel@gnu.org; Thu, 29 Jul 2021 19:02:07 -0400 Original-Received: from cm13.websitewelcome.com (cm13.websitewelcome.com [100.42.49.6]) by gateway34.websitewelcome.com (Postfix) with ESMTP id 833B6D8B8 for ; Thu, 29 Jul 2021 18:02:04 -0500 (CDT) Original-Received: from host2007.hostmonster.com ([67.20.76.71]) by cmsmtp with SMTP id 9F2SmmdUdrJtZ9F2SmTJpJ; Thu, 29 Jul 2021 18:02:04 -0500 X-Authority-Reason: nr=8 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=stephe-leake.org; s=default; h=Content-Type:MIME-Version:Message-ID: In-Reply-To:Date:References:Subject:Cc:To:From:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=KSomDctrvlDY5105iwsc3xXNNnjnQD1RZbtDOUxm7KI=; b=aax6+bcflC/4HJegzeJ56k20eX ctxvdOSoSxNSnB7vC6SqAm3Vm1MlBmEXb+2WHoaHrxyfq9UhYFiPmeuDUgUrkxV/drkA8zipRD8UV yubDFLZX2VKSsVeWJvc7GqpcTYDOJyMjUFyavdnnhCQx9DhfuLErxTp6uhvoTyWBCsyPx69fHFNUO n986x4olBmf5eOvediphHYcHDIMBe1iTlNvtJFPbInfpwYpqNrOXQvgNHfQSUVqGaumRCFTvILvVA 7nPJjYkW7lN6yKVwtYn9UjkG1QllqOLr6uYXdRJAvcQ3lhGDH2Wh4T0O6UsSYcISzSLCKqE5J7rxh sTScIIew==; Original-Received: from [76.77.182.20] (port=50567 helo=Takver4) by host2007.hostmonster.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1m9F2R-004HZM-QY; Thu, 29 Jul 2021 17:02:03 -0600 In-Reply-To: <831r7itjc8.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 28 Jul 2021 20:54:31 +0300") X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host2007.hostmonster.com X-AntiAbuse: Original Domain - gnu.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - stephe-leake.org X-BWhitelist: no X-Source-IP: 76.77.182.20 X-Source-L: No X-Exim-ID: 1m9F2R-004HZM-QY X-Source-Sender: (Takver4) [76.77.182.20]:50567 X-Source-Auth: stephen_leake@stephe-leake.org X-Email-Count: 5 X-Source-Cap: c3RlcGhlbGU7c3RlcGhlbGU7aG9zdDIwMDcuaG9zdG1vbnN0ZXIuY29t X-Local-Domain: yes Received-SPF: permerror client-ip=192.185.149.105; envelope-from=stephen_leake@stephe-leake.org; helo=gateway34.websitewelcome.com X-Spam_score_int: -8 X-Spam_score: -0.9 X-Spam_bar: / X-Spam_report: (-0.9 / 5.0 requ) BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_NEUTRAL=0.779 autolearn=no 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:271803 Archived-At: Eli Zaretskii writes: >> From: Yuan Fu >> Date: Wed, 28 Jul 2021 13:47:42 -0400 >> Cc: Stephen Leake , >> cpitclaudel@gmail.com, >> monnier@iro.umontreal.ca, >> emacs-devel@gnu.org >> >> Could you describe the desired effect on tree-sitter when the buffer is narrowed? > > The behavior should be the same as if the text before and after the > narrowed region didn't exist. That would be true for the multi-major-mode use case, but not for the temporarily narrow-to-defun case. In other words, this should be up to the major mode to determine; the low-level code should support either case (there are probably other use cases out there). >> If we just deny accessibility of the hidden region from tree-sitter, >> tree-sitter is still aware of the hidden text, because it has >> previously parsed the hidden text and stored the result in the parse >> tree. > > The adherence to narrowing is for the use cases where TS is _always_ > invoked on the same narrowed region. right; the multi-major-mode case. > You seem to be thinking about changes in the narrowing while TS is > parsing, or between consecutive re-parsing calls, but I see no > interesting/important use cases which would need to do that. And if > there are some tricky cases which do need this, the respective Lisp > programs will have to deal with the problem. Right. -- -- Stephe