This branch is a full, incompatible, rewrite of nvim-treesitter and work in progress. This branch REQUIRES (the latest commit on) Neovim master.
The nvim-treesitter plugin provides
- functions for installing, updating, and removing tree-sitter parsers;
- a collection of queries for enabling tree-sitter features built into Neovim for these languages.
- Neovim 0.10.0 or later (nightly)
tarandcurlin your path (or alternativelygit)- a C compiler in your path and libstdc++ installed (Windows users please read this!)
- optional:
tree-sitterCLI andnode
You can install nvim-treesitter with your favorite package manager (or using the native package feature of vim, see :h packages).
NOTE: This plugin is only guaranteed to work with specific versions of language parsers (as specified in the lockfile.json). When upgrading the plugin, you must make sure that all installed parsers are updated to the latest version via :TSUpdate.
It is strongly recommended to automate this; e.g., using lazy.nvim
require('lazy').setup(
{ 'nvim-treesitter/nvim-treesitter', build = ':TSUpdate', lazy = false }
)NOTE: This plugin does not support lazy-loading.
nvim-treesitter can be configured by calling setup. The following snippet lists the available options and their default values. You do not need to call setup for nvim-treesitter to work using default values.
require'nvim-treesitter'.setup {
-- A list of parser names or tiers ('stable', 'core', 'community', 'unsupported')
ensure_install = { },
-- List of parsers to ignore installing
ignore_install = { 'unsupported' },
-- Automatically install missing parsers when entering buffer
auto_install = false,
-- Directory to install parsers and queries to
install_dir = vim.fn.stdpath('data') .. '/site'
}Check :h nvim-treesitter-commands for a list of all available commands.
For nvim-treesitter to support a specific feature for a specific language requires both a parser for that language and an appropriate language-specific query file for that feature.
A list of the currently supported languages can be found on this page.
We are looking for maintainers to add more parsers and to write query files for their languages. Check our tracking issue for open language requests.
For related information on the supported languages, including related plugins, see this wiki page.
nvim-treesitter provides queries for the following features. These are not automatically enabled.
Treesitter highlighting is provided by Neovim, see :h treesitter-highlight. To enable it for a filetype, put vim.treesitter.start() in a ftplugin/<filetype>.lua in your config directory, or place the following in your init.lua:
vim.api.nvim_create_autocmd('FileType', {
pattern = { '<filetype>' },
callback = function() vim.treesitter.start() end,
})Treesitter-based folding is provided by Neovim. To enable it, put the following in your ftplugin or FileType autocommand:
vim.wo.foldexpr = 'v:lua.vim.treesitter.foldexpr()'Treesitter-based indentation is provided by this plugin but considered experimental. To enable it, put the following in your ftplugin or FileType autocommand:
vim.bo.indentexpr = "v:lua.require'nvim-treesitter'.indentexpr()"(Note the specific quotes used.)
Injections are used for multi-language documents, see :h treesitter-language-injections. No setup is needed.
These queries can be used to look up definitions and references to identifiers in a given scope. They are used, e.g., by the nvim-treesitter-refactor plugin.
If you have a parser that is not on the list of supported languages (either as a repository on Github or in a local directory), you can add it manually for use by nvim-treesitter as follows:
- Clone the repository or create a new project in, say,
~/projects/tree-sitter-zimbu. Make sure that thetree-sitter-cliexecutable is installed and in your path; see https://tree-sitter.github.io/tree-sitter/creating-parsers#installation for installation instructions. - Run
tree-sitter generatein this directory (followed bytree-sitter testfor good measure). - Add the following snippet to your
init.lua:
local parser_config = require('nvim-treesitter.parsers').configs
parser_config.zimbu = {
install_info = {
url = '~/projects/tree-sitter-zimbu', -- local path or git repo
files = { 'src/parser.c' }, -- note that some parsers also require src/scanner.c or src/scanner.cc
-- optional entries:
branch = 'develop', -- only needed if different from default branch
location= 'parser', -- only needed if the parser is in subdirectory of a "monorepo"
requires_generate_from_grammar = true, -- only needed if repo does not contain pre-generated src/parser.c
generate_requires_npm = true, -- only needed if parser has npm dependencies
},
}If you use a git repository for your parser and want to use a specific version, you can set the revision key
in the install_info table for you parser config.
- If the parser name differs from the filetype(s) used by Neovim, you need to register the parser via
vim.treesitter.language.register('zimbu', { 'zu' })If Neovim does not detect your language's filetype by default, you can use Neovim's vim.filetype.add() to add a custom detection rule.
- Start
nvimand:TSInstall zimbu.
You can also skip step 2 and use :TSInstallFromGrammar zimbu to install directly from a grammar.js in the top-level directory specified by url.
Once the parser is installed, you can update it (from the latest revision of the main branch if url is a Github repository) with :TSUpdate zimbu.
Note: Parsers using external scanner in C++ need to target C++11 or earlier. Newer versions are not supported.
Queries can be placed anywhere in your runtimepath under queries/<language>, with earlier directories taking precedence unless the queries are marked with ; extends; see :h treesitter-query.
E.g., to add queries for zimbu, put highlights.scm etc. under
vim.fn.stdpath('data') .. 'site/queries/zimbu'Before doing anything, make sure you have the latest version of this plugin and run :checkhealth nvim-treesitter.
It can also help to update the parsers via :TSUpdate.
-
Check the
nvim-treesittersection of:checkhealthfor any warning, and make sure that the query for{X}is listed for{language}. -
Ensure that the feature is enabled as explained above.
-
Ensure Neovim is correctly identifying your language's filetype using the
:echo &filetypecommand while one of your language's files is open in Neovim.
This is probably due to a change in a parser's grammar or its queries.
Try updating the parser that you suspect has changed (:TSUpdate {language}) or all of them (:TSUpdate).
If the error persists after updating all parsers,
please open an issue.
This could be due a query file outside this plugin using outdated nodes, or due to an outdated parser.
- Make sure you have the parsers up to date with
:TSUpdate - Make sure you don't have more than one
parserruntime directory. You can execute this command:= vim.api.nvim_get_runtime_file('parser', true)to find all runtime directories. If you get more than one path, remove the ones that are outside this plugin (nvim-treesitterdirectory), so the correct version of the parser is used.
In your Lua config:
require("nvim-treesitter.install").prefer_git = trueYou can either configure curl to use additional CLI arguments in your Lua config:
require("nvim-treesitter.install").command_extra_args = {
curl = { "--proxy", "<proxy url>" },
}or you can configure git via .gitconfig and use git instead of curl
require("nvim-treesitter.install").prefer_git = trueI want to use a mirror instead of "https://github.com/"
In your Lua config:
for _, config in pairs(require("nvim-treesitter.parsers").configs) do
config.install_info.url = config.install_info.url:gsub("https://github.com/", "something else")
end
require'nvim-treesitter'.setup {
--
--
}