nvim-cursorword VS mini.nvim

Try nvim-cursorword

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.

Finally, I think this should be solved upstream (probably LSP / the author of this API) instead. And I did find an alternative that can highlight the cursor word immediately, xiyaowong/nvim-cursorword, the only problem is that it is completely NOT LSP-related, no usage of treesitter (so hovering on the Lua function won't highlight its end). But who cares? If a feature cannot provide a good UX, it is f**king useless IMOO.

I was sleeping. Did you mean this one? [xiyaowong/nvim-cursorword](https://github.com/xiyaowong/nvim-cursorword)

This is essentially a tagline of mini.move.

Just as the others suggested, oil.nvim solves this outta the box. I freaking love it (here my config in case ya need it). Apparently also mini.files handles this by default

You mean backwards seeking text objects? You can get those with mini.ai https://github.com/echasnovski/mini.nvim/blob/main/readmes/mini-ai.md

I would like to offer you to join me in saying late greetings to this autumn with a release of mini.nvim version 0.10.0. It is mostly about introducing three (quite feature full, dare I say) modules and minor updates of existing ones.

Last night I cleaned up all the dead code in my config and realised that mini.nvim has to be the single best plugin that I've used. I have a couple of other favourites but this collection has been so consistently good that I wanted to give some thanks to the juggernaut that is u/echasnovski! Thanks for all the work you plugin authors and core maintainers put in to make this editor what it is <3

For example: I spent a lot of time configuring file tree plugins to have the same sorting as VS Code, tweaking their icons, etc. But then I realized I barely used the file explorer at all, and now I'm super happy with the minimal approach of mini.files. I had similar experiences with other plugins that were just adding "fluff" instead of the functionality I was looking for.

Around two weeks ago I've announced the release of mini.files - a file explorer module of mini.nvim with column view navigation and "edit text to manipulate file system" design. This resulted into a great feedback from the community, much of which turned into new features.

A mini.ai textobject specification that you can use standalone