From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Dmitry Gutov Newsgroups: gmane.emacs.bugs Subject: bug#61369: Problem with keeping tree-sitter parse tree up-to-date Date: Sat, 18 Feb 2023 19:21:40 +0200 Message-ID: <2e141270-ab5c-8987-6c40-c2665a4e7ca2@yandex.ru> References: <1AC63591-F4EF-411F-B554-7CD38B4B4888@gmail.com> <9c4e551b-42b3-8202-ccff-fb8170b616a6@yandex.ru> <7751EE35-F5FF-418B-AF28-F1FF5ECEF3AE@gmail.com> <52d15d7e-82e9-ca7b-be16-0ccf89d5053c@yandex.ru> <83sff3zbo3.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="10992"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 Cc: casouri@gmail.com, theo@thornhill.no, 61369@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Feb 18 18:22:24 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 1pTQul-0002gP-VQ for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 18 Feb 2023 18:22:23 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pTQuU-0000dJ-E1; Sat, 18 Feb 2023 12:22:06 -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 1pTQuQ-0000cr-I7 for bug-gnu-emacs@gnu.org; Sat, 18 Feb 2023 12:22:02 -0500 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 1pTQuQ-0001N0-9d for bug-gnu-emacs@gnu.org; Sat, 18 Feb 2023 12:22:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pTQuP-0004Wl-Ri for bug-gnu-emacs@gnu.org; Sat, 18 Feb 2023 12:22:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Dmitry Gutov Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 18 Feb 2023 17:22:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 61369 X-GNU-PR-Package: emacs Original-Received: via spool by 61369-submit@debbugs.gnu.org id=B61369.167674091117385 (code B ref 61369); Sat, 18 Feb 2023 17:22:01 +0000 Original-Received: (at 61369) by debbugs.gnu.org; 18 Feb 2023 17:21:51 +0000 Original-Received: from localhost ([127.0.0.1]:44856 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pTQuE-0004WK-KN for submit@debbugs.gnu.org; Sat, 18 Feb 2023 12:21:50 -0500 Original-Received: from mail-wm1-f53.google.com ([209.85.128.53]:43760) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pTQuC-0004W7-SK for 61369@debbugs.gnu.org; Sat, 18 Feb 2023 12:21:49 -0500 Original-Received: by mail-wm1-f53.google.com with SMTP id bg25-20020a05600c3c9900b003e21af96703so452607wmb.2 for <61369@debbugs.gnu.org>; Sat, 18 Feb 2023 09:21:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :sender:from:to:cc:subject:date:message-id:reply-to; bh=eDAInN9U2Ef70rBBbpNPIqtm1q9W4EpICvSnUEIEzI4=; b=MYXROo3C15KV+Ygkmsk2Js8c/3I+t/LFo8c89Ysv/BJhPSTmJ4zXv88r+bkk8TqT9j yxYOmV5SWCdEOBi9YjBFGhyuc178Qru/5Dpa1cXiPLGclfLzoN/FncWy2sEJuv3f1As/ B2GByqms3P8538PF/do9gfgUrCMBVAUXu4cqxAZ5ezKGc3mw4mlZHxIdcaNXOYJOwq+e WSHAU9TyU3YNSBF228FM70gLgY+gZitXvDPOIsaSXpNPIl9KeiXHGMRGZAwmyvGCVInf VRQKoY8w8he3EFmrtBTI8txcJI+jT23xKFRhqg7VMOWmUXYxTNyc2W8emHY84Igw8Key O0uQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :sender:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=eDAInN9U2Ef70rBBbpNPIqtm1q9W4EpICvSnUEIEzI4=; b=CpfUCyVSItQ0ZIHqcO/CGIlQ2AHLB5JjiEJiL87rFX6eB/08ebtSoQP34ViVr0n00F tIGmB4mpFWz8AMWkyaaiaO5ZT5dSyRF3VBwCoiiS3B76DqUriwDpXYwNFyeOuCNZNToj 8U2LTwmmv1hyLmKUP6eUM6jV5oA6ZpCer9CFnDhyVAR43FZjmUTzJitTO8akH8SEtDHk N8Mj9PmhIVvwPEs38VMtvXd3Yt5Pn5xd4Qz84Tf0vj0f3OJQZXrPZm7pk5101NMxAkTe gp1kLF/cGl17DSwHmgKsOb2L7Plv7dXsye4Vc0Wvz1yCreacxWSiRgcZHyxEY+ggCOwa /jOQ== X-Gm-Message-State: AO0yUKWZhFdWJ2bBbHIqdJiLjxLu5PUThj7ZSwRS91UFO8wbV9p7KctD gK5MgbB4GrVrVVH0CgUQr0M= X-Google-Smtp-Source: AK7set8mEH82akD+apwaF6XafnPISPbgeVrypedjLlR/O/HZpVE7HAEv9CpI+uUCKE4XXqEdp59Dcw== X-Received: by 2002:a05:600c:755:b0:3e2:1fe9:8d1b with SMTP id j21-20020a05600c075500b003e21fe98d1bmr4916363wmn.6.1676740902835; Sat, 18 Feb 2023 09:21:42 -0800 (PST) Original-Received: from [192.168.0.2] ([46.251.119.176]) by smtp.googlemail.com with ESMTPSA id b4-20020a05600c4e0400b003d1d5a83b2esm5270594wmq.35.2023.02.18.09.21.41 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 18 Feb 2023 09:21:42 -0800 (PST) Content-Language: en-US In-Reply-To: <83sff3zbo3.fsf@gnu.org> 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:255980 Archived-At: On 18/02/2023 09:15, Eli Zaretskii wrote: >> Cc: Theodor Thornhill,61369@debbugs.gnu.org >> Date: Sat, 18 Feb 2023 02:11:22 +0200 >> From: Dmitry Gutov >> >> I'm not sure whether there is an actual hard limit on modifying the >> text outside of the current restriction. > It is, for most/all practical purposes. If you try to modify text > outside of the current restriction, you risk many parts of code > barfing or signaling errors on you. For example, conversion from > character to byte positions and vice versa will stop working (and in a > build with --enable-checking will actually raise SIGABRT). All right, thank you both.