This might make it harder to know you haven't entered any typos, but (blindly) typing fg Enter should suffice (unless you have multiple jobs and the one in question isn't the most recent, in which case you will indeed need the job descriptor). If it is still outputting data (be it to standard output or standard error), it will certainly make your terminal visually cluttered, but all of that output will be ignored as it is not part of your input. Unless the job in question has components that are backgrounded (or the whole job is backgrounded, perhaps via kill -CONT), you shouldn't actually see output while it is suspended. The process outputs to stderr, so how shall I issue the command fg while the process is outputting to the terminal? The edit to this question asks about standard error: If you do not know the process ID and aren't worried about suspending other instances of the process by name, you can pass signals to one of these: killall -STOP program_nameĪ CONT signal to a program stopped with Ctrl+ z (and not bg'd) will resume its progress (in the foreground), the same as if you were to fg it. You can get the PID with pgrep …, or ps aux |grep … (or from the same shell, jobs -l, or $!) and you can then run: kill -STOP $PID # suspend You can still act on another process once you know its process ID (PID). If you're in a different shell instance (or a different user, sometimes including sudo commands), you likely won't be able to use job numbers. kill %1 rather than bg, and I certainly don't want to default to killing! (This logic also extends into why I no longer use this key binding: If I'm hammering on Ctrl+ z to stop a process, the last thing I want it to do is resume!) Non-interactive There's probably also a clever way to implicitly run bg upon suspending, but it seems unwise at least for me, the majority of my Ctrl+ z usage is because Ctrl+ c is failing to break out I want to follow that with e.g. In zsh, you can write a key binding to implicitly run fg from the prompt via another Ctrl+ z: _zsh_cli_fg()
bg will background the most recently suspended program.
Ctrl+ z will suspend the currently foregrounded program.It's in the POSIX standard, so even dash supports job control (when run interactively or with -m). This should be true of any shell with job control, which (for the most part) you can take for granted unless dealing with a truly ancient shell.
0 kommentar(er)
