Re: Tree-sitter api

[Yuan Fu]

>> 
>> 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?

I thought you proposed the major mode thing to replace the naming scheme, 
because we were talking about naming languages and translating language names 
to library names when you proposed it. So you agree to to the initial plan to 
translate tree-sitter-<lang> to libtree-sitter-<lang>.so/etc, and to use an 
override alist for irregular names?

Yuan