neovim-plugin VS vim-illuminate

Definitely remove it, as it is an anti-pattern that gained popularity because individuals often copy content without careful consideration. As far as I know, it primarily originated from this Github post, which was created during the early days of Lua's growing popularity in Neovim as an attempt to reinvent the wheel.

I'm pretty sure we got started down the .setup road because of this article by norcalli a few years ago. It was published when plugins started using Lua and suddenly I went from seeing one or two plugins using .setup to literally every single plugin use it.

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.