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?
Was "terse" intended to mean "no gratuitous success/failure messages"
or was it intended to mean "easy to parse in a script"?