oil.nvim VS mini.nvim

Oil is great: https://github.com/stevearc/oil.nvim

It just treats your file structure as a buffer

Hey , i'm using oil.nvim, it does integrate LSP rename file, but currently if you code in js you must apply this pull request https://github.com/stevearc/oil.nvim/pull/248 to fix refactor js ,ts file. (warning: the author says this pull request doesn't work with all pattern maybe it will be updated in future )

File explorer: oil.nvim

Hello, i've tried Oil.nvim and liked it , but when people talk about it , in general questions about FileTrees and File Browsers people really swear by Oil.nvim and got me wondering,what am i missing?

A very nice plugin which I use whenever I have to edit/create multiple files is oil.nvim

For those that want this to replace `oil.nvim`, here are the keymaps I added to my config for it to behave the same as oil. The dash keymap will open `mini.files` in the current directory from the file you triggered the keymap. The `fe` keymap opens the `mini.files` at the root directory so you can use it like your file manager. I like that the location you leave the window when opening with `fe` is not affected by the location you leave the dash trigger. I hope that map makes sense. I use NvChad, so my mapping looks like this, but you should be able to use it in any distro or custom config.

https://github.com/stevearc/oil.nvim - file explorer

Maybe https://github.com/stevearc/oil.nvim? Nvim tree and neotree both have floating mode as well which I prefer more.

I use oil.nvim.

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