News for hackers. Stuff that matters.
Re:Show HN: Deff – side-by-side Git diff review in your term... by flamestro on Thursday February 26, 2026 @04:12PM (#47172058)
I personally find vimdiff a bit harder to navigate for my usecase. The reason is that I am context unaware of the file often in larger projects and wanted something that allows me to check all lines in a touched file. However, I have to admit vimdiff comes quite close to what I need and is a great tool!
Re:Show HN: Deff – side-by-side Git diff review in your term... by PhilipRoman on Thursday February 26, 2026 @05:03PM (#47172571)
zr?

vim folds are fully programmable. For me a bigger issue was git calling vimdiff for each file, which I fixed with my own difftool: https://gist.github.com/PhilipRoman/60066716b5fa09fcabfa6c95...

Re:Show HN: Deff – side-by-side Git diff review in your term... by anitil on Thursday February 26, 2026 @06:52PM (#47174094)
I ran in to a couple problems when trying that script (details below), but I'm really happy that you shared it, because I had not seen ':windo diffthis' before, and that method of scripting diffs. I'll definitely be customising it!

(I found that my mac machine doesn't support the '-printf' option, and also I was attempting to run 'git bvd main' on a branch but it seems it does a recursive directory diff, so I'll use 'git diff --name-only' as the input to the awk command).

Edit: worked nicely! I haven't used tabs much in vim so is a slightly new workflow but otherwise very handy

Re:Show HN: Deff – side-by-side Git diff review in your term... by devnonymous on Friday February 27, 2026 @05:12AM (#47178768)
> For me a bigger issue was git calling vimdiff for each file,

If you configure vimdiff as the difftool in your git config, just doing a `git diff` would show you the diff for each file sequentially.