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/?)
Often: ctrl+z to see what is running on that terminal, exactly. Particularly useful for programs that run over many hours or days.
'screen' is very useful – it's a default for me. But often launched programs are GUI-based in some way, and I need to see with how much RAM I launched them, and what exact parameters.