bin/ldiff doesn't always output the correct output #6

Open
halostatue opened this Issue Aug 27, 2011 · 2 comments

1 participant

@halostatue
Owner

With files aX (containing aX\n) and bXaX (containing bXaX\n), the output of bin/ldiff does not match that of GNU diff.

With bin/ldiff aX bXaX:


1c1
< aX
---
> bXaX

With diff aX bXaX:

1c1
< aX
---
> bXaX

Note the extra blank lines.

The same applies with bin/ldiff -u aX bXaX:

--- aX  2011-08-27 09:36:12 -0400
+++ bXaX    2011-08-27 09:36:18 -0400

@@ -1,2 +1,2 @@
-aX
+bXaX

versus:

--- aX  2011-08-27 09:36:12.000000000 -0400
+++ bXaX    2011-08-27 09:36:18.000000000 -0400
@@ -1 +1 @@
-aX
+bXaX
@halostatue
Owner

The fact that bin/ldiff -u sees the files as having two lines is likely a hint that points to the possible problem seen in Issue 2.

@halostatue
Owner

This has mostly improved. The output from bin/ldiff aX bXaX:

1c1
< aX
---
> bXaX

Unified diffs are 100% better:

--- aX  2013-02-09 10:43:26.000000000 -0500
+++ bX  2013-02-09 10:43:34.000000000 -0500
@@ -1,2 +1,2 @@
-aX
+bXaX

Context diffs (not shown previously) are also correctly identical.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment