delta

Thanks! https://github.com/dandavison/delta/pull/1893 > To automatically display the light or dark version of images depending on their gh theme Ah, good call. That could be a nice improvement -- creating light and dark versions of the screenshots with switching as you describe.

If you read the comments, you’ll find https://github.com/dandavison/delta/pull/1746 which adds the option I mentioned, which limits the length of syntax highlighting, but still has a rather low limit on maximum (unhighlighted) line length :)

Delta is great for what it does, but I consistently hit an issue where it truncates long lines. This post inspired me to check if the situation had changed... and it has! Now if you set `git config --global --replace-all delta.max-line-length 0`, it will no longer truncate lines. It's unclear to me why this is not the default. Discussion about the change is in https://github.com/dandavison/delta/pull/290.

As someone who also uses Git exclusively from the command line, without any TUI wrappers, I agree with a lot of this. The parts about commits being revertable, bisectable and in general _atomic_ are very important, and IME the only correct way of using version control. One exception: conventional commits. I find them very useful even on solo projects, since a) they make it easy to spot the type of change at a glance, and b) they force me to keep commits atomic. That is, if I'm ever compelled to make a commit that is both a `fix` and a `refactor`, usually out of laziness :), sticking to a conventional commit message is a quick way to determine what needs to be split into a different commit. These conventions really shine when used in a team, as they improve communication and keep the history tidy (along with all other benefits of atomic co

- https://github.com/dandavison/delta is nice for a prettier presentation of the same information as `git diff`. - This may or may not qualify, since I think GNU diff supports it with an option, as does Git diff, but "Color-words" diff can be nice, where changes in the middle of the line are highlighted and whitespace is ignored. - Somebody already recommended https://github.com/Wilfred/difftastic, which I second. It uses treesitter and is very interesting. Surprisingly, in practice difftastic is not always noticeably better than color words diff (don't expect miracles), but occasionally it is much better. For the last two, see Difftastic's FAQ, https://github.com/Wilfred/difftastic#isnt-this-basically---... Update: Finally, this blog post about difftastic describes some details: https://www.wilfred.me.uk/blog/2022/09/06/difftastic-the-f

`git blame` lets you identify the commit that changed the line you’re looking for, but doesn’t make it easy to then view further details. The author might prefer GitHub’s blame view because it has these features: • each hunk has a link to the commit that changed it, as opposed to needing to copy a line’s SHA and then run a new `git show …` command • each hunk has a link to view the `blame` as of that older commit, as opposed to needing to copy a line’s SHA and then run a new `git blame … path/to/same/file` command • the code is syntax highlighted by default, without you needing to configure your local Git install to use https://github.com/dandavison/delta These features lead to a better experience than `git blame`. Various IDEs, editor plugins, TUIs, and GUIs provide similar features.

Delta is a drop in replacement with git diffs. Why is this not possible with difftastic? I.e it suggests to create aliases etc https://github.com/dandavison/delta

No, I don't think delta integrates with difftastic: https://github.com/dandavison/delta/issues/535

Nice tool. Also relevant: https://github.com/dandavison/delta

My personal favorite additions to my git config are using delta[1] as my pager for much more readable and syntax highlighted diffs. And adding the following alias, which means I no can always check out to the default branch of the repo, no matter if it's called master/main/develop/whatever [alias] checkout-default = "!git checkout $(git rev-parse --abbrev-ref origin/HEAD | sed 's@^origin/@@')" [1] https://github.com/dandavison/delta

Thanks for the difftastic & zoxide tips! However, I've been using this git pager/difftool: https://github.com/dandavison/delta While it's not structural like difft, it does produce more readable output for me (at least when scrolling fast through git log -p /scanning quickly)