vim-illuminate VS nvim-lint

The vim-illuminate plugin offers the goto_next_reference() and goto_prev_reference() to navigate to next/previous reference of the word under the cursor.

vim-illuminate (https://github.com/RRethy/vim-illuminate) might be what you're looking for. It also has Alt-N/Alt-P mappings by default for jumping between matches.

You can add a prefix that's specific to your plugin, or just have a single field specific to your plugin's name which takes a table. Alternatively, in one of my plugins I use .configure strictly for configuration, which doesn't init the plugin, see https://github.com/RRethy/vim-illuminate/issues/112. The majority of configuration shouldn't be needed though if you have strong defaults, just look at tpope plugins.

Found it, vim-illuminate.

I think you're looking for vim-illuminate.

Does it do anything different from illuminate?

Ok, my guess is that you are using RRethy/vim-illuminate, xiyaowong/nvim-cursorword, or mini.cursorword. All of them use underline as default highlighting for word under cursor. And that you tried ellisonleao/gruvbox.nvim variant of Gruvbox, which doesn't explicitly support none of them.

setup is deprecated, use the opts table directly. Related stuff. Note that Leap is internally lazy-loaded anyway.

Personally, i think nvim-lint is the best alternative currently, specially so because it has no dependencies on external binaries. This guide assumes you already have your LSP set up with nvim-lspconfig (or an alternative like lsp-zero). You should also have an way to install the linters you are gonna need, i highly recommend Mason with mason-lspconfig.

Try out https://github.com/mfussenegger/nvim-lint for linting tools, it integrates with nvim diagnostics module, might cover all use cases of null-ls for someone shopping around.

People looking for alternative can check these projects: - nvim-lint - formatter.nvim

For linting, I would recommend nvim-lint. Again the same step as before, a little bit of setup code to register your linter and you're good to go!

This will be the third linting solution to make use of the [Neovim Diagnostic] module after null-ls and nvim-lint. All can co-exist, all have the pros and cons.

I use nvim-lint (https://github.com/mfussenegger/nvim-lint), but I still don't know exactly how to achieve your goals with it. My hunch is that it should be somewhat straightforward, since Lua code could be used to provide the executable command (i.e. if in poetry project then cmd =poetry run ...else if ... then ... end)

It's not obvious from the website, but this is the blog of GitHub user @mfussenegger, who is a Neovim core member, one of the primary maintainers of Neovim's LSP client implementation, and the other of several excellent plugins.

https://github.com/mfussenegger/nvim-lint works with the diagnostics API that was created after LSP was added, to allow non-LSP to use diagnostics API. Meaning you can see LSP and linting in the same interfaces if you use this API.

As part of my work-in-progress Neovim [plugin]([https://github.com/nat-418/tcl.nvim)(https://github.com/nat-418/tcl.nvim)) for Tcl development, I added support for Nagelfar syntax checking in the nvim-lint plugin. This provides inline checking for errors as seen in the attached screenshot. If anyone has any ideas on how to create a Tcl Language Server, or knows of a project already working on one, I would be very interested to know about it.