On Sun, Jan 4, 2009 at 3:31 PM, Maciej Kazulak <kazulakm@...> wrote:

> The reason only the first command was executed can be that it returned a
> non-zero exit status. If you want to make sure every command gets a chance
> to execute, regardless of what the exit status of the previous one is,
> substitute '&&' with ';'. Check this out:
> box% false && echo "will not be echoed"
> box% false; echo "hello"
> hello
> box%
>
> That's how bash evaluates logic expressions. There's even a fancy word for
> it i think. Point is it will execute commands only to the point where it can
> determine the logic result. So above if the first element is false there's
> no need to execute echo as the logic result is already known to be false.

hehe, didn't think about using a ; that would work as well :-)
(but if you have A to Z, your command will be much longer than just
the for-loop in script 1)

BTW, you might want to output all to a file using >> "/home/Fred
Music/output.log" and view it using a "tail -f /path/file". Run
mp3gain quiet and grep the output.log file for errors/failures..