From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>
Cc: casouri@gmail.com, theo@thornhill.no, 61369@debbugs.gnu.org
Subject: bug#61369: Problem with keeping tree-sitter parse tree up-to-date
Date: Sat, 18 Feb 2023 19:21:40 +0200 [thread overview]
Message-ID: <2e141270-ab5c-8987-6c40-c2665a4e7ca2@yandex.ru> (raw)
In-Reply-To: <83sff3zbo3.fsf@gnu.org>
On 18/02/2023 09:15, Eli Zaretskii wrote:
>> Cc: Theodor Thornhill<theo@thornhill.no>,61369@debbugs.gnu.org
>> Date: Sat, 18 Feb 2023 02:11:22 +0200
>> From: Dmitry Gutov<dgutov@yandex.ru>
>>
>> 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.
prev parent reply other threads:[~2023-02-18 17:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 15:34 bug#61369: Problem with keeping tree-sitter parse tree up-to-date Dmitry Gutov
2023-02-08 18:20 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-08 19:41 ` Dmitry Gutov
2023-02-10 1:22 ` Yuan Fu
2023-02-10 1:38 ` Dmitry Gutov
2023-02-13 9:10 ` Yuan Fu
2023-02-13 23:59 ` Yuan Fu
2023-02-15 2:17 ` Dmitry Gutov
2023-02-15 22:44 ` Dmitry Gutov
2023-02-17 22:32 ` Yuan Fu
2023-02-18 0:11 ` Dmitry Gutov
2023-02-18 1:14 ` Yuan Fu
2023-02-18 1:25 ` Dmitry Gutov
2023-02-18 10:05 ` Yuan Fu
2023-02-18 7:15 ` Eli Zaretskii
2023-02-18 17:21 ` Dmitry Gutov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2e141270-ab5c-8987-6c40-c2665a4e7ca2@yandex.ru \
--to=dgutov@yandex.ru \
--cc=61369@debbugs.gnu.org \
--cc=casouri@gmail.com \
--cc=eliz@gnu.org \
--cc=theo@thornhill.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).