Easily find issues by searching: #<Issue ID>
Example: #1832
Easily find members by searching in: <username>, <first name> and <last name>.
Example: Search smith, will return results smith and adamsmith
| Dev |
|
| QA |
|
| Priority | Low |
| Complexity | Unknown |
| Component | App - FluidShell - Command |
| Version | 12.0 |
The \fluidshell command should be treated as an Interactive command, therefor a corresponding error message should be displayed when calling \fluidshell from the Command Line (aka via runfluidscript-bundled.sh).
Fixed, SVN r27235; a message similar to the one shown below will be generated if \fluidshell is invoked from a script:
Script error on line N:
Interactive command can not be run in the batch mode: fluidshell
--- notes for developer ---
For command that can only run interactively, the constructor should pass a 'true' flag as the second argument to super(String, boolean). Shell will use this flag to check whether a command is allowed to run in a batch mode; the validation is done in BashShellNonInteractive.invoke(...). Note that this check is done at shell level, validation of command line arguments is not taken into consideration.
Verified using ADStudio 12 Dev 43.
Closed.
Verified using ADStudio 12 Dev 43.
Closed.
Issue #6905 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build trunk/27235 |
| No time estimate |
Fixed, SVN r27235; a message similar to the one shown below will be generated if \fluidshell is invoked from a script:
Script error on line N:
Interactive command can not be run in the batch mode: fluidshell
--- notes for developer ---
For command that can only run interactively, the constructor should pass a 'true' flag as the second argument to super(String, boolean). Shell will use this flag to check whether a command is allowed to run in a batch mode; the validation is done in BashShellNonInteractive.invoke(...). Note that this check is done at shell level, validation of command line arguments is not taken into consideration.