Jane Young wrote on 06/25/2010 06:19 PM:
> Bill Shannon wrote:
>> Jane Young wrote on 06/25/10 05:15 PM:
>>> In v2, if the command fails and if terse=true, then it just displays:
>>> "Command failed" and exits with a non-zero exit code
>>> If terse=false, then it displays the exception message
>>> (e.getLocalizedMessage())) from the server side.
>>> All the commands in v2 has the --terse option, similar to --echo option.
>>> The purpose of terse option is for CLI scripting where users wants a
>>> terse output.
>>
>> Right, but do you think that was intended to apply only to the
>> success/failure message? Or was that intended to apply to all
>> other forms of output from the command?
> It was intended to all other forms of output from the command, not just
> success/failure message.
> Unfortunately it turned out to be that way... :-(
>>
>> Was "terse" intended to mean "no gratuitous success/failure messages"
>> or was it intended to mean "easy to parse in a script"?
>>
> Intended for easy parsing in the script.
Maybe I'm alone, but I *hate* the success/failure messages, which
seem completely gratuitous, so I always set AS_ADMIN_TERSE=true in
my environment. I'm not sure I want it to effect all the other
output, turning it from human readable to script parsable.
Anyone else?