Re: Update on tree-sitter structure navigation

[Dmitry Gutov <dgutov@yandex.ru>]

On 08/09/2023 09:40, Eli Zaretskii wrote:
>> From: Yuan Fu<casouri@gmail.com>
>> Date: Thu, 7 Sep 2023 18:04:02 -0700
>> Cc: emacs-devel<emacs-devel@gnu.org>, Danny Freeman<danny@dfreeman.email>,
>>   Theodor Thornhill<theo@thornhill.no>,
>>   Jostein Kjønigsen<jostein@secure.kjonigsen.net>,
>>   Randy Taylor<dev@rjt.dev>, Wilhelm Kirschbaum<wkirschbaum@gmail.com>,
>>   Perry Smith<pedz@easesoftware.com>
>>
>>> I don't have a better idea than basically copying NeoVim and others: to maintain the urls to parser repositories and the ref of the latest known good revision, for the current version of the major mode. That info could be filled in by major modes themselves, e.g. in an autoload block (similarly to how auto-mode-alist is appended to).
>> That’ll probably be ideal for third-party modes. But knowing Eli, I don’t think builtin major modes can do that.
> FTR, I have nothing against this technique, I just said that it will
> need volunteers to assume this non-trivial job for each major mode,
> and therefore I personally don't believe this to be a reliable
> solution in practice.  But if volunteers step forward to do this, I
> don't object.

I don't see a way around it, if the grammars continue to add breaking 
changes.

We already have volunteers: when somebody works on a ts mode (adds a new 
feature or verifies that the current font-lock and indentation work 
fine), might as well put in the last-known-good commit hash. Or update 
it, if needed (e.g. the new feature requires that).

Adding versions ranges if/when proper versions arrive might require more 
foresight, but the alternative seems to be "unsupporting" 
distro-packaged grammars.

What I'm saying is in this case not doing this job well (e.g. updating 
the commit hashes and font-lock/indent rules very rarely) might still be 
better than not doing it at all.