vim-arpeggio VS vim-fugitive

Might be able to pull something like this off with https://github.com/kana/vim-arpeggio

If the reason for not liking jk is that it doesn't work for visual mode, and you are not using the which-key plugin, I would suggest the vim-arpeggio plugin. You'll have to hit jk very quick for exit so it won't interrupt j and k movement in visual mode

kana/vim-arpeggio for the jk ==> mapping

But today, I found the plugin vim-arpeggio, it maps key chords, i.e., keys pressed (seemingly) simultaneously. I tried it out and omg, it solves everything. No longer do I need to wait for timeoutlen, no longer do I miss a k at the end of word: jk and kj only triggers when pressed simultaneously, and I don't have to set timeoutlen insanely short.

vim-arpeggio: Keychords for custom mappings (since there are not enough 'free keys' available)

The half keyboard basically mirrors the keyboard while the spacebar is held down (so you have, for example, normal “asdf” that then turns into “;lkj” while space is pressed). It sounds weird but if you touch type it’s surprisingly easy to get used to because the same fingers press the same keys—your index finger presses both “f” and “j” as normal. You might be able to emulate it with something like vim-arpeggio.

But there is e.g. this plugin, that tries to achieve it, possibly others as well: https://github.com/kana/vim-arpeggio

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