Local compilation of abritrary TS grammars

[ethan-leba]

I wanted to get the ball rolling on abritrary grammar installation, so here's my attempt at it. Let me know if this fits in with your goals for TS langs, and what we can change if not!

This PR adds the following:

• Splits the compilation logic in tree-sitter-langs-compile from the submodule handling.
• Allows abritary directories to be specified in tree-sitter-langs-ensure.

This will allow users to be able to use grammars that aren't in TS langs, or compile versions that are more recent than what is in TS langs.

A next step I'd like to see is automatic installation from a git repo instead of cloning manually, but out of scope of this PR.

[ethan-leba]

Hi @ubolonton, is there anything I can do to help get this PR through code review?

[siraben]

Can you give an example of how a user would use this? Suppose I had the grammars compiled in ~/.tree-sitter/bin, how can I get tree-sitter langs to use those more recent ones?

[ethan-leba]

Can you give an example of how a user would use this?

Sure, I have a snippet like this in my config:

(tree-sitter-langs-ensure 'my-python "~/tree-sitter-python")
(push '(python-mode . my-python) tree-sitter-major-mode-language-alist)

Suppose I had the grammars compiled in ~/.tree-sitter/bin, how can I get tree-sitter langs to use those more recent ones?

If you already have a grammar with the same symbol name, then ensure won't override it -- so you'd have to manually delete the old grammar from your grammar-dir, or give the grammar a different symbol name. It would be great if ensure could detect if the provided grammar is newer and overwrite, but that would be for a future PR. (Not sure exactly if that was what you were asking?)

[siraben]

Do I have to do tree-sitter-langs-ensure for every language in my grammar-dir?

[ethan-leba]

The purpose of this PR is to allow grammars to be installed outside of the prepackaged repositories that come with TSL -- the functionality for interacting with those prepackaged grammars is completely unchanged. For custom grammars, you'd need to provide a path of course

[ethan-leba]

Closing this as it will need to be reworked if/when emacs-tree-sitter/elisp-tree-sitter#220 is merged