[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Tree-sitter introduction documentation

From: Eli Zaretskii
Subject: Re: Tree-sitter introduction documentation
Date: Tue, 27 Dec 2022 14:11:29 +0200

> Date: Tue, 27 Dec 2022 00:42:55 +0200
> Cc: emacs-devel@gnu.org
> From: Dmitry Gutov <dgutov@yandex.ru>
> On 17/12/2022 17:42, Stefan Monnier wrote:
> > Those grammars have been in use for a while now
> > (by other editors), AFAIK, so why would the situation change just because
> > Emacs starts to use them as well?
> I guess "other editors" that use tree-sitter do bundle the grammars?
> Or include them in the optional language packages. Or provide built-in 
> recipes to install them.

WDYT about what we have in NEWS about this?

> E.g. nvim-treesitter seems to be doing the latter: 
> https://github.com/nvim-treesitter/nvim-treesitter#language-parsers
> The corresponding recipes look like:
> list.ruby = {
>    install_info = {
>      url = "https://github.com/tree-sitter/tree-sitter-ruby";,
>      files = { "src/parser.c", "src/scanner.cc" },
>    },
>    maintainers = { "@TravonteD" },
> }

It sounds like a non-trivial maintenance burden to keep this kind of
DB up-to-date.  So I'm not sure we should do this in the upstream

But if Someone(TM) wants to provide Emacs commands to download,
compile, and install a grammar library, I see no reason not to add
that to Emacs.  This could be part of treesit.el, for example.

One condition, though: please implement the commands in Emacs Lisp,
without invoking any shell scripting features (which shouldn't be
needed to begin with), just by using compiler, Emacs commands and
functions that deal with files, and (possibly) Git.

Also, if we provide some list of grammar libraries we support
officially and their respective sites, that list should include only
libraries with a Free license.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]