http://bugs.winehq.org/show_bug.cgi?id=58745
--- Comment #2 from Robin Haberkorn rhaberkorn@fmsbw.de --- (In reply to Eric Pouech from comment #1)
- if it's run from a unix shell, then the pipe used in a unix one, which is
imported inside wine, but which doesn't have all the Win32 semantics (like shown here with PeekNamedPipe); and I'm not sure it's something we want to or can improve
If I run the `echo TEST | ./peeknamedpipe.exe` in an MSYS shell under Windows 10, ie. a bash ported to Windows, I get exactly the same output as under cmd.exe. Effectively you can have a console application reading from stdin that works correctly in MSYS under Windows, but won't run correctly on a FreeBSD shell (be it bash) with Wine, e.g. in a quasi-msys2 [1] environment. Which is exactly how I noticed the difference in behavior.
But if you say it can't be fixed in Wine the glib people would be willing to add a workaround. They want a clear statement, though.
I suppose the only workaround for now would be using temporary files everywhere this causes problems. (I do not have infinite streams luckily.)
[1]: https://github.com/HolyBlackCat/quasi-msys2