-
I maintain a small git status prompt plugin (https://github.com/abathur/lilgit) that uses a mix of git2 and shelling out for diff commands that are much faster via the git CLI. I needed a distraction this weekend so I (finally) took a look at switching it to gitoxide: abathur/lilgit@fec61d6#diff-0d38d1e1503421fbfddac213c09243d5eec6a47822631b22458c804c7005694a This went pretty well, though it did leave me wondering:
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
Thanks for sharing! I left a few comments on the commit you linked.
Yes, I really liked what I saw and how the
At the moment this is the best choice even for |
Beta Was this translation helpful? Give feedback.
Thanks for sharing!
I left a few comments on the commit you linked.
Yes, I really liked what I saw and how the
head
API shines in comparison togit2
. Theupstream()
method ingit2
is really missing ingitoxide
though, and it shows. That definitely has to change but I don't know when it will.At the moment this is the best choice even for
gitoxide
. However,gix
will be significantly faster in the case that something is dirty as you will be able to make it stop once the first change or untracked file has been found. Also, all the involved diffs will be run in paralle…