Re: Tree-sitter api

[Yuan Fu]

>> 
>>> What I had in mind is a function that give the major-mode symbol will
>>> return the name of the corresponding TS language module (or a list of
>>> modules, if there's more than one).
>> 
>> My problem with such a function is that Emacs can’t possibly cover all the 
>> major-modes and tree-sitter languages. What if there is a new language, and 
>> someone wrote a tree-sitter language definition for it, and then want to 
>> write an Emacs major mode using tree-sitter features?
> 
> 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)?

Yuan