Traditional highlighting (left) vs Treesitter-based highlighting (right).

Warning: Treesitter and Treesitter highlighting are an experimental feature of nightly versions of Neovim. Please consider the experience with this plug-in as experimental until Neovim 0.5 is released!

• Neovim nightly
• git in your path.
• A C compiler in your path (Windows users please read this!).

You can install nvim-treesitter with your favorite package manager, or using the default pack feature of Neovim!

If you are using vim-plug, put this in your init.vim file:

Plug 'nvim-treesitter/nvim-treesitter'

We highly recommend reading :h packages to learn more about this feature, but you can still follow these steps:

$ mkdir -p ~/.local/share/nvim/site/pack/nvim-treesitter/start
$ cd ~/.local/share/nvim/site/pack/nvim-treesitter/start
$ git clone https://github.com/nvim-treesitter/nvim-treesitter.git

Treesitter uses a different parser for every language. It can be quite a pain to install, but fortunately nvim-treesitter provides two command to tackle this issue:

• TSInstall {language} to install one or more parsers. TSInstall <tab> will give you a list of supported languages, or select all to install them all.
• TSInstallInfo to know which parser is installed.

Let's say you need parsers for lua, this is how you install it:

:TSInstall lua
Downloading...
Compiling...
Treesitter parser for lua has been installed

Cool, lets see which parsers are installed:

:TSInstallInfo
lua        [✓] installed
c          [✗] installed
html       [✗] not installed
typescript [✗] not installed
...

And now you should be ready to use every functionality nvim-treesitter provides!

All modules are disabled by default, so you'll need to activate them by putting this in your init.vim file:

lua <<EOF
require'nvim-treesitter.configs'.setup {
  ensure_installed = "all",     -- one of "all", "language", or a list of languages
  highlight = {
    enable = true,              -- false will disable the whole extension
    disable = { "c", "rust" },  -- list of language that will be disabled
  },
}
EOF

Check :h nvim-treesitter-modules for a list of available modules and its options.

Consistent syntax highlighting.

lua <<EOF
require'nvim-treesitter.configs'.setup {
  highlight = {
    enable = true,
    custom_captures = {
      -- Highlight the @foo.bar capture group with the "Identifier" highlight group.
      ["foo.bar"] = "Identifier",
    },
  },
}
EOF

Incremental selection based on the named nodes from the grammar.

lua <<EOF
require'nvim-treesitter.configs'.setup {
  incremental_selection = {
    enable = true,
    keymaps = {
      init_selection = "gnn",
      node_incremental = "grn",
      scope_incremental = "grc",
      node_decremental = "grm",
    },
  },
}
EOF

Highlights definition and usages of the current symbol under the cursor.

lua <<EOF
require'nvim-treesitter.configs'.setup {
  refactor = {
    highlight_definitions = { enable = true },
  },
}
EOF

Highlights the block from the current scope where the cursor is.

lua <<EOF
require'nvim-treesitter.configs'.setup {
  refactor = {
    highlight_current_scope = { enable = true },
  },
}
EOF

Renames the symbol under the cursor within the current scope (and current file).

lua <<EOF
require'nvim-treesitter.configs'.setup {
  refactor = {
    smart_rename = {
      enable = true,
      keymaps = {
        smart_rename = "grr",
      },
    },
  },
}
EOF

Provides "go to definition" for the symbol under the cursor, and lists the definitions from the current file. If you use goto_definition_lsp_fallback instead of goto_definition in the config below vim.lsp.buf.definition is used if nvim-treesitter can not resolve the variable. goto_next_usage/goto_previous_usage go to the next usage of the identifier under the cursor.

lua <<EOF
require'nvim-treesitter.configs'.setup {
  refactor = {
    navigation = {
      enable = true,
      keymaps = {
        goto_definition = "gnd",
        list_definitions = "gnD",
        goto_next_usage = "<a-*>",
        goto_previous_usage = "<a-#>",
      },
    },
  },
}
EOF

Define your own text objects mappings similar to ip (inner paragraph) and ap (a paragraph).

lua <<EOF
require'nvim-treesitter.configs'.setup {
  textobjects = {
    select = {
      enable = true,
      keymaps = {
        -- You can use the capture groups defined in textobjects.scm
        ["af"] = "@function.outer",
        ["if"] = "@function.inner",
        ["ac"] = "@class.outer",
        ["ic"] = "@class.inner",

        -- Or you can define your own textobjects like this
        ["iF"] = {
          python = "(function_definition) @function",
          cpp = "(function_definition) @function",
          c = "(function_definition) @function",
          java = "(method_declaration) @function",
        },
      },
    },
  },
}
EOF

Define your own mappings to swap the node under the cursor with the next or previous one, like function parameters or arguments.

lua <<EOF
require'nvim-treesitter.configs'.setup {
  textobjects = {
    swap = {
      enable = true,
      swap_next = {
        ["<leader>a"] = "@parameter.inner",
      },
      swap_previous = {
        ["<leader>A"] = "@parameter.inner",
      },
    },
  },
}
EOF

Define your own mappings to jump to the next or previous text object. This is similar to ]m, [m, ]M, [M Neovim's mappings to jump to the next or previous function.

lua <<EOF
require'nvim-treesitter.configs'.setup {
  textobjects = {
    move = {
      enable = true,
      goto_next_start = {
        ["]m"] = "@function.outer",
        ["]]"] = "@class.outer",
      },
      goto_next_end = {
        ["]M"] = "@function.outer",
        ["]["] = "@class.outer",
      },
      goto_previous_start = {
        ["[m"] = "@function.outer",
        ["[["] = "@class.outer",
      },
      goto_previous_end = {
        ["[M"] = "@function.outer",
        ["[]"] = "@class.outer",
      },
    },
  },
}
EOF

set foldmethod=expr
set foldexpr=nvim_treesitter#foldexpr()

This will respect your foldnestmax setting.

echo nvim_treesitter#statusline(90)  " 90 can be any length
module->expression_statement->call->identifier

Each feature can be enabled or disabled by different means:

:TSBufEnable {module} " enable module on current buffer
:TSBufDisable {module} " disable module on current buffer
:TSEnableAll {module} [{ft}] " enable module on every buffer. If filetype is specified, enable only for this filetype.
:TSDisableAll {module} [{ft}] " disable module on every buffer. If filetype is specified, disable only for this filetype.
:TSModuleInfo [{module}] " list information about modules state for each filetype

Check :h nvim-treesitter-commands for a list of all available commands.

For nvim-treesitter to work, we need to use query files such as those you can find in queries/{lang}/{locals,highlights,textobjects}.scm

We are looking for maintainers to write query files for their languages.

List of currently supported languages:

• bash (maintained by @TravonteD)
• c (maintained by @vigoux)
• c_sharp (maintained by @svermeulen)
• cpp (maintained by @theHamsta)
• css (maintained by @TravonteD)
• dart (maintained by @Akin909)
• elm
• fennel (maintained by @TravonteD)
• go (maintained by @theHamsta, @WinWisely268)
• haskell
• html (maintained by @TravonteD)
• java (maintained by @p00f)
• javascript (maintained by @steelsojka)
• jsdoc (maintained by @steelsojka)
• json (maintained by @steelsojka)
• julia
• lua (maintained by @vigoux)
• markdown
• nix
• ocaml (maintained by @undu)
• php (maintained by @tk-shirasaka)
• python (maintained by @stsewd, @theHamsta)
• Tree-sitter query language (maintained by @steelsojka)
• regex (maintained by @theHamsta)
• rst (maintained by @stsewd)
• ruby (maintained by @TravonteD)
• rust (maintained by @vigoux)
• scala
• swift
• toml (maintained by @tk-shirasaka)
• tsx
• typescript (maintained by @steelsojka)
• vue
• yaml

The goal of nvim-treesitter is both to provide a simple and easy way to use the interface for Treesitter in Neovim, but also to add some functionalities to it.

You can find the roadmap here. The roadmap and all features of this plugin are open to change, and any suggestion will be highly appreciated!

Users and plugin authors can take advantage of modules by creating their own. Modules provide:

• Treesitter language detection support
• Attach and detach to buffers
• Works with all nvim-treesitter commands

You can use the define_modules function to define one or more modules or module groups.

require'nvim-treesitter'.define_modules {
  my_cool_plugin = {
    attach = function(bufnr, lang)
      -- Do cool stuff here
    end,
    detach = function(bufnr)
      -- Undo cool stuff here
    end,
    is_supported = function(lang)
      -- Check if the language is supported
    end
  }
}

Modules can consist of the following properties:

• module_path: A require path (string) that exports a module with an attach and detach function. This is not required if the functions are on this definition.
• enable: Determines if the module is enabled by default. This is usually overridden by the user.
• disable: A list of languages that this module is disabled for. This is usually overridden by the user.
• is_supported: A function that takes a language and determines if this module supports that language.
• attach: A function that attaches to a buffer. This is required if module_path is not provided.
• detach: A function that detaches from a buffer. This is required if module_path is not provided.

You can get some utility functions with

local ts_utils = require 'nvim-treesitter.ts_utils'

Check :h nvim-treesitter-utils for more information.

Queries are what nvim-treesitter uses to extract informations from the syntax tree, and they are located in the queries/{lang}/* runtime directories (like the queries folder of this plugin).

nvim-treesitter considers queries as any runtime file (see :h rtp), that is :

• if the file is in any after/queries/ folder, then it will be used to extend the already defined queries.
• Otherwise, it will be used as a base to define the query, the first query found (with the highest priority) will be the only one to be used.

This hybrid approach is the most standard way, and according to that, here is some ideas on how to use is :

• 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 directory.

Before doing anything make sure you have the latest version of this plugin and run :checkhealth nvim_treesitter. This will help you find where the bug might come from.

First, check the ## {language} parser healthcheck section of :checkhealth if you have any warning. If you do, it's highly possible that this is the cause of the problem. If everything is okay, then it might be an actual error.

In both cases, feel free to open an issue here.

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 is a well known issue, which arise when the tree and the buffer are getting out of sync. As this issue comes from upstream, we don't have any finite fix. To get around this, you can force reparsing the buffer with this command:

:write | edit | TSBufEnable highlight

This will save, restore and enable highlighting for the current buffer, fixing the issue.

This might happen, and is known to happen with vim-clap, to avoid those kind of errors, please use setlocal instead of set for the appropriate filetypes.