On Sat, 7 Dec 2013, Daniel Barnes wrote:
> There's a few issues with this that causes this behavior:
>
> The way "or" works, it waits until the first command has been executed, then
> moves on to the second. The "if" only seems to be taking the first command,
> and the "or" is actually being execu
On Sat, 7 Dec 2013, Nick Mapsy wrote:
> Hi, I'm trying to figure out how to combine multiple commands in a
> conditional with boolean operators, but I must be missing something.
>
> I thought this is how "or" is meant to be used, but this gives "no" as the
> output:
> if false; or true
> echo ye
There's a few issues with this that causes this behavior:
The way "or" works, it waits until the first command has been executed,
then moves on to the second. The "if" only seems to be taking the first
command, and the "or" is actually being executed inside the block:
if false;
or true;
e
Hi, I'm trying to figure out how to combine multiple commands in a
conditional with boolean operators, but I must be missing something.
I thought this is how "or" is meant to be used, but this gives "no" as the
output:
if false; or true
echo yes
else
echo no
end
If this is wrong, what is the
