Show HN: Git Diff Viewer and Editor

Show HN: Git Diff Viewer and Editor(github.com)

2 points by r1chardnl 133 days ago | 2 comments

pvtmert 133 days ago |

I have couple of questions and suggestions;

Q1: Can this be a replacement/drop-in for $GIT_EDITOR?

Q2: On the issue ID #1, it is already mentioned but, can it use the existing $EDITOR / $VISUAL ?

Q3: Feature request / differentiating factor: Many similar tools exist, but if you can/could create a "snapshot" feature, that may be the killer factor here. As I see this is already a plain-C code, _tar_'ing `.git` directory and restoring after; essentially doing-bunch-of-things-but-cancelling-them-after use-case.

S1: Bit nit-picky but all strings are hard-coded within various places. Although it's easier to find where is something, will be difficult to translate for different languages.

S2: I think the title may need CLI/TUI in it. For some reason I expected yet-another Electron-based app. Maybe it's just me though...

S3: Adding to Homebrew (at least as a CASK even) should be relatively straightforward. As I (usually) don't want to manually maintain some binaries I downloaded from random-github-releases-link. Not to mention auto-updates are handled by the Brew.sh itself...

r1chardnl 133 days ago | |

A1: I don't think so now, but good idea. I haven't thought of it because well it depends entirely on how you interact with things. I tried many alternatives in the past from Magit to shell scripted vimdiff setups and now I usually just use VSCode or git from the CLI. I didn't want to open up another slow VSCode instance for every directory so this is mainly my motivation for making this. I just add an alias t='path/to/tuide' to .bash_aliases and type 't' in the repository I want to see.

A2: No it doesn't support that now. I did think of just having it be like a opionated visual git diff and using it in that way at first.

A3: Not sure. Couldn't you already do this with git reset and branches? I do have some features in mind to make some things easier like selecting multiple commits and then combining them for a rebase, but wait ah if that fails or something goes wrong the above snapshot feature might come in handy.

Thanks for the suggestions.