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 Usually? I've set a load of environment variables as I'm doing something and it's easier to background something that's running and run another command than to remember what I'd set.
It's absolutely a problem of my own making, and if job control didn't exist then I'd keep a dotfile up-to-date, but it does and I don't.
I've had the "no screen/tmux" etc. thing in the past where I'd SSH in somewhere, open an editor to change a config, ctrl+z, restart service, test, etc. - I just found the muscle memory of `ctrl+z, up, up, enter, ctrl+r resta, enter, <test>` loop really easy.
Again, making work for myself, but you know what it's like when you're in the middle of something- the most efficient way of working is whatever you've done a hundred times before.
Julia Evans
THRILLHO