Predicates/directives are documented to end in either `!` or `?`. However, `query.c` allows them to be any valid identifier, and also allows `?` or `!` characters anywhere inside an identifier. This commit removes `?` and `!` from the list of valid identifier characters, and asserts that predicates/directives only *end* in `?` or `!`, respectively. This commit is breaking because you can no longer do something like `(#eq? @capture foo!bar)` (`foo!bar` must now be quoted). |
||
|---|---|---|
| .. | ||
| benches | ||
| config | ||
| eslint | ||
| generate | ||
| loader | ||
| npm | ||
| src | ||
| build.rs | ||
| Cargo.toml | ||
| README.md | ||
Tree-sitter CLI
The Tree-sitter CLI allows you to develop, test, and use Tree-sitter grammars from the command line. It works on MacOS, Linux, and Windows.
Installation
You can install the tree-sitter-cli with cargo:
cargo install --locked tree-sitter-cli
or with npm:
npm install tree-sitter-cli
You can also download a pre-built binary for your platform from the releases page.
Dependencies
The tree-sitter binary itself has no dependencies, but specific commands have dependencies that must be present at runtime:
- To generate a parser from a grammar, you must have
nodeon your PATH. - To run and test parsers, you must have a C and C++ compiler on your system.
Commands
-
generate- Thetree-sitter generatecommand will generate a Tree-sitter parser based on the grammar in the current working directory. See the documentation for more information. -
test- Thetree-sitter testcommand will run the unit tests for the Tree-sitter parser in the current working directory. See the documentation for more information. -
parse- Thetree-sitter parsecommand will parse a file (or list of files) using Tree-sitter parsers.