Re: Tree-sitter api

[Eli Zaretskii]

> From: Yuan Fu <casouri@gmail.com>
> Date: Mon, 13 Sep 2021 17:13:40 -0700
> Cc: Tuấn-Anh Nguyễn <ubolonton@gmail.com>,
>  Theodor Thornhill <theo@thornhill.no>,
>  Clément Pit-Claudel <cpitclaudel@gmail.com>,
>  Emacs developers <emacs-devel@gnu.org>,
>  Stefan Monnier <monnier@iro.umontreal.ca>,
>  stephen_leake@stephe-leake.org
> 
> > A new major mode will extend the function to support its language(s).
> > the extension could be as simple as adding something to a database of
> > known mode-to-language associations in some alist.
> > 
> 
> Just to recap, we were talking about how to represent a tree-sitter language 
> in Emacs and how to figure out the dynamic library name for that language. My 
> plan is to use tree-sitter-<lang> to represent a language, which is usually 
> the project name for that language definition. And we just turn it into 
> libtree-sitter-<lang>.so/dylib/dll to get the name of the dynamic library. I 
> think your idea has evolved into another thing—translating major-mode to the 
> tree-sitter languages it uses could be useful, but how does it help with the 
> original topic (representing language, translate to library name)?

I guess I don't see a problem there?  What is the problem?