GNU bug report logs - #62333
30.0.50; Issue with tree-sitter syntax tree during certain changes

Previous Next

Full log

Message #188 received at 62333 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Gregory Heytings <gregory <at> heytings.org>
Cc: wkirschbaum <at> gmail.com, casouri <at> gmail.com, 62333 <at> debbugs.gnu.org,
 dgutov <at> yandex.ru
Subject: Re: bug#62333: 30.0.50; Issue with tree-sitter syntax tree during
 certain changes
Date: Thu, 30 Mar 2023 20:47:30 +0300

> Date: Thu, 30 Mar 2023 17:27:02 +0000
> From: Gregory Heytings <gregory <at> heytings.org>
> cc: wkirschbaum <at> gmail.com, casouri <at> gmail.com, 62333 <at> debbugs.gnu.org, 
>     dgutov <at> yandex.ru
> 
> > The parsers _can_ have access to those ranges, if they need it for some 
> > reason.  In general, everything in Emacs should honor the current 
> > restriction, unless there's a good reason to ignore it.
> 
> Okay, so in the above example by default the parsers will only have access 
> to 1000-1100 for the first one, and 1100-1200 for the second one until the 
> user removes the restrictions.  Unless they need to widen the buffer for 
> some (good) reason.
> 
> If they do widen, will the parsers get access to [400..1100] and 
> [1100..1500], or to the whole buffer?

The former.

> > The problem with ignoring it is that we can never know which code/user 
> > defined the restriction and for what purpose.  I hope that keeping the 
> > parser's restrictions as part of the parser itself will allow us to 
> > break free of that issue when we have to widen.
> 
> At least it's a possibility that seems worth investigating.

I think so, yes.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.