gitui

Personally, I just break out to the CLI for the vast majority of use cases. Things like viewing logs or making commits or staging hunks with `git add --patch`. I'd suggest looking at only replacing the parts of your workflow that are painful and keep what works. For example, I've heard many folks say that fugitive's `:Git blame` support is the killer feature for them. To that end, I'd probably pick up a good Terminal User Interface like `lazygit` before spending much time investing into fully driving git through vim. Grains of salt suggested, but if you're interested in exploring other git TUI options, I've also heard good things about `gitui`[0]. [0]: https://github.com/gitui-org/gitui

Side note, if you're a lazygit fan, consider using gitui as an alternative. Feature wise they're pretty similar but gitui is much faster and I find it easier to use. https://github.com/gitui-org/gitui

There're multiple solutions like this and I've used some of them over the past years. - There's obviously the fantastic Magit (https://github.com/magit/magit) which is an Emacs Plugin but you can configure your Emacs start up just with Magic and nothing else so that Emacs is only used as a TUI Git client. I did this for a while. - There's GitUI written in Rust (https://github.com/extrawurst/gitui) I did use this for a long time but recently switched over to LazyGit for the better Vim bindings and having more features - LazyGit (https://github.com/jesseduffield/lazygit) is what I'm using right now and I'm mostly happy I actually wrote my own in C some years ago called Gitsi (https://github.com/terhechte/gitsi). One thing that I added that (as far as I know) none of the others have and I sorely miss is VIM number based movements. So you can

Git gui in terminal https://github.com/extrawurst/gitui

There are some reasonably complex git tuis. https://github.com/extrawurst/gitui is one

I was missing interactive rebase, as it is missing from libgit2 https://github.com/extrawurst/gitui/issues/32

It's a low-level tool. Imagine writing code with Microsoft Word. There are layers on top of Git that give you more of what you're looking for. - https://github.com/extrawurst/gitui - https://github.com/jesseduffield/lazygit - https://magit.vc/

It's nice but I prefer https://github.com/extrawurst/gitui cause it's a little snappier.

See https://github.com/Extrawurst/gitui#3--benchmarks-top- for a comparison on indexing the linux kernel

Ah, I'm noticing that my parent comment didn't quite say what I intended! What I wanted to say, was that helix should make an additional keymapping file that has nearly identical keys to vim. Repositories like gitui [0] do this, so vim users can just jump in guns-blazing. Granted, they have far less keybinds to cover. The second link, "Migrating from vim", doesn't nearly cover all the differences between vim and helix. If there wasn't a keybinding file I could use, I would need a document that covers as many differences as possible between vim and helix. I found this document when trying to figure out a mapping in helix, and it didn't cover it. I can't remember what the mapping was though. I really want to use helix - I want lsp and tree-sitter out of the box in the terminal. I hate managing a neovim config. But I also use tons of other m

I use gitui. Its a TUI written in rust and it is great. I mainly use it for looking at the gitlog, committing, and pushing. https://github.com/extrawurst/gitui