fugitive (via vim) VS ale

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. - Source: Hacker News / 4 months ago

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... Source: 7 months ago

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). Source: 10 months ago

I replace vim-fugitive with :! git. Source: 11 months ago

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... Source: 11 months ago

Support for code quality tools are provided by the ALE plugin. These are supported for PHP:. - Source: dev.to / 3 months ago

Hello Everyone! W0rp here. I thought I'd ask on Reddit if there's anyone out there would like to help maintain ALE. It would be nice to have another willing volunteer who is up for providing relevant feedback on PRs, answering common questions, merging good PRs, and managing GitHub issues. I'll mention to anyone interested that I have a general policy of never closing issues, no matter how old, unless they are... Source: 5 months ago

Ctrl-X Ctrl-L is line based completion, see :help CTRL-X_CTRL-L for details. :help ins-completion gets the useful docs, Vim's own docs are very good and worth spending some time learning how to use, so you can learn Vim itself better. Another favorite of mine is 'gf' to open the filename under the cursor, very useful combined with ^X ^F. Omni completion is also useful: https://vim.fandom.com/wiki/Omni_completion... - Source: Hacker News / 7 months ago

FWIW, I still use regular vim with ale [0] and it does everything I want. It formats files with Black and isort, shows ruff and pyright errors, supports jumping to definitions, and has variable information available on hover. I have collected my config over the past several years, but I pretty rarely encounter errors with it. [0]: https://github.com/dense-analysis/ale. - Source: Hacker News / 10 months ago

At some of those syntax things neovim behaves better, and like. But there is https://github.com/dense-analysis/ale. Source: 10 months ago