Corina wrote: > In the Linux kernel there's some magic > going on which we can't reproduce in Cygwin so far. Trying to open > an existing pipe for writing or reading opens apparently exactly the > right end of the pipe under Linux. On Windows, you only get the exact > end of the pipe which is already available to the current process. That's > the read side of the pipe, AFAICS, and that doesn't allow writing. This > explains the "Permission denied".
Interesting. Looking in function process_substitute in subst.c, I can see that bash tries to swap ends of the pipe depending on whether its a >(cmd) or a <(cmd) substitution. Lev -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/