From: "Björn Bidar" <bjorn.bidar@thaodan.de>
To: Yuan Fu <casouri@gmail.com>
Cc: Emacs Devel <emacs-devel@gnu.org>,
Peter Oliver <p.d.oliver@mavit.org.uk>,
Stefan Kangas <stefankangas@gmail.com>
Subject: Re: Validating tree-sitter major modes and grammar
Date: Tue, 24 Dec 2024 23:36:41 +0200 [thread overview]
Message-ID: <43961.52905408$1735076247@news.gmane.org> (raw)
In-Reply-To: <8DF80F0D-E50A-4162-93E6-F7F55B2E7144@gmail.com> (Yuan Fu's message of "Mon, 23 Dec 2024 19:20:06 -0800")
Yuan Fu <casouri@gmail.com> writes:
>> On Dec 22, 2024, at 4:44 PM, Björn Bidar <bjorn.bidar@thaodan.de> wrote:
>>
>> Yuan Fu <casouri@gmail.com> writes:
>>
>>> Continuing from the tree-sitter maternity thread, I cooked up some
>>> script to go over each builtin tree-sitter mode, clone the grammars it
>>> uses, and check whether the font-lock queries are compatible with the
>>> latest version of the grammar. If everything works fine, the script
>>> adds some comment in the source file listing the version that was
>>> checked.
>>
>> Oh that sounds very good. This could be a good workaround for the sort
>> of fast and lose nature of tree-sitter.
>>
>
> Great. Do you think the “verified version” comment will be helpful for packagers?
>
It would be helpful in case something goes wrong as a kind of sanity
check but it won't help much for an indicator when to update since I
don't think that would be blocker for updating.
It is helpful but none the less the goal should be that such errors
should be preventable between grammar versions.
prev parent reply other threads:[~2024-12-24 21:36 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 9:09 Validating tree-sitter major modes and grammar Yuan Fu
2024-12-20 12:24 ` Eli Zaretskii
2024-12-20 16:22 ` Yuan Fu
2024-12-23 0:44 ` Björn Bidar
[not found] ` <868qs6vd76.fsf@aarsen.me>
2024-12-24 1:16 ` Yuan Fu
2024-12-24 3:12 ` Yuan Fu
2024-12-24 12:19 ` Eli Zaretskii
2024-12-24 21:30 ` Yuan Fu
2024-12-24 23:09 ` Dmitry Gutov
2024-12-25 8:39 ` Yuan Fu
2024-12-26 2:23 ` Dmitry Gutov
2025-01-02 3:30 ` Yuan Fu
[not found] ` <6768b29d.050a0220.1b40f2.5574SMTPIN_ADDED_BROKEN@mx.google.com>
2024-12-24 3:20 ` Yuan Fu
2024-12-24 12:36 ` Peter Oliver
2024-12-24 14:20 ` Michael Albinus
2024-12-24 22:20 ` Yuan Fu
2024-12-25 8:20 ` Michael Albinus
2024-12-25 9:33 ` Yuan Fu
2024-12-25 13:51 ` Michael Albinus
2024-12-26 12:54 ` Peter Oliver
2024-12-26 17:50 ` Michael Albinus
2024-12-28 12:02 ` Michael Albinus
2024-12-30 8:08 ` Yuan Fu
2025-01-02 16:48 ` Peter Oliver
2025-01-03 12:26 ` Peter Oliver
2025-01-04 8:31 ` Yuan Fu
2024-12-24 22:14 ` Yuan Fu
2024-12-24 21:36 ` Björn Bidar [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='43961.52905408$1735076247@news.gmane.org' \
--to=bjorn.bidar@thaodan.de \
--cc=casouri@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=p.d.oliver@mavit.org.uk \
--cc=stefankangas@gmail.com \
/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).