fm-nvim VS xplr.vim

fm-nvim

I'm already using vifm as my main-file-manager so I'm using `fm-nvim with a custom vifm-open-function to open up vifm in nvim.

For "neighbour" files of the current buffer I normally use :NeoTreeReveal if the file is in the main repo. (the current pwd). If not I'll use fm-nvim with ranger. I can use the Ranger %:p:h command to open the folder of the current folder in ranger without changing the pwd in vim.

I'm using vifm as my file manager which is pretty awesome in combination with (n)vim which is easy possible thanks to fm-nvim.

- https://github.com/is0n/fm-nvim

I've recently released a Neovim plugin that opens a floating window with 1/5 terminal file managers called fm-nvim. It's quite small and fast as the entire plugin is written in less than 100 lines of Lua.

xplr.vim

Xplr, a hackable, minimal, fast TUI file explorer

xplr (TUI file explorer)

The supported file managers (as of right now) are nnn, lf, ranger, xplr, and vifm.

Being super configurable, [xplr][xplr] by design integrates well with other tools. Try this fzf integration tutorial or this vim plugin if you are not convinced yet.

Fun fact: xplr has a vim plugin.

I use xplr with plugin for exploring and fzf for searching.

View on GitHub

Now, I would like to clean up, probably improve and turn xplr.vim into a real and well maintained plugin, with its own dedicated variables and docs. However, I have no experience with vim plugin development and decided that it's better to offload this task to someone who knows their way around the (neo)vim plugin system, so that I can focus more on xplr's development instead.