As the top commenter said, the problems do not end with choosing a good editor and fixing its display methodology. Git and many other VCSs create noisy diffs whenever space is added and forgotten, which ultimately complicates the life of developers that want to review changes.
Even if your editor were able to make display diffs in a clean way, you would still have a dirty history when for instance using less/more or other tools (not to mention the merging issues problem).
Git and many other VCSs create noisy diffs whenever space is added and forgotten, which ultimately complicates the life of developers that want to review changes.
That's because Git is stupidly opinionated about end-of-line whitespace, having been written by .... Linus.
Comments
Who cares? Get a decent editor that doesn't give a crap if there's invisible whitespace at the end of a line.
As the top commenter said, the problems do not end with choosing a good editor and fixing its display methodology. Git and many other VCSs create noisy diffs whenever space is added and forgotten, which ultimately complicates the life of developers that want to review changes. Even if your editor were able to make display diffs in a clean way, you would still have a dirty history when for instance using less/more or other tools (not to mention the merging issues problem).
That's because Git is stupidly opinionated about end-of-line whitespace, having been written by .... Linus.
Right, but that's only half of the robustness principle.
or run perl -e s/(.*)\s+$/$1/g