threads / discuss / 37471

Trailing whitespace on git diff output.

Subject: Trailing whitespace on git diff output.

## tl;dr

2 messages between Sep 1, 2014 and Sep 1, 2014.

replies: 1people: 2as markdown or json

Adria Farres· Sep 1, 2014, 17:47 UTC · lore
Hello,

Today, while redirecting git diff's output to a text file, I noticed git diff leaves a trailing whitespace between different deltas of the same file (the line that separates two different deltas). For example, committing a file with the following content: --- test

test ---

then changing it to the following: --- test test

test test ---

committing and diffing it, leaves a trailing whitespace on line 8 of the diff output.

Is that expected behavior? I'm using git 2.1.0.
Sorry for taking your time,
Adria
Matthieu Moy· Sep 1, 2014, 18:10 UTC · re: Adria Farres · lore

Re: Trailing whitespace on git diff output.

Adria Farres <14farresa@gmail.com> writes:
Show 23 quoted lines
> Hello,
>
> Today, while redirecting git diff's output to a text file, I noticed git diff
> leaves a trailing whitespace between different deltas of the same file (the line
> that separates two different deltas). For example, committing a file with the
> following content:
> ---
> test
>
> test
> ---
>
> then changing it to the following:
> ---
> test
> test
>
> test
> test
> ---
>
> committing and diffing it, leaves a trailing whitespace on line 8 of the
> diff output.
That is (I replaced spaces with _):
--- a/test.txt
+++ b/test.txt
@@ -1,3 +1,5 @@
_test
+test
_
_test
+test

GNU diff does the same, and that is what I would expect: the first
column is left for + and -, and spaces are used as a prefix for the
context.

If you diff

test
x
test

and

test
test
x
test
test

you'd expect a space before the 'x' in the diff output. In your example,
there's a space before the empty string, which has the same role as the
'x' above.
-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/

← back to recent threads