.cfg VS nvim-colorizer.lua

Internal validation behaviours are a bit complex to be fully described in this article. The full code is found here, though.

It is possible to find related configuration files tracked in my dotfiles repository. Also, I gathered the most helpful resources I found in the Neovim learning path. You will find at that location most of the resources I am going to reference, and also additional ones I could not fit in this article.

I'm new to neovim and want to change the default config options for colorizer.lua.

Even though we're on r/vim, many people here actually use Neovim, so I have to ask: do you have tree-sitter? If so, you need to enable the additional_vim_regex_highlighting option of the highlight module in nvim-treesitter since vim-css-color depends on Vim's syntax highlighting rather than Neovim's. An alternative would be to use a Neovim plugin that does the same thing with tree-sitter support – e.g nvim-colorizer (I haven't tested it at all).

It's nvim-colorizer if that would help.

- Is there a way to replace something like colorizer with your plugin?

norcalli/nvim-colorizer.lua - A high-performance color highlighter

I've been using https://github.com/norcalli/nvim-colorizer.lua

Are you sure about the name? I could not find any vim or neovim plugin called 'colorstil'. The closest google suggestion is this one https://github.com/norcalli/nvim-colorizer.lua

I'm using nvim-colorizer and sometimes that happens, :e forces the buffer to re-render which fixes it.

If you're using neovim, u can use https://github.com/norcalli/nvim-colorizer.lua, it's the one I use currently.