https://bugs.winehq.org/show_bug.cgi?id=56459
--- Comment #12 from Eric Pouech eric.pouech@gmail.com --- (In reply to renatopereyra from comment #11)
We could think of "nicer" way of doing it (eg. env variable not to bind to unix console when set, or small shell script to wrap that up...)
I think an env var would be optimal and even better if the behavior of the env var is tested.
The wrapper script can be a temporary solution.
I'll see what we can push upstream (actually, I think there are already too many env variables for Wine, so I would not favor that one, but let's see maintainers' stance) whatever the solution, it'll be hard to automate the testings as none of the tests are run attached to a unix console, and even less able to generate input or read output to that console (this is doable - if have locally bits of this -, but would require a lot of new stuff upstream, that are likely not to be approved) But if someone wants to create its own testbed, go ahead
console is unbuffered
Are you confirming that this is how Windows consoles (and therefore wineconsole) should behave?
yes
to check your claim this you need to intertwin write:s to stdout and stderr.
... Or are you asking me to confirm my observations?
no, I've done it already. I'm just saying that your program (as you sent it) cannot test that claim.
--- Comment #13 from renatopereyra@google.com ---
I'll see what we can push upstream (actually, I think there are already too many env variables for Wine, so I would not favor that one, but let's see maintainers' stance) whatever the solution, it'll be hard to automate the testings as none of the tests are run attached to a unix console, and even less able to generate input or read output to that console (this is doable - if have locally bits of this -, but would require a lot of new stuff upstream, that are likely not to be approved) But if someone wants to create its own testbed, go ahead
Thanks! I appreciate this. Please let me know what, if anything, can be added upstream.
no, I've done it already. I'm just saying that your program (as you sent it) cannot test that claim.
Ah, yes, I see your point now. Thanks for clarifying.