[bug #27983] Windows text mode mis-interpreted

[Eric Blake]

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
effect.

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:

  <http://savannah.gnu.org/bugs/?27983>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/