nvim-ts-rainbow2 VS Comment.nvim

You should continue with the fork nvim-ts-rainbow2 instead. But I also have the same problem. The colors are not updated instantaneously and sometimes pairs are mismatched. But most of the time formatting the file works fine. Other times simple :e solves it certainly.

Author of nvim-ts-rainbow2 (fork of the aforementioned nvim-ts-rainbow) here.

If you are afraid of missing something, then I recommend you to put all public symbols in one file. For example, in nvim-ts-rainbow2 the file lua/ts-rainbow re-exports symbols from private modules for public use. Whenever I add a new symbol to the table I know I have to document it.

I was using a recent fork of it from 'mrjones2014'. Now I tried https://gitlab.com/HiPhish/nvim-ts-rainbow2 too, still the same issue random order in different files. So weird :(

for the past few days I have been working on a fork to the nvim-ts-rainbow plugin: nvim-ts-rainbow2. I am pretty much done, except for one small issue: finding out the level of a node relative to other container nodes. I know how to determine the level of a node in the tree (just keep counting up from 1 while going through the parents until I hit the root), but that is not what I need.

Do you have any concrete plans on what you want to change? I have created a fork as well, but one which intends to overhaul the code quite a bit. See the TODO file for an overview (some of it is already implemented).

I have now forked to incorporate my ideas. The key idea is to abstract away the concept of a "strategy", which is to say how to perform the highlighting. The default strategy for now is the global highlight in which the entire buffer is lit up like a Christmas tree. The next strategy will be like in the PR above to highlight only the current sub-tree that contains the cursor (see video in linked issue).

Treesitter is a syntax parser that'll build a tree-like structure to enable anything from excellent syntax highlighting through to complex refactoring. There are so many creative ways you can use Treesitter, from jumping around text objects to commenting sections of code, it's a must-have in my books.

A couple nice quality of life plugins would be: Comment (which lets you use a keybinding to comment/uncomment things), Autopairs (which will make the paired brackets/parentheses/etc.), and Rainbow2 (which color-matches the pairs if things like parentheses).

I am reading the documentation for the [Comments](https://github.com/numToStr/Comment.nvim] plugin with :h comment.config and I see this

I was wondering what plugins you use for comments, actually, I'm using numToStr/Comment.

Nowadays, people (mostly) autogenerate their help docs with either markdown or emmmylua are their source. You are facing an issue that I faced before with Comment.nvim.

Comment.nvim?

Based on your reply I recommend taking out the comment plugin, replacing it with https://github.com/nvim-treesitter/nvim-treesitter-textobjects and https://github.com/numToStr/Comment.nvim