[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, 12 Apr 2010 21:13:35 +0000
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20100330 Fedora/3.5.9-2.fc12 Firefox/3.5.9

Follow-up Comment #11, bug #27983 (project findutils):

I have no qualms with using 'b' - on a POSIX system it has no effect, but we
know that on non-POSIX systems, it is standardized by C99 and has a beneficial

But I am adamantly opposed to using 't' - it is not specified by any
standard, and creates more problems than it solves.

If you have complaints about how cygwin handles newlines, take it up on the
cygwin list, not here.  I have no plans on fixing it upstream in findutils,
since it is not an upstream findutils issue.  But since it affects cygwin
users, you may find more agreement on the cygwin list, or better ways to
accomplish what you are trying to do by patching xargs.  And I disagree with
your statement that cygwin apps cannot rely on POSIX compliance of the system
features they consume - if you use only cygwin apps and binary mount points
(which is the only environment where cygwin makes promises of POSIX
compliance, anyways), then there is no problem.  And if you use anything else,
then you only have to isolate the differences at the boundaries, as with the
d2u trick.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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