On Fri Jul 18 09:04:29 2025 +0000, eric pouech wrote:
- each individual test can decide upon its input stream (<NUL, <CON,
echo "xyz" | ...); so there's no absolute need to bind cmd's std input to NUL 2) if cmd's input has to be changed, IMO it should be bound to console's input (as some builtin commands use stdin, other reopen the console; so that's a saner default). Didn't test it, but passing GetStdHandle(STD_INPUT_HANDLE) in CreateProcess instead could help. that will also force to adapt all the tests that read from stdin to explicitly define what input they're using
Technically true, but adding <nul to every find invocation whose args say don't read stdin would be ugly, confusing to future readers, and easy to forget in future find calls. I'd rather fix the root cause.
No opinion on nul vs caller's stdin; if you feel stdin is better, sure, let's do that. Needs a few additional <nul so date, time and choice don't get stuck waiting for user input, but that's probably an improvement anyways.