4 ms·
Why? How does syntax coloring help in this context? I don't use syntax coloring at all in my editor, I don't think it adds any information or clues that help me
by gregjor 2y ago
Why? How does syntax coloring help in this context? I don't use syntax coloring at all in my editor, I don't think it adds any information or clues that help me understand the code. I think colored diff output (beyond red for deleted and green for added) just adds distractions.
- lucasoshiro 2y agoDelta can show in the terminal a diff that looks like the GitHub one. You can compare side by side what was changed. It also highlight with more strength what changed inside the line. I installed it once, and never came back to the standard diff output. If Delta doesn't work like you expected and you want a standard diff output temporarily, no problem, you can run Git with git -c core.pager=less Note also that if you redirect the Git output, Git is smart enough to not call the pager (in this case, Delta) This is a case of personal taste. My only complaint about Delta is its name. Delta is already a concept in Git, and every time that I need to search about it is a pain... I search directly by "dandavision delta"
- gregjor 2y agoThat tells me what Delta does, but not why I might want syntax highlighting in the diff context. I want to quickly see the differences, not a kaleidoscope of colors. I normally use vimdiff and lazygit to see diffs. No syntax coloring.