[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #27983] Windows text mode mis-interpreted

From: Eric Blake
Subject: [bug #27983] Windows text mode mis-interpreted
Date: Mon, 05 Apr 2010 12:45:58 +0000
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20100330 Fedora/3.5.9-1.fc12 Firefox/3.5.9

Update of bug #27983 (project findutils):

                  Status:                    None => Wont Fix               
             Assigned to:                    None => ericb                  


Follow-up Comment #2:

Cygwin does provide the ability to request explicit text-mode processing, but
it is almost always a bug to use it.  For example, it is possible to name
files with an explicit trailing carriage return; blindly using text mode would
make it impossible to process these files through xargs.  Rather, programs
should trust that for text files, plain "r" will do the right thing given the
underlying mount point.  Input through a pipe from a cygwin process will
already be in binary mode and not have spurious carriage returns.  And if you
are using input from a non-cygwin program, then you can simply add another
process in the pipeline, and pass your data through d2u, rather than having to
patch every other application to have to care about the differences.

As maintainer of the cygwin port of findutils, I don't think that this should
be changed in findutils.

Meanwhile, I don't see what your complaint is about the xfreopen wrapper; but
if you think there is a bug with it, you should report it to the gnulib list. 
POSIX requires that freopen return either NULL on failure, or the original
file argument on success - there is no implementation that returns a different
file than what you pass in.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]