From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#62333: 30.0.50; Issue with tree-sitter syntax tree during certain changes Date: Wed, 29 Mar 2023 14:08:31 +0300 Message-ID: <83lejf7r2o.fsf@gnu.org> References: <87fs9yur7r.fsf@gmail.com> <83sfduelab.fsf@gnu.org> <8FC25A01-6934-43BB-899C-CA5926BEA3CF@gmail.com> <83jzz5c8ml.fsf@gnu.org> <83edpdc6sn.fsf@gnu.org> <1ca302bf-99dc-7f9e-8544-063064a1cb21@yandex.ru> <831qlcdisi.fsf@gnu.org> <398721ad-79b0-3f6d-97b3-4902d9bfbe39@yandex.ru> <83wn34c2qa.fsf@gnu.org> <3b3d82d1-f0f6-a768-a5db-8dc9386a5a34@yandex.ru> <83r0tcbz8g.fsf@gnu.org> <1967361679760225@umbzx4hqxrw5qxo7.sas.yp-c.yandex.net> <83mt40bxzd.fsf@gnu.org> <83jzz4bugh.fsf@gnu.org> <3d64520c-54da-a04a-ed0d-a66b4e753f8a@yandex.ru> <831qlcaysh.fsf@gnu.org> <29679184-7366-0167-9e94-def97048f663@yandex.ru> <83v8inal29.fsf@gnu.org> <9886ffa5-ead2-50d5-a325-f6704b736ada@yandex.ru> <728618716b8c5349d27e@heytings.org> <83bkke9uue.fsf@gnu.org> <83ilel861g.fsf@gnu.org> <290987e0-821e-a231-c1c4-b40bb9542ffe@yandex.ru> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="4031"; mail-complaints-to="usenet@ciao.gmane.io" Cc: wkirschbaum@gmail.com, gregory@heytings.org, casouri@gmail.com, 62333@debbugs.gnu.org To: Dmitry Gutov Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Mar 29 13:09:14 2023 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1phTg2-0000u8-HW for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 29 Mar 2023 13:09:14 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1phTfr-0003Cw-JT; Wed, 29 Mar 2023 07:09:03 -0400 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 1phTfq-0003Co-KH for bug-gnu-emacs@gnu.org; Wed, 29 Mar 2023 07:09:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1phTfq-00015N-CM for bug-gnu-emacs@gnu.org; Wed, 29 Mar 2023 07:09:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1phTfq-0008IR-5J for bug-gnu-emacs@gnu.org; Wed, 29 Mar 2023 07:09:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 29 Mar 2023 11:09:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 62333 X-GNU-PR-Package: emacs Original-Received: via spool by 62333-submit@debbugs.gnu.org id=B62333.168008811631859 (code B ref 62333); Wed, 29 Mar 2023 11:09:02 +0000 Original-Received: (at 62333) by debbugs.gnu.org; 29 Mar 2023 11:08:36 +0000 Original-Received: from localhost ([127.0.0.1]:51391 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1phTfQ-0008Hl-72 for submit@debbugs.gnu.org; Wed, 29 Mar 2023 07:08:36 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:48700) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1phTfN-0008HY-KM for 62333@debbugs.gnu.org; Wed, 29 Mar 2023 07:08:34 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1phTfH-00014E-O7; Wed, 29 Mar 2023 07:08:27 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=OfSZu0hJ+CwSWb81rvyab+4TjL/KpToE9WJIhJeyUpA=; b=onc9TnXBrc+r Ivw2aaOf97PIMmuFNUKDFmggxhnaVSG6ND8sjIMlHuYpS7sJJFfjf8FqX4Zn/oC71F6xzNhbpOx9+ 2j2WeKRW1tBi6dHeoqD4/p8OedvhlcLU68R04qAlEfdamTYQF6HOkPo4N14IWk+inIfHpj1roGhYA fajU86CJQ219qMuXHTZQKeLXKhDRdvaYEOqyzUCXqQMhOvvx2/nuiwYbPk6AvUQewUF8iN8smoxmF Kt1cWiKlGEB/gyv+v4V4jIlHsTc9sHL1aBq2kqLycB/lcdLpXEZpaUx/V6R1xaYouwjx71QwKNpVu XlEXirFGp9nQVtsADGVkfQ==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1phTfD-0004SV-KO; Wed, 29 Mar 2023 07:08:27 -0400 In-Reply-To: <290987e0-821e-a231-c1c4-b40bb9542ffe@yandex.ru> (message from Dmitry Gutov on Wed, 29 Mar 2023 00:08:53 +0300) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:258839 Archived-At: > Date: Wed, 29 Mar 2023 00:08:53 +0300 > Cc: wkirschbaum@gmail.com, gregory@heytings.org, casouri@gmail.com, > 62333@debbugs.gnu.org > From: Dmitry Gutov > > >> Is that because we don't think the user level narrowing is done purely > >> for visual effect? > > > > Indeed, it isn't always for visual effect. > > When isn't it? Is there a way to determine that from code? I'm not sure I understand the question, but if I do, then narrowing to prevent search functions and commands from finding irrelevant hits is one example that comes to mind. > >> judging by regular user requests for make this or that command > >> ignore user-level narrowing, it seems like "purely visual" should be the > >> default interpretation. > > > > I think you base your judgment on feedback from users who are not used > > to take advantage of narrowing in editing. I think most young people > > aren't, since this feature is more-or-less unique to Emacs. > > Either narrowing should be used to change lexical/grammatical/etc > context, or it should not. Do we have any documentation that says one or > the other way? That should affect how Lisp code deals with narrowing -- > which interactive functions should widen, and so on. I was talking about user commands that narrow, so I'm not sure I understand how documentation could help. When the user types "C-x n n", there's nothing Emacs can do except obey.