flash.nvim VS mini.nvim

I came across this term in https://github.com/folke/flash.nvim but couldn't figure out how to use this Search method.

flash.nvim supports jumping to treesitter nodes by labels(just like leap does for searching text). You might want to give that a try and see if it fits your needs.

The new plugin from Folke https://github.com/folke/flash.nvim has enhanced f, t, F, T motions and tons leap motions features!

There actually is one plugin, namely flash.nvim, which does something roughly in that direction for search; as soon as you type a unique string it jumps you to the respective location. https://github.com/folke/flash.nvim

return { -- https://github.com/folke/flash.nvim { "folke/flash.nvim", event = "VeryLazy", opts = { labels = "asdfghjklqwertyuiopzxcvbnm", }, config = function(_, opts) local flash = require("flash") flash.setup(opts) _G.flashnav = { jump = function () flash.jump({ search = { mode = "search"}, }) end, jumptoline = function () flash.jump({ search = { mode = "search", max_length = 0 }, label = { after = { 0, 0 } }, pattern = "^" }) end

-- Plugins require("lazy").setup({ -- Motions [https://github.com/folke/flash.nvim] "folke/flash.nvim", event = "VeryLazy", ---@type Flash.Config opts = {}, keys = { { "s", mode = { "n", "x", "o" }, function() require("flash").jump() end, desc = "Flash", }, { "S", mode = { "n", "o", "x" }, function() require("flash").treesitter() end, desc = "Flash Treesitter", }, { "r", mode = "o", function() require("flash").remote() end, desc = "Remote Flash", }, { "R", mode = { "o", "x" }, function() require("flash").treesitter_search() end, desc = "Flash Treesitter Search", }, { "", mode = { "c" }, function() require("flash").toggle() end, desc = "Toggle Flash Search", }, }, })

I just released a new plugin!

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