Output on stderr and not using return values

RT Developers
1

I just started using the RT(v3.6.3) command line interface for scripting
purposes and was wondering why it doesn’t make use of return values at
all, means wether a command was successfully done or not can only be
recognized by comparing the output strings on /dev/stderr as it always
returns zero as returnvalue… this leads me directly to my second
question: why not using /dev/stdout for outputs instead? It took me
about one day to figure out why my string comparison didn’t work :frowning:

any ideas?

Regards

Patrick

2

I just started using the RT(v3.6.3) command line interface for scripting
purposes and was wondering why it doesn’t make use of return values at
all, means wether a command was successfully done or not can only be
recognized by comparing the output strings on /dev/stderr as it always
returns zero as returnvalue… this leads me directly to my second
question: why not using /dev/stdout for outputs instead? It took me
about one day to figure out why my string comparison didn’t work :frowning:

I’d love a patch to offer sane return values. As to why we’re using
STDERR rather than STDOUT, the best I can offer is to plead “historical
insanity”

Best,
Jesse