traxys/tree-sitter
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: small fixes

Browse source 
Co-authored-by: Wang <bonede@qq.com>
Co-authored-by: Sebastiaan Speck <12570668+sebastiaanspeck@users.noreply.github.com>
This commit is contained in:
dundargoc 2024-02-10 16:41:47 +01:00 • committed by dundargoc
parent 6895b7a1e1
commit bf9154febe
4 changed files with 5 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

1
docs/index.md
View file

@ -20,6 +20,7 @@ There are currently bindings that allow Tree-sitter to be used from the followin
* [Guile](https://github.com/Z572/guile-ts)
* [Haskell](https://github.com/tree-sitter/haskell-tree-sitter)
* [Java](https://github.com/serenadeai/java-tree-sitter)
* [Java](https://github.com/bonede/tree-sitter-ng)
* [Java (Android)](https://github.com/AndroidIDEOfficial/android-tree-sitter)
* [JavaScript (Node.js)](https://github.com/tree-sitter/node-tree-sitter)
* [JavaScript (Wasm)](https://github.com/tree-sitter/tree-sitter/tree/master/lib/binding_web)

2
docs/section-2-using-parsers.md
View file

@ -661,7 +661,7 @@ Consider the following example targeting C:
(#eq? @variable.builtin "self"))
```
This pattern would match any identifier that is `self` or `this`.
This pattern would match any identifier that is `self`.
And this pattern would match key-value pairs where the `value` is an identifier
with the same name as the key:

4
docs/section-7-playground.html
View file

@ -54,12 +54,12 @@ permalink: playground
<h4 id="about">About </h4>
<p>You can try out tree-sitter with a few pre-selected grammars on this page.
You can also run playground locally (with your own grammar) using the
<a href="/creating-parsers">CLI</a>'s <code>tree-sitter playground</code> subcommand.</p>
<a href="/tree-sitter/creating-parsers">CLI</a>'s <code>tree-sitter playground</code> subcommand.</p>
<p>The syntax tree should update as you type in the code. As you move around the
code, the current node should be highlighted in the tree; you can also click any
node in the tree to select the corresponding part of the code.</p>
<p>Logging (if enabled) can be viewed in the browser's console.</p>
<p>You can enter one or more <a href="/using-parsers#pattern-matching-with-queries">patterns</a>
<p>You can enter one or more <a href="/tree-sitter/using-parsers#pattern-matching-with-queries">patterns</a>
into the Query panel. If the query is valid, its captures will be
highlighted both in the Code and in the Query panels. Otherwise
the problematic parts of the query will be underlined, and detailed

2
test/fuzz/README.md
View file

@ -34,7 +34,7 @@ The `run-fuzzer` script handles running an individual fuzzer with a sensible def
which will log information to stdout. Failing testcases and a fuzz corpus will be saved to `fuzz-results/<grammar-name>`. The most important extra `libFuzzer` options are `-jobs` and `-workers` which allow parallel fuzzing. This is can done with, e.g.:
```
./script/run-fuzzer <grammer-name> halt -jobs=32 -workers=32
./script/run-fuzzer <grammar-name> halt -jobs=32 -workers=32
```
The testcase can be used to reproduce the crash by running: