4 ms·
Maybe in the general case, but not in the scenario I outlined above. What if there are 20 files I touched? I'll need to type each of the 20 paths to view each
by Mouse47 9y ago
Maybe in the general case, but not in the scenario I outlined above. What if there are 20 files I touched? I'll need to type each of the 20 paths to view each individual diff. And that's if I view each diff only once, which I don't typically do.
I understand the value of being familiar with your tools, but sometimes the CLI just isn't the right one.
EDIT: btw, I use the vim plugins in all of my work (VS, VSCode), so I'm not shy when it comes to learning curves.
- whorleater 9y ago>git diff Gets all the differences between your current unstaged changes vs your head, no need for typing 20 individual paths
- Mouse47 9y agoGood to know, although I'm still not impressed with its presentation when doing larger diffs.
- dotancohen 9y agoThen use a different `diff` app, such as the wonderful graphical kdiff if you're on KDE. You can find the differ that you like and then set `git` use it as a default.
- Mouse47 9y agoThen we're back to using a GUI, which is what I was arguing for in the first place lol
- dotancohen 9y agoTrue, but a graphical differ I'll concede could be easier to use than a CLI differ for some people. But a full graphical Git environment is horrible. I've seen my Windows-using colleagues use them. Shudder. By the way, you might want to look at the `--diff-word` option.