TimUntersberger

I believe vim already supports merges by default using `:h diff` so we can reuse the [diff view](#57) code for this once merged. I recently had a lot to do...

The current plan is to implement merge conflict resolution in [diffview.nvim](https://github.com/sindrets/diffview.nvim) and then just reuse the existing integration to support this. > I think that when you are just editing...

Would it be okay for you if you would have to open the cli history `$` to see the command output? We could add new events so you could automatically...

I added two notifications: * `Committing ...` which gets displayed when you start a commit and gets removed once the commit is done. * `Successfully commited!` which gets displayed when...

> I think in lieu of actually streaming the output, another way to approach this would be to have a text "spinner" that you could enable like "Committing..." that shows...

> Further, I cannot see the reason for failure: pressing $ (as the notification suggests) shows only commands like git status and git ls-files without any output from the commit....

Libgit2 seems like a better solution than writing pure cli commands. How could we then do the git command history stuff?

Just to make sure, are we talking about the same thing? I am talking about for example: `git status --....` this then gets added to the history along with the...

If you want to you can try changing an existing implementation to use libgit2, so we can see how this would work. The easiest one would probably be the status...

> should be too hard Do you mean `shouldn't be too hard` ? Nice work!