I know in bash I can run one command after another by separating them by semicolons, like
$ command1; command2
Or if I only want command2
to run only if command1
succeeds, using &&
:
$ command1 && command2
This works, but if I suspend command1
using Ctrl-z
, in the first case, it runs command2
immediately, and in the second case, it doesn't run it at all. How can I run commands in sequence, but still be able to suspend the first command, but not have the second run until I have restarted it (with fg
) and it finishes? I'd prefer something as simple to type as possible, as I would like to do this interactively. Or maybe I just need to set an option somewhere.
By the way, what is the proper term for what Ctrl-z
does?
The following should do it:
Note the added parentheses.
In Bash, when you place a job into the background (using CTRL+Z or &) it does not wait for the job to finish, and gives an exit code of zero (success). That much you have observed, and it is documented in the
man
pages.The behaviour of logical "AND", &&, is that it tests from left-to right. Each part must be successful, so if the first is unsuccessful then the second will not run. So with && it runs commands from left to right until one of them fails. The definition of success is an exitcode ($?) of zero.
Contrast this with logical "OR", ||, which runs commands from left to right until one of them works.
Explaination of the subshell solution give by @NPE can also be found in the
man
pages:Compound commands and command sequences of the form ‘a ; b ; c’ are not handled gracefully when process suspension is attempted. When a process is stopped, the shell immediately executes the next command in the sequence. It suffices to place the sequence of commands between parentheses to force it into a subshell, which may be stopped as a unit.
The proper term for CTRL+Z is the suspend character, again from the
man
pages:Typing the suspend character (typically ^Z, Control-Z) while a process is running causes that process to be stopped and returns control to bash.
(Sorry to quote the
man
pages so much, but they really are your friends and worth reading)If you look at
stty -a
you will see something like this:So you can alter it, hence the phrase "typically". Don't do that though, it will confuse the heck out of everyone. The terminal driver raises a SIGTSTP signal which is trapped by Bash.