From: Yuan Fu <casouri@gmail.com>
To: Peter Oliver <p.d.oliver@mavit.org.uk>
Cc: Emacs Devel <emacs-devel@gnu.org>
Subject: Re: Validating tree-sitter major modes and grammar
Date: Sat, 4 Jan 2025 00:31:08 -0800 [thread overview]
Message-ID: <BF8AAD24-2001-4C56-BB63-96E328CD011B@gmail.com> (raw)
In-Reply-To: <e005cffe-c3e7-3f07-5351-bb87124f2545@mavit.org.uk>
> 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
next prev parent reply other threads:[~2025-01-04 8:31 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 [this message]
2024-12-24 22:14 ` Yuan Fu
2024-12-24 21:36 ` Björn Bidar
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=BF8AAD24-2001-4C56-BB63-96E328CD011B@gmail.com \
--to=casouri@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=p.d.oliver@mavit.org.uk \
/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).