Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Wed, 29 Nov 2000 21:08:26 -0500 (EST)
From: "Richard M. Heiberger" <rmh AT fisher DOT stat DOT temple DOT edu>
Message-Id: <200011300208.VAA17667@fisher.stat.temple.edu>
To: ntemacs-users AT cs DOT washington DOT edu, cygwin AT sourceware DOT cygnus DOT com,
        Chuck DOT Irvine AT mail DOT sprint DOT com
Subject: Re:  ediff falsely identifying a difference as white space
    only

This looks (again) like an issue that I raised some time ago (6-12
months?).  ediff and ediff-3 were misbehaving with dos and mac line
endings.  A fix was installed (ntemacs 20.6 ?) that worked correctly
on NTemacs but not on other systems.  The fix reinvented something
that was done differently in the development tree leading to emacs 21.
There was some discussion among the developers about the best way to
handle the line endings.  I remember that there was an issue about how
to handle the --binary issue.  It was supposed to be sensitive to
whether the diff program could use that argument.

The current discussion makes me think the alternate solutions were not
completely reconciled.

Rich

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com