Live data from Hacker News

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

github.com

31–40 of 74 posts

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

#33

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?

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

#34
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…

I was also searching for some time, but most of them did not have enough context for my workflow tbh. So thats why I decided to make deff. Another good one I liked is vimdiff

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

#35
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…

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.

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

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

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

#37

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.

I get the hesitation :D But the code is open and the install.sh is as minimal as it gets tbh. Still, as said, I get the hesitation. What a time to be alive.

It does not install binaries, it builds the binary by checking out the project basically. You can also do the process manually and use the tool.

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

#38
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…

I had tried `delta` a few years ago but eventually went with `diff-so-fancy`[1]

The two are kind of similar if I remember correctly, and both offer a lot of config options to change the style and more. I mostly use it for diffs involving long lines since it highlights changes within a line, which makes it easier to spot such edits.

I have an alias set in `~/.gitconfig` to pipe the output of `git diff` (with options) to `diff-so-fancy` with `git diffs`:

    diffs = "!f() { git diff $@ | diff-so-fancy; }; f"

[1] https://github.com/so-fancy/diff-so-fancy

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

#39
post #25
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…

Not TUI based but I made something called meatcheck. The idea being that the LLM requests a review from the human, you can leave inline comments like a PR review. Once you submit it outputs to stdout and the agent reads your comments and actions them. https://github.com/jfyne/meatcheck

Thank you! At a glance this is very close to what I had in mind, especially with the straightforward output format, I'll give this a try.

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

#40
post #5

git difftool --tool=vimdiff

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

Post reply on HN