[MinGW-notify] [ mingw-Bugs-1793180 ] Strange behaviour in command pipeline

[SF/projects/mingw n. l. <min...@li...>]

Bugs item #1793180, was opened at 2007-09-12 07:30
Message generated for change (Settings changed) made by earnie
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=102435&aid=1793180&group_id=2435

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: MSYS
>Group: Aged issue
>Status: Pending
Resolution: None
Priority: 1
Private: No
Submitted By: Keith Marshall (keithmarshall)
Assigned to: Cesar Strauss (cstrauss)
Summary: Strange behaviour in command pipeline

Initial Comment:
I've only ever noticed this in the particular circumstances described here: https://sourceforge.net/tracker/?func=detail&atid=379173&aid=1792340&group_id=23617

It seems to be explicit to the GnuWin32 pnmtopng.exe reading data from a pipe, invoked from MSYS.  All appears hunky-dory, when run natively in cmd.exe, so they may dismiss it as an MSYS bug.  In MSYS, what is the difference between

  pnmtopng < foo.pnm > foo.png

which works, and

  cat foo.pnm | pnmtopng > foo.png

which doesn't?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=102435&aid=1793180&group_id=2435