telescope-zf-native.nvim VS mini.nvim

If i understand you right i think you want this https://github.com/natecraddock/telescope-zf-native.nvim

Thanks a lot for your great work! Will zf-native be used to replace fzf-native as the repository of zf-native contains pre-compiled libzf binaries and still very small in repo size?

This looks awesome! As someone who is already pretty invested in trouble.nvim and native integrations with Telescope and GitSigns (to name just two), what do you feel are the selling points? I wonder how you see integrations evolving too? In example, I use zf via telescope-zf-native.nvim over fzf and have had to do little to let other plugins fallback into that.

You probably want one of telescope-fzf-native.nvim or telescope-zf-native.nvim, which are both telescope extensions that replace the default fzy-like sorter. The default doesn't allow spaces in the query, but both fzf and zf should.

I made an issue tracking this: https://github.com/natecraddock/telescope-zf-native.nvim/issues/3. Hopefully I can get it resolved quickly!

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