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: Sun, 25 Jul 2021 11:21:27 -0700 Message-ID: <86pmv66yqg.fsf@stephe-leake.org> References: <83h7gw6pyj.fsf@gnu.org> <83y2a764oy.fsf@gnu.org> <83v95b60fn.fsf@gnu.org> <00DD5BFE-D14E-449A-9319-E7B725DEBFB3@gmail.com> <83r1fz5xr9.fsf@gnu.org> <1AAB1BCC-362B-4249-B785-4E0530E15C60@gmail.com> <83czri67h0.fsf@gnu.org> <46BBFF88-76C3-4818-8805-5437409BEA93@gmail.com> <83wnpq46uk.fsf@gnu.org> <533BD53B-4E85-4E9E-B46A-346A5BBAD0F5@gmail.com> <258CB68D-1CC1-42C8-BDCD-2A8A8099B783@gmail.com> <1a776770-50b7-93cd-6591-c9a5b3a56eb8@gmail.com> <8335s64v10.fsf@gnu.org> <5380C92B-6C15-4490-A1E0-1C3132DBB16A@gmail.com> <83k0li2shw.fsf@gnu.org> <86wnpg82v3.fsf@stephe-leake.org> <83lf5wyn0z.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="18273"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (windows-nt) Cc: casouri@gmail.com, 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 Sun Jul 25 20:22:09 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 1m7ilM-0004X7-PT for ged-emacs-devel@m.gmane-mx.org; Sun, 25 Jul 2021 20:22:09 +0200 Original-Received: from localhost ([::1]:40596 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1m7ilL-0003G4-Oi for ged-emacs-devel@m.gmane-mx.org; Sun, 25 Jul 2021 14:22:07 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:38862) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1m7ikn-0002L4-JT for emacs-devel@gnu.org; Sun, 25 Jul 2021 14:21:33 -0400 Original-Received: from gateway22.websitewelcome.com ([192.185.46.156]:22792) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1m7ikl-0005vS-5k for emacs-devel@gnu.org; Sun, 25 Jul 2021 14:21:33 -0400 Original-Received: from cm11.websitewelcome.com (cm11.websitewelcome.com [100.42.49.5]) by gateway22.websitewelcome.com (Postfix) with ESMTP id B776612B8 for ; Sun, 25 Jul 2021 13:21:29 -0500 (CDT) Original-Received: from host2007.hostmonster.com ([67.20.76.71]) by cmsmtp with SMTP id 7ikjm9DSXK61i7ikjmNkt0; Sun, 25 Jul 2021 13:21:29 -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=xsnuQH72hntxpx9MaadfmRWDGHJwlmvh5aZEb9kDH3M=; b=XChcben6OvlN3+0HtVVwVgePxk oIZXlOruSjHjdDewhXZ18+Gy6cGMJBkg3TiVXCyB3FicfT3d2+6ujTpT7Rao5OcmrTY72/r5Ap97J kbQ2OujoEc5V4ZrjKlz2RBOnzdaAh9ZT5yyHSyqs6DqNL+eV+Whv+eZoERjr2SBLW/m9JPjVDkjE9 AWXKXaaAobmTxyneoW+2+//R1dLv81u8fFUOqaA8LK0irwk3GRorZ4SALneJdq+gsu9X8Dm0A21jU K0itbTpuQDxqrOK2Okxo52KeEuf9gfd7g+O+BraNzR3Y4RXHiqNNsN1+yp1e+6CIpBEpQ/VU+uXLY zMTvqHkg==; Original-Received: from [76.77.182.20] (port=57316 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 1m7ikj-001Fsm-0m; Sun, 25 Jul 2021 12:21:29 -0600 In-Reply-To: <83lf5wyn0z.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 24 Jul 2021 14:22:20 +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: 1m7ikj-001Fsm-0m X-Source-Sender: (Takver4) [76.77.182.20]:57316 X-Source-Auth: stephen_leake@stephe-leake.org X-Email-Count: 10 X-Source-Cap: c3RlcGhlbGU7c3RlcGhlbGU7aG9zdDIwMDcuaG9zdG1vbnN0ZXIuY29t X-Local-Domain: yes Received-SPF: permerror client-ip=192.185.46.156; envelope-from=stephen_leake@stephe-leake.org; helo=gateway22.websitewelcome.com X-Spam_score_int: 10 X-Spam_score: 1.0 X-Spam_bar: + X-Spam_report: (1.0 / 5.0 requ) DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, 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:271620 Archived-At: Eli Zaretskii writes: >> From: Stephen Leake >> Cc: Yuan Fu , cpitclaudel@gmail.com, >> monnier@iro.umontreal.ca, emacs-devel@gnu.org >> Date: Sat, 24 Jul 2021 02:42:24 -0700 >> >> > But that's how the current font-lock and indentation work: they never >> > look beyond the narrowing limits. >> >> And that's broken > > ??? Of course, it isn't: it's how Emacs has worked since v21.1. Ada (and other languages, but not all) requires the full file text to properly compute font and indent; narrowing breaks that. The fix for font-lock is font-lock-dont-widen; I implemented a similar mechanism for indent of an ada-mode region in multi-major-mode. In plain ada-mode, indent is currently broken in a narrowed buffer; wisi-indent-region does not widen because it is language-agnostic, and I have not gotten around to implementing a "widen for indent" hook because I don't use narrowing very often, and no one has complained. >> unless the narrowing is for multi-major-mode. > > And what would you do in that case, if you allow TS to look beyond the > restriction? In the multi-major-mode case, there is a separate parser for each language, and each sub-mode region in the text would get its own parser tree (ie, it acts like a separate file), and that parser tree is only told about changes to those regions. So the parser will never try to look outside the region; it doesn't need to know about narrowing. I'll have to upgrade my Ada multi-major-mode implementation to do this for incremental parse. -- -- Stephe