vim-renamer VS vim-eunuch

I use vim-renamer for stuff like this.

I use this plugin - works wonderfully

Also, related to dired: vim-renamer lets you rename files kinda like dired by editing their names in a buffer and saving.

I like vim-renamer for doing renames. It opens a buffer with your filenames in it, you can modify the filenames, and when you save it applies those renames.

Honorable mention : vim-eunch has this feature plus many other convenience commands.

I use eunuch.vim mostly by executing :Rename or :Remove or :Move. I also use this plugin whenever I have to manipulate multiple files in the working directory using :Cfind -name '*.lua' -type f which puts all .lua files in the cwd in the quickfix list then doing something like :cfdo lua vim.lsp.buf.format() to format all files.

If you are avoiding vim plugins due to external, non-standard dependencies (e.g. fzf), then you might be pleased to know that some plugins can solve this problem with standard linux utilities, like :Cfind and :Lfind from tpope/vim-eunuch which use the find linux utility.

I use vim-dirvish(you probably want to pair this with vim-enunch), it's a more minimal version of Netrw.

Try vim-eunuch lua {'tpope/vim-eunuch', config = function () vim.cmd('cnoreabbrev rename Rename') --:rgb + to trigger end},

I use netrw but I do moving, renaming etc with vim-eunuch and have done for about ten years. It just works how you'd expect it to.

You might want to look into :Delete from tpope's vim-eunuch, along with wrappers for mkdir, chmod, etc.

I did try: 1. Using the vim file explorer move command: 1. It does not implement autocomplete 1. I cannot use the vim movement shortcuts to move in the path, so I need to use the arrow keys to get before the file name. (dealbreaker) 1. It does not rename the buffer 1. Using eunuch plugin Move command: https://github.com/tpope/vim-eunuch 1. Relative paths were dependent on doing a change directory command first. That is fine but bothersome. 1. Required me to write the filename manually if I used the autocomplete. I did not find an efficient way to paste the current file name (without the path) to a command argument. 1. All in all quite close but still not good enough for me.