[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Validating tree-sitter major modes and grammar
From: |
Yuan Fu |
Subject: |
Re: Validating tree-sitter major modes and grammar |
Date: |
Sat, 4 Jan 2025 00:31:08 -0800 |
> On Jan 3, 2025, at 4:26 AM, Peter Oliver <p.d.oliver@mavit.org.uk> wrote:
>
> On Thu, 2 Jan 2025, Peter Oliver wrote:
>
>> On Mon, 30 Dec 2024, Yuan Fu wrote:
>>
>>> Anyway, as a first step, I added a command that generates a html file that
>>> looks like the below. I’ll try setting up a cron job on my machine, then
>>> we can figure out how do we run it on EMBA and how to host the generated
>>> webpage.
>>>
>>> Peter, do you have any suggestions after seeing this example webpage?
>>
>> Looks good.
>>
>> Rather than the latest commit, I’d be more interested in the latest release
>> (i.e., commit tagged with a tag starting “v”). I’d only consider packaging
>> a Git snapshot as a last resort to solve an important bug, so tagged commits
>> are more relevant to me.
>
> So, then, something along the lines of the attached (although, actually,
> maybe we want both?).
>
> --
> Peter
> Oliver<0001-New-function-treesit-language-git-version-tags.patch><0002-Tweak-Tree-sitter-compatibility-report-to-show-only-.patch>
Thanks! What you showed looks good. And yeah, we should have both “last tag”
and “last commit”. “Last commit” would be useful for people that install
tree-sitter grammars with download scripts.
Let me see how can I construct the table to show both.
Yuan