On Mon, 14 Apr 2025, Bruno Haible via Cygwin wrote: > Especially since this commit modified select.cc, removing a comment > /* TODO: Buffer really full or non-Cygwin reader? */ > and here we are exactly in that case: a non-Cygwin process reading from > Cygwin's /dev/null.
That's Cygwin's select, it shouldn't have any bearing on what a non-Cygwin process sees. What I'm not getting is why ./something < /dev/null should be any different than doing in CMD something < NUL - I would hope there's not a pipe to Cygwin to deal with /dev/null but rather just a handle to Windows' NUL device... -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
