Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Deff – Side-by-side Git diff review in your terminal

github.com

Post reply on HN
Print view View original

51–60 of 74 posts

Re: Show HN: Deff – Side-by-side Git diff review in your terminal

#51

Post by anitil »

PhilipRoman wrote: post #40
flamestro wrote: post #28

Earlier quoted context omitted.

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!

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...

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 terminal

#54

Post by greatgib »

jaden wrote: post #45
greatgib wrote: post #36

It blows my mind that nowadays, some random tools on internet tells you to do "curl -fsSL https://.... | bash" to install some "binary" things and a lot of people will do it without hesitation. It probably explains why there is so many data leaks recently but it is like we did a 20 years jump back in time in terms of security in just a few years.

Is it that different from downloading and running a binary?

No, but who said that downloading and running a random binary found on internet is a good idea?

As I said, it's like being back 20 years back in the past.

Re: Show HN: Deff – Side-by-side Git diff review in your terminal

#56

Post by insane_dreamer »

flamestro wrote: post #33
insane_dreamer wrote: post #22

we need something like this in lazygit -- which is excellent all around but lacking in visual diffing/merging. What is most useful though is a 3-panel setup, like JetBrains -- still the best git client I have worked with.

What would the third panel contain in this case? Do you mean the setup that IntelliJ has in merge conflicts?

yes, it shows the final merge (what was accepted from the left and right panels); very handy

Re: Show HN: Deff – Side-by-side Git diff review in your terminal

#59

Post by ushironoko »

llbbdd wrote: post #7

I was looking for a good TUI tool for diffs recently, but I'm not sure yet if what I want exists already (and I don't think this tool does it (yet?)). I've been moving my workflow out of VSCode as I'm using TUI-driven coding agents more often lately but one thing I miss from my VSCode/GitHub workflow is the ability to provide a comment on lines or ranges in a diff to provide targeted feedback to the agent. Most diff…

[dead]

Re: Show HN: Deff – Side-by-side Git diff review in your terminal

#60

Post by Imustaskforhelp »

llbbdd wrote: post #35
kodomomo wrote: post #17

Earlier quoted context omitted.

Octo [0] for nvim lets you submit reviews, add comments on ranges, reply to threads, etc. This in conjunction with gh-dash [1] to launch a review can get you a pretty nice TUI review workflow. [0] https://github.com/pwntester/octo.nvim [1] https://github.com/dlvhdr/gh-dash *Edit: I see you meant providing feedback to an agent, not a PR. Well that's what I get for reading too fast.

No problem, I appreciate another reason to look at Neovim; I do sometimes have a need to interact with GH's actual PR flow and once I've moved the rest of my workflow out of VSCode, Neovim looks like the best option for the last mile of actually writing and editing code. I just have to commit the time to set it up with everything I probably take for granted in VSCode's editor.

Micro editor is a great choice as well imo but I don't think that micro has the thriving plugin ecosystem as compared to neovim but it is possible to make plugins for micro editor as well

https://github.com/micro-editor/plugin-channel

Link to Micro editor: https://micro-editor.github.io/

Post reply on HN