Dave Korn writes: >Christopher Faylor wrote: >> >> Although, hmm, on rereading it isn't clear that the output shows up on >> the screen. It sounds like the DOS program just might not differentiate >> between stdout and stderr.
Yes the output (both stderr and stdout) appear on screen > I checked: you can't redirect its error output at all, even in a genuine >cmd.exe shell with cygwin having nothing to do with it. It must indeed be >using the console directly. <checks imports> Curiouser and curiouser... it >links msvcrt.dll and imports printf and wprintf, but then it goes and actually >does everything the hard way with lowlevel console i/o in unicode. How peculiar. Strange. What is meant then by this sentence included in the help: "SubInAcl error messages are sent to the Standard error." -- View this message in context: http://old.nabble.com/How-to-capture-stderr-of-dos-process-running-in-bash-shell---tp26341304p26354920.html Sent from the Cygwin list mailing list archive at Nabble.com. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple