Affects Version/s: 14.0.0, 14.5.1, 6.0.0, 22.214.171.124, 126.96.36.199, 7.0.0
Fix Version/s: None
Support Ticket IDs:
Using Amster by loading an Amster Script (.amster file) when triggered from the command line (e.g. amster install.amster) upon finishing the script remains within the amster CLI.
This means that scripts which use amster part-way through will not continue to execute instructions after amster, unless the amster script itself explicitly exits at the end of it (e.g. by having :q as the final line of each script).
Suggested that we change amster such that when activated from the command-line with a script as a parameter, after execution it exits with a status code indicating successful execution (0) of the script of unsuccessful (1) so that scripts can use this amster functionality appropriately.
This would avoid having to include :q at the end of each amster script file, and allow scripts that use Amster to branch depending on this status code (e.g. using && to continue running further commands on the CLI)
Steps to Reproduce
Create a script, e.g. install.amster :
Run with amster /path/to/install.amster
Current Output: (leaves the Amster prompt open)
In the case of an incorrectly-written amster file, or the operation fails, e.g:
Create bad_install.amster: (note the typo in acceptLicense)
Run with amster /path/to/bad_install.amster