[bug #27983] Windows text mode mis-interpreted

2011-05-11 Thread James Youngman
Update of bug #27983 (project findutils): Open/Closed:Open => Closed ___ Reply to this item at: ___ M

[bug #27983] Windows text mode mis-interpreted

2010-04-12 Thread 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

[bug #27983] Windows text mode mis-interpreted

2010-04-12 Thread Ilguiz Latypov
Follow-up Comment #10, bug #27983 (project findutils): > Cygwin cannot be POSIX-compliant I meant "Cygwin applications cannot rely on POSIX compliance of the system features they consume". ___ Reply to this item at:

[bug #27983] Windows text mode mis-interpreted

2010-04-12 Thread Ilguiz Latypov
Follow-up Comment #9, bug #27983 (project findutils): > app | d2u | xargs > That is a one-size-fits-all solution - it works no matter the windows app on the left and no matter the consumer on the right. This means that the developers should be aware about the newline subtlety that may be expose

[bug #27983] Windows text mode mis-interpreted

2010-04-12 Thread Eric Blake
Follow-up Comment #8, bug #27983 (project findutils): If you really want xargs to handle data from a native windows application, then add d2u into the pipeline: app | d2u | xargs That is a one-size-fits-all solution - it works no matter the windows app on the left and no matter the consumer on

[bug #27983] Windows text mode mis-interpreted

2010-04-09 Thread Ilguiz Latypov
Follow-up Comment #7, bug #27983 (project findutils): xargs may receive input not just from a text-mode-mounted file but also from a Windows native application. So I thought that being liberal on input was good and gave the "t" hint to Cygwin DLL in my added freopen(). In the case of "-d X" or

[bug #27983] Windows text mode mis-interpreted

2010-04-09 Thread Eric Blake
Follow-up Comment #6, bug #27983 (project findutils): In the POSIX world, fopen() with 'b' has no effect, but with 't' has undefined behavior ('t' happens to be a cygwin extension, and you have no business trying to use it in an application trying to be portable to POSIX). I still argue that the

[bug #27983] Windows text mode mis-interpreted

2010-04-08 Thread Ilguiz Latypov
Follow-up Comment #5, bug #27983 (project findutils): > Then you use cat, which preserves binary mode, through a pipe which also preserves binary mode. But this is a valid sequence of commands, and Cygwin should preserve the behavior of this sequence regardless of the input's low-level line end

[bug #27983] Windows text mode mis-interpreted

2010-04-05 Thread Eric Blake
Follow-up Comment #4, bug #27983 (project findutils): In your example, $tf1 is created in text mode, so it contains file names listed with carriage returns. Then you use cat, which preserves binary mode, through a pipe which also preserves binary mode. But this is an example of a useless use of

[bug #27983] Windows text mode mis-interpreted

2010-04-05 Thread Ilguiz Latypov
Follow-up Comment #3, bug #27983 (project findutils): Is the expectation in the test script valid? > mount -t "$(cygpath -w "${dir}")" /textmode [..] > tf1="/textmode/file1.txt" > tf2="/textmode/file2.txt" [..] > echo "foo" > "${tf1}" > echo "bar" >> "${tf1}" [..] > cat "${tf1}" | xargs -i echo

[bug #27983] Windows text mode mis-interpreted

2010-04-05 Thread Eric Blake
Update of bug #27983 (project findutils): Status:None => Wont Fix Assigned to:None => ericb ___ Follow-up Comment #2: Cygwin does prov

[bug #27983] Windows text mode mis-interpreted

2009-11-16 Thread Ilguiz Latypov
Follow-up Comment #1, bug #27983 (project findutils): Correction of my phrase on the extra file entity, One has to explicitly set it with the "r" vs. "rb" (O_BINARY) open mode. There is no explicit text mode setting. The "r" mode is the default and will be interpreted by the emulation layer

[bug #27983] Windows text mode mis-interpreted

2009-11-10 Thread Ilguiz Latypov
Additional Item Attachment, bug #27983 (project findutils): File name: text-mode.sh Size:2 KB ___ Reply to this item at: ___ Message

[bug #27983] Windows text mode mis-interpreted

2009-11-09 Thread Ilguiz Latypov
Additional Item Attachment, bug #27983 (project findutils): File name: text-mode.sh Size:2 KB ___ Reply to this item at: ___ Message

[bug #27983] Windows text mode mis-interpreted

2009-11-09 Thread Ilguiz Latypov
URL: Summary: Windows text mode mis-interpreted Project: findutils Submitted by: ilgiz Submitted on: Mon 09 Nov 2009 11:04:14 PM EST Category: xargs Severity: 3 - Norm