vim-eunuch VS vim-fugitive

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.

the only reason I do some git stuff in vim and not _always_ in the shell, is because tpope is very thoughtful and fugitive.vim provides nice ways to deal with hunks or hunk partials (visually selecting a range within a hunk, for i.e.)

https://github.com/tpope/vim-fugitive/blob/master/doc/fugiti...

I agree, navigating blame history is incredibly useful, if only to save you from asking the wrong person about a particular change.

Vim's Fugitive[1] can do this and also in Textmate to. So I would hope that most editor git plugins can.

1. https://github.com/tpope/vim-fugitive

Git: vim-fugitive and gitsigns.nvim

You'll want to invest the time in learning Magit, which will change your life once you get the hang of it (and I was a heavy user of Fugitive in Vim previously!), and it's unlikely you'll find a better integration with GDB anywhere else on the planet than with Emacs, though I can't say that empirically. You just need to take the plunge and start learning it, then cut over and take the hit in productivity one day when you're feeling adventurous. You'll ultimately become far more powerful than you've ever been. Especially if you delve into elisp over time. I use Spacemacs, which is bloated and has bugs, but it has so many features that I haven't undertaken the massive endeavor to replace it from scratch yet.

For an option that works on Vim, if you already use tpope's vim-fugitive, there's vim-rhubarb (for GitHub) and fugitive-gitlab.vim (for GitLab).

I replace vim-fugitive with :! git

The only thing I truly miss from Emacs is [Magit](https://magit.vc/) since I still consider it the best git wrapper available. It is just too good. Unfortunately [Neogit](https://github.com/TimUntersberger/neogit) is not quite there yet although I hope it makes it at some point. I didn't like [Fugitive]https://github.com/tpope/vim-fugitive), but I ended up finding a good enough workaround by using [Lazygit](https://github.com/jesseduffield/lazygit) through [Toggleterm](https://github.com/akinsho/toggleterm.nvim).

I do think VSCode is a great tool and I recommend it frequently to people, but I still want to set the record straight here. Yes, vim is obviously limited in the sense that as a CLI app it doesn't draw it's own PDF or HTML windows, that's fair. But it can remote control your favorite PDF viewer or browser for roughly the same functionality. I'm currently writing my thesis using vimtex and it's quite smooth. And all the other stuff you mention is implemented quite competently by various plugins like vim-fugitive, coc.nvim, vimspector and copilot.vim.

Edit: je viens de trouver [https://github.com/tpope/vim-fugitive de Val