unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Yuan Fu <casouri@gmail.com>
Cc: p.d.oliver@mavit.org.uk, emacs-devel@gnu.org
Subject: Re: Versioned Tree-sitter parser libraries
Date: Mon, 24 Apr 2023 14:05:50 +0300	[thread overview]
Message-ID: <83o7ndy1yp.fsf@gnu.org> (raw)
In-Reply-To: <FB1D3E68-3653-41CA-AD3A-0CE3A3E6DEDA@gmail.com> (message from Yuan Fu on Mon, 24 Apr 2023 00:00:20 -0700)

> From: Yuan Fu <casouri@gmail.com>
> Date: Mon, 24 Apr 2023 00:00:20 -0700
> Cc: Eli Zaretskii <eliz@gnu.org>,
>  emacs-devel@gnu.org
> 
> > On Apr 17, 2023, at 1:17 PM, Peter Oliver <p.d.oliver@mavit.org.uk> wrote:
> > 
> > On Mon, 17 Apr 2023, Yuan Fu wrote:
> > 
> >> I was suggesting that we do recognize ABI versions, but since tree-sitter grammars don’t really have a ABI version, and the version extension in filenames are just there by convention (of Fedora), we can expect the version extension to be always 0.0, should there be one.
> > 
> > It’s the Tree-sitter project that have chosen the numbers in their Makefiles, not Fedora, by the way.  https://github.com/tree-sitter/tree-sitter-json/blob/master/Makefile#L42
> > 
> > -- 
> > Peter Oliver
> 
> Now Emacs should recognize .0 and .0.0 suffixes. I pushed the change to emacs-29.

You did?  Because I don't see it when I update from Git.



  reply	other threads:[~2023-04-24 11:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-16 14:20 Versioned Tree-sitter parser libraries Peter Oliver
2023-04-16 14:49 ` Eli Zaretskii
2023-04-17  3:03   ` Yuan Fu
2023-04-17 17:03     ` Eli Zaretskii
2023-04-17 18:41       ` Yuan Fu
2023-04-17 18:49         ` Eli Zaretskii
2023-04-17 20:17         ` Peter Oliver
2023-04-24  7:00           ` Yuan Fu
2023-04-24 11:05             ` Eli Zaretskii [this message]
2023-04-24 17:39               ` Yuan Fu
2023-04-24 18:47                 ` Eli Zaretskii

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=83o7ndy1yp.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=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).