2. Yes, that was the only reason I have used git GUIs, but most modern editors have these features built-in.
Still, usually what I need there is the ability to leave a line or two there but don't stage it.
You get more context because you can see other parts of the diff in the editor, unlike when using the -p switch with the git add or reset commands.
GitGutter make working with hunks easy
>> You cannot unstage a staged hunk.
I'm not sure if that's a feature they plan to support, but something like this could easily be done by highlighting the hunk displayed when running git diff --cached in vim's linewise visual mode and filtering it through git apply -R --cached -.
I guess you would not want to edit a text file of which you could only see a single line at a time.
Projects can be messy and sometime you really need a bird's view of what's going on with all those branches\merges etc.
I felt a certain bravado in uni for always using the cli that I see among other HNers. As I get older, I couldn't give less of a damn. Scrolling manpages to find an re-remember the unintuitive cli arg I need vs just clicking a button that does it? I prefer the latter. The former is always available if I need it.
The few times I have to drop into cli git are the things I always have to look up anyways, like git-reflog.
1. you can see all the information at on glance: current branch, all local branches all remotes and remot branches, local changes, recent commits, current merge conflics
2. cherry picking single lines for staging in multiple files is much faster in a GUI than via terminal (maybe there are clever tricks to make it easier I don't know of)