poll: when you're using your shell **interactively**, do you ever use its job control features (ctrl+z, fg, bg, `jobs`, `wait`, etc?)
(other than maybe occasionally backgrounding a process with &)
poll: when you're using your shell **interactively**, do you ever use its job control features (ctrl+z, fg, bg, `jobs`, `wait`, etc?)
(other than maybe occasionally backgrounding a process with &)
I'm also curious about reasons folks are using job control instead of opening a new tab in their terminal/tmux/screen
so far we have:
* use ctrl+z to suspend a CPU-hungry program because you need to use the CPU for something else
* you're in a situation with no screen/tmux/fancy terminal
* background a GUI app so it's not taking up a terminal tab
* accidentally started a long-running job without tmux/screen
* already set up a lot of environment variables
* accidentally ran ctrl+z
(2/?)
@b0rk At my company they don't allow terminal/tmux etc so you have to use bg/nohup/& if you want to start a long running job and be able disconnect your session.
As an aside I've found a way around the tmux ban by compiling a version to run out of my home directory which has been working fairly well.