Don't display stack trace for cli parse failures
Just display the error message and exit. The stack trace isn't necessary (since it's likely user error) and is potentially confusing.
A
Asher committed
80b2d9481f4a04e1f139d08366532a66fb20dd5c
Parent: 0e2eaa9