benbot/nvim-treesitter
1
0
Fork 0
mirror of https://github.com/nvim-treesitter/nvim-treesitter.git synced 2026-07-18 11:20:07 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

Fix readme setup example

Browse source
This commit is contained in:
drocha87 2020-11-11 16:52:35 -03:00 • committed by Thomas Vigouroux
parent 16fcbd1824
commit 12064efe2f
1 changed files with 4 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

5
README.md
View file

@ -105,6 +105,7 @@ All modules are disabled by default,
so you'll need to activate them by putting this in your `init.vim` file: so you'll need to activate them by putting this in your `init.vim` file:
```lua ```lua
lua <<EOF
require'nvim-treesitter.configs'.setup { require'nvim-treesitter.configs'.setup {
ensure_installed = "maintained", -- one of "all", "maintained" (parsers with maintainers), or a list of languages ensure_installed = "maintained", -- one of "all", "maintained" (parsers with maintainers), or a list of languages
highlight = { highlight = {
@ -112,6 +113,7 @@ require'nvim-treesitter.configs'.setup {
disable = { "c", "rust" }, -- list of language that will be disabled disable = { "c", "rust" }, -- list of language that will be disabled
}, },
} }
EOF
``` ```
Check [`:h nvim-treesitter-modules`](doc/nvim-treesitter.txt) Check [`:h nvim-treesitter-modules`](doc/nvim-treesitter.txt)
@ -175,7 +177,6 @@ Other modules can be installed as plugins.
- [playground](https://github.com/nvim-treesitter/playground) - Treesitter integrated playground - [playground](https://github.com/nvim-treesitter/playground) - Treesitter integrated playground
- [context](https://github.com/romgrk/nvim-treesitter-context) - Show parent code context in a popover - [context](https://github.com/romgrk/nvim-treesitter-context) - Show parent code context in a popover
# Extra features # Extra features
## Syntax based code folding ## Syntax based code folding
@ -219,6 +220,7 @@ List of currently supported languages:
<!--This section of the README is automatically updated by a CI job--> <!--This section of the README is automatically updated by a CI job-->
<!--parserinfo--> <!--parserinfo-->
- [x] [bash](https://github.com/tree-sitter/tree-sitter-bash) (maintained by @TravonteD) - [x] [bash](https://github.com/tree-sitter/tree-sitter-bash) (maintained by @TravonteD)
- [x] [c](https://github.com/tree-sitter/tree-sitter-c) (maintained by @vigoux) - [x] [c](https://github.com/tree-sitter/tree-sitter-c) (maintained by @vigoux)
- [x] [c_sharp](https://github.com/tree-sitter/tree-sitter-c-sharp) (maintained by @svermeulen) - [x] [c_sharp](https://github.com/tree-sitter/tree-sitter-c-sharp) (maintained by @svermeulen)
@ -327,6 +329,7 @@ located in the `queries/{lang}/*` runtime directories (like the `queries` folder
This hybrid approach is the most standard way, and according to that, here is some ideas on how to This hybrid approach is the most standard way, and according to that, here is some ideas on how to
use is : use is :
- If you want to rewrite (or write) a query, don't use `after/queries`. - If you want to rewrite (or write) a query, don't use `after/queries`.
- If you want to override a part of a query (only one match for example), use the `after/queries` - If you want to override a part of a query (only one match for example), use the `after/queries`
directory. directory.