On Wed Nov 22 09:15:51 2023 +0000, Zebediah Figura wrote:
I'm confused about why "scripting" is a concern here. Do any scripts currently parse the *text* output, which is currently localized, and redundant with the return value anyway? Would changing that to MESSAGE actually keep compatibility in that case? I think it probably makes sense to keep console output for the sake of clear communication, but I don't understand why scripting.
As posted above, some native apps don't return error code (eg. see comments in regedit - didn't retest it though).
So scripts calling these apps want to keep output for at least let the user know (from reading the output) if something went wrong (see https://bugs.winehq.org/show_bug.cgi?id=55723). The concern of 'scripting' is more linked to keeping an output, rather than insuring that output has a given form (or defined structure to be parsed.
The idea was :
* keep an output (at least in case of error) to the Unix console * MESSAGE avoids reopening fd 1 as handle (at the cost of moving output from stdout to stderr), and also loses proper conversion to unix shell locale, hence the request to force English locale to have something always readable * if scripters want to parse output, they likely already force a given locale