unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ergus <spacibba@aol.com>
To: emacs-devel@gnu.org
Subject: New tree sitter "official" langs
Date: Tue, 23 Jul 2024 16:41:28 +0200	[thread overview]
Message-ID: <ek4c5ehmvi5ljrlesp4d4allcmtxuwo5wohqdaaiaxbpeeeec5@lafpkc45wyhm> (raw)
In-Reply-To: ek4c5ehmvi5ljrlesp4d4allcmtxuwo5wohqdaaiaxbpeeeec5.ref@lafpkc45wyhm

Hi:

Recently I have found that some of the grammar source repositories
we use in:

https://github.com/casouri/tree-sitter-module

are out of date (2 or 3 years with no updates, fixes or replies to
issues).

Some of those repositories are somehow "Legacy" because they are
superseded by a new "official" repository:

https://github.com/tree-sitter-grammars

This seems to be a meta-repo including support for many langs including
some that are supported by emacs.

I opened this issue:

https://github.com/casouri/tree-sitter-module/issues/53

Where I added a table of the modules that could be desirable to update
to the `tree-sitter-grammars' source. Most of them can (and apparently
should) be updated immediately with no issue.

The only two exceptions are markdown and scss, where we use two grammars
that seems unmaintained. So I may ask the *-ts-mode developers to
consider to update to the new grammars versions if there is some
incompatibility.

Specially the markdown one seems to be more feature rich and include
inline markdown as well. https://github.com/tree-sitter-grammars/tree-sitter-markdown

The scss looks like maybe in the past it was forked from the one we use,
not sure of this.

In any case, none of those two have been updated in 3 years and the new
version received updates only two months ago.

Best,
Ergus



       reply	other threads:[~2024-07-23 14:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ek4c5ehmvi5ljrlesp4d4allcmtxuwo5wohqdaaiaxbpeeeec5.ref@lafpkc45wyhm>
2024-07-23 14:41 ` Ergus [this message]
2024-07-23 21:40   ` New tree sitter "official" langs 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=ek4c5ehmvi5ljrlesp4d4allcmtxuwo5wohqdaaiaxbpeeeec5@lafpkc45wyhm \
    --to=spacibba@aol.com \
    --cc=emacs-devel@gnu.org \
    /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).