>
> Does that make sense?

Not really, no.
You might want to be more precise about what you mean by "parser" and
explain what's the difference between the "generic parser" and more
specific ones.

By "specific parser" are you referring to something that I might call
"compiled grammars"?

Yeah.

The way I understand it, to use TS for a given language, you need:
- The TS runtime (which should be included in Emacs if you use the
corresponding feature branch and which include what I'd called "the
incremental parser").
- The language's grammar. This is usually a .js file and is compiled to
an .so file by the tree sitter tools. This is *not* included in the
feature branch (neither the grammars nor the tools).
- The glue in the major mode code.

Yes, and the tree-sitter-module repo provides a way to compile these grammar.js files into an object emacs understands. Some functionality to do this can be implemented in emacs, but isn't yet. This is the missing piece, apart from implementing the modes such as the provided js mode patch I made earlier today.

Should this compilation process be integrated in the feature branch?

Theo