setting up Treesitter using a MiniMax config

[passmore]

Contributing guidelines

• I have read CODE_OF_CONDUCT.md

Module(s)

all of the above

Question

I have set up a newly installed neovim v0.13.0-dev-613+g1a7ab1ab47 using the MiniMax config starter. To register new languages with Treesitter I edited the 40_plugins.lua file a shown:

  add({
    "https://github.com/nvim-treesitter/nvim-treesitter",
    "https://github.com/nvim-treesitter/nvim-treesitter-textobjects",
  })

  -- Define languages which will have parsers installed and auto enabled
  -- After changing this, restart Neovim once to install necessary parsers. Wait
  -- for the installation to finish before opening a file for added language(s).
  local languages = {
    -- These are already pre-installed with Neovim. Used as an example.
    -- Add here more languages with which you want to use tree-sitter
    "lua",
    "vimdoc",
    "markdown",
    "bash",
    "bibtex",
    "css",
    "gitignore",
    "gpg",
    "html",
    "html_tags",
    "javascript",
    "latex",
    "regex",
    "ruby",
    "toml",
    "yaml",
    -- To see available languages:
    -- - Execute `:=require('nvim-treesitter').get_available()`
    -- - Visit 'SUPPORTED_LANGUAGES.md' file at
    --   https://github.com/nvim-treesitter/nvim-treesitter/blob/main
  }
  local isnt_installed = function(lang)
    return #vim.api.nvim_get_runtime_file("parser/" .. lang .. ".*", false) == 0
  end
  local to_install = vim.tbl_filter(isnt_installed, languages)
  if #to_install > 0 then
    require("nvim-treesitter").install(to_install)
  end

  -- Enable tree-sitter after opening a file for a target language
  local filetypes = {}
  for _, lang in ipairs(languages) do
    for _, ft in ipairs(vim.treesitter.language.get_filetypes(lang)) do
      table.insert(filetypes, ft)
    end
  end
  local ts_start = function(ev)
    vim.treesitter.start(ev.buf)
  end
  Config.new_autocmd("FileType", filetypes, ts_start, "Start tree-sitter")
end)

I ran :restart and :TSUpdate and confirmed that the listed parsers were downloaded to ~/.local/share/nvim/site/parser. I also installed tree-sitter-cli and added the parser path to `~/.config//tree-sitter/config.json parser-directories list.

However, Treesitter syntax highlighting only activates for the builtin filetypes: markdown, lua and vimdoc but not for any of the parsers I added like bash, latex or ruby. I have probably missed a step, but I can't see where. Can anyone help?

[echasnovski]

It seems to work for me at least for latex and ruby files. I had to make sure that the latex file is not just .*.tex as it is not recognized as LaTeX by default (but plaintex filetype instead).

However, Treesitter syntax highlighting only activates for the builtin filetypes: markdown, lua and vimdoc but not for any of the parsers I added like bash, latex or ruby. I have probably missed a step, but I can't see where. Can anyone help?

Couple of clarifying questions:

• How do you determine that tree-sitter highlighting is not activated? The most convenient thing to do that is to put cursor on some highlighted text and execute :Inspect. If it mentions "Treesitter", then it is active in the current buffer.
• Did you run :checkhealth vim.treesitter nvim-treesitter?

---

Also, as this is a MiniMax question, it would have been better to ask directly in MiniMax repo. So I moved it.

[passmore]

Initially, I didn't see any highlight colours, just monochrome text throughout. But when I run :Inspect in bash, tex or ruby files the response is "No items fount at position x,y in buffer z". In lua and markdown files :Inspect mentions Treesitter. I forgot to mention that I had also set vim.g.tex_flavor='latex' in options, so .*.tex should have been recognised as LaTeX. I did run :checkhealth vim.treesitter nvim-treesitter The first gave a big list of parsers marked OK. nvim-treesitter only reports installed languages as

Installed languages     H L F I J ~
- bash                  . . . . .
- bibtex                ✓ . ✓ ✓ ✓
- css                   . . . . .
- ecma
- gitignore             . . . . .
- gpg                   . . . . .
- html                  . . . . .
- html_tags
- javascript            . . . . .
- jsx
- latex                 . . . . .
- lua                   ✓ . ✓ . ✓
- markdown              ✓ . ✓ . ✓
- markdown_inline       ✓ . . . ✓
- regex                 . . . . .
- ruby                  . . . . .
- toml                  . . . . .
- vimdoc                ✓ . . . ✓
- yaml                  . . . . .

but other sections, Requirements and Install directory, say OK. Sorry about posting to the wrong repo, I didn't see this one initially.

[echasnovski]

I did run :checkhealth vim.treesitter nvim-treesitter The first gave a big list of parsers marked OK. nvim-treesitter only reports installed languages as ...

This doesn't look right to me. The vim.treesitter checkhealth should also have a section "Treesitter queries" listing which queries it can recognize.

The output of nvim-treesitter checkhealth shows that there are no recognized queries for installed languages (like ruby). Here is the output of the fresh MiniMax config where only the above list of languages was added (after :restart and waiting for all languages to be installed):

Installed languages     H L F I J ~
- bash                  ✓ ✓ ✓ ✓ ✓
- bibtex                ✓ . ✓ ✓ ✓
- css                   ✓ . ✓ ✓ ✓
- ecma
- gitignore             ✓ . . . ✓
- gpg                   ✓ . . . ✓
- html                  ✓ ✓ ✓ ✓ ✓
- html_tags
- javascript            ✓ ✓ ✓ ✓ ✓
- jsx
- latex                 ✓ . ✓ . ✓
- regex                 ✓ . . . .
- ruby                  ✓ ✓ ✓ ✓ ✓
- toml                  ✓ ✓ ✓ ✓ ✓
- yaml                  ✓ ✓ ✓ ✓ ✓

So I am afraid, there might be something going on either in other part of the config or system-wide. Couple more questions:

• Do you have this behavior in a fresh separate config or as a replacement for the old one? If the second one (and maybe even the first one), make sure that there is no 'lazy.nvim' installation affecting the installation (if you used one before).
• If the above does not help, then I'd ask to try to reproduce this in a fully separate config where the only change is the added new languages. Like NVIM_APPNAME=nvim-minimax or another previously unused one, as described here. This will help to determine if the problem is on Neovim or overall system level.

[passmore]

Thanks, I tried the install again as you suggested with NVIM_APPNAME=nvim-minimax and just added the languages. This time everything worked well. Output of :checkhealth vim.treesitter nvim-treesitter is here. I've never installed lazy.nvim but have experimented with a variety of Neovim configs, most recently using Lazy and Mason, but wanting to simplify things as Treesitter and vim.pack have become built-in in recent releases. I think MiniMax is a great help with this, but I guess I didn't clean up well enough before moving it to ~/.config/nvim/. Thanks again for your help.

[echasnovski]

I've never installed lazy.nvim but have experimented with a variety of Neovim configs, most recently using Lazy and Mason ...

The LazyVim distro is built around 'lazy.nvim' plugin manager. So if it was used as the main config (in ~/.config/nvim), then it indeed was installed somewhere. It probably interfered with 'runtimepath' somehow and didn't make installed queries visible for the Neovim process.

As a side note, Mason is not a Neovim config, but a 'mason-org/mason.nvim' plugin which MiinMax can work with (and I personally use it).