When working on a customer question, I noticed that "executing a set of commands sequentially with && operator" is not implemented correctly in FluidShell.
When executing a set of commands chained together using && operator, when a command execution failed, then subsequent commands should not be executed. In FulidShell, when executing a set of commands with && operator, all of commands get executed despite some of them failed.
Here is a simple case to reproduce the problem:
(1) Open a FluildShell.
(2) > cd any_directory_you_have_access
(3) > mkdir tmp_test
(4) > cd tmp_test
(5) > date && cd xxx && date && cd xxx && date
where > is FluidShell prompt
At step (5), there are 5 commands to be executed, 3 'date' commands and 2 'cd xxx' commands. In UNIX environment, only the first 2 commands will get executed, i.e. the first 'date' command and the first 'cd xxx' command. Since directory xxx does not exist, hence, the first 'cd xxx' command will fail and subsequent commands will not be executed. In FluidShell, all of 5 commands will get executed, this is incorrect. Please see this attachment.
|
34 KB
We have not have any support calls on this behavior, so I am not sure if customers are either not annoyed by this enough or that they are "liking" this behavior? Thus we probably should wait for some complaints before fixing this in case customers are liking the current behavior.
Issue #15445 |
New |
Completion |
No due date |
No fixed build |
No time estimate |
We have not have any support calls on this behavior, so I am not sure if customers are either not annoyed by this enough or that they are "liking" this behavior? Thus we probably should wait for some complaints before fixing this in case customers are liking the current behavior.