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
There seems to be some inconsistencies regarding when the initialization script is executed and when not if using the Command mode FluidShell.
For instance, let's say we have the file script.txt containing echo FILE,
and in ADStudio let's add the following initialization script (from File > Options > FluidShell > Script): echo INIT.
Now we have the below cases:
1. calling from the Unix Terminal ./runfluidscript-bundled.sh -fscript.txt and
having enabled "Execute Script for all Shells"
will print
echo FILE
FILE
2. calling from the Unix Terminal ./runfluidscript-bundled.sh -fscript.txt and
having disabled "Execute Script for all Shells"
will print the same as 1 above.
3. calling from the Unix Terminal ./runfluidscript-bundled.sh -fscript.txt -cMY-SERVER and
having enabled "Execute Script for all Shells"
will print
echo INIT
INIT
echo FILE
FILE
4. calling from the Unix Terminal ./runfluidscript-bundled.sh -fscript.txt -cMY-SERVER and
having disabled "Execute Script for all Shells"
will print as 1 & 2 above.
Should the Initialization Script ever run in Command mode? Additionally should it respect the GUI option "Execute Script for all Shells"?
Command line should respect the option "Execute Script for all Shells". Ivan missed this in SVN #29891.
Fixed. SVN r29932.
Fixed. SVN r29932.
Verified using ADStudio 12.0.3.
For each case the following happens:
* 1. both INIT and FILE messages are printed<---OK
* 2. only FILE message is printed<---NOT OK, the INIT message is not displayed
* 3. INIT message is printed two times, followed by FILE message<---NOT OK, the INIT message should be printed only once
* 4. only FILE message is printed<---OK
For cases 1 & 2 the INIT message should appear because they are about opening a shell without a server connection.
For case 3 the INIT message should appear because the "Execute Script for all Shells" option is enabled, even if the server connection is specified.
For case 4 the INIT message should not appear as the "Execute Script for all Shells" option is disabled and there is a server connection specified.
Verified using ADStudio 12.0.3.
For each case the following happens:
* 1. both INIT and FILE messages are printed<---OK
* 2. only FILE message is printed<---NOT OK, the INIT message is not displayed
* 3. INIT message is printed two times, followed by FILE message<---NOT OK, the INIT message should be printed only once
* 4. only FILE message is printed<---OK
For cases 1 & 2 the INIT message should appear because they are about opening a shell without a server connection.
For case 3 the INIT message should appear because the "Execute Script for all Shells" option is enabled, even if the server connection is specified.
For case 4 the INIT message should not appear as the "Execute Script for all Shells" option is disabled and there is a server connection specified.
All of 4 test cases should work now. SVN r29959.
All of 4 test cases should work now. SVN r29959.
Verified using ADStudio 12.0.4.
All 4 cases are working fine now.
Found an inconsistency regarding command echoing from the Init Script, added as #7905 - Echoing (or not) commands from the Init Script in Batch mode.
Closed.
Verified using ADStudio 12.0.4.
All 4 cases are working fine now.
Found an inconsistency regarding command echoing from the Init Script, added as #7905 - Echoing (or not) commands from the Init Script in Batch mode.
Closed.
Issue #7859 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| No fixed build |
| No time estimate |
1 issue link |
relates to #7847
Issue #7847Add option File->Options->FluidShell->Script Options->[Execute Script for all Servers] |
Command line should respect the option "Execute Script for all Shells". Ivan missed this in SVN #29891.