After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 701661 - meld doesn't recognise end-of-line marker differences
meld doesn't recognise end-of-line marker differences
Status: RESOLVED DUPLICATE of bug 635593
Product: meld
Classification: Other
Component: filediff
unspecified
Other All
: Normal major
: ---
Assigned To: meld-maint
meld-maint
Depends on:
Blocks:
 
 
Reported: 2013-06-05 16:58 UTC by Christoph Anton Mitterer
Modified: 2013-06-06 21:59 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Christoph Anton Mitterer 2013-06-05 16:58:03 UTC
Hi.

It seems that meld doesn't recognise differences in end-of-line markers (i.e. CRLF vs. LF, etc.).

This can especially be critical, as there are files with mixed end-of-line markers, i.e. both, CRLF and LF.
meld will not notice these, but for other programs the semantics of the file might be completely different, e.g. when it detects the file to be CRLF (possibly based on the first few lines),... they might take single LFs in the middle as a "literal" character. (*)

Per default it should, and this should only be optionally ignorable.


With respect to adding an option that makes end-of-line marker differences ignorable,... there need to be two options (because of (*) above):
- one that ignores CRLF/LF differences only on a global base, i.e. only when _ALL_(!) occurrences of the EOL marker of the left file are replaced by the _SAME_(!) other EOL marker on the right file.... these diffs should be ignored.

- another that ignores any CRLF/LF differences,...

These two options resemble the what I told above about "mixed" EOL markers in the same file.


Cheers,
Chris.
Comment 1 Kai Willadsen 2013-06-06 21:59:50 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 635593 ***