Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com To: jasonr AT gnu DOT org, ntemacs-users AT cs DOT washington DOT edu Cc: cygwin AT sourceware DOT cygnus DOT com Subject: Re: ediff falsely identifying a difference as white space only References: <200011300208 DOT VAA17667 AT fisher DOT stat DOT temple DOT edu> From: Bill Pringlemeir Date: 01 Dec 2000 09:35:18 -0500 In-Reply-To: Jason Rumney's message of "30 Nov 2000 20:48:44 +0000" Message-ID: Lines: 24 User-Agent: Gnus/5.0803 (Gnus v5.8.3) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii >>>>> "JR" == Jason Rumney writes: [snip] JR> option rather than using it blindly. This means that versions of JR> diff that do not understand the --binary option will still work JR> for some cases (in 20.7 they do not work at all), but you will JR> still need a version that understands the --binary option if you JR> want perfect bug free ediffing. But this seems to be untrue. The --binary option is equivalent to the `-q' option. This simply results in "Files %s and %s differ\n" message. Certainly this is not what ediff wants. Also, the newest version of `Ediff' does still contain the code that appends the --binary flags (if supported). How is this going to help things by passing the binary option? Or should `ignore_some_changes' be set so that this condition is false? Sorry, I am a little confused; perhaps I am missing something. However this doesn't seem like it will work to me. regards, Bill -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com