tmux and screen let you run different processes (e.g. vim, a bash script, mysql, psql, etc) in different virtual windows. But traditional Unix job control (using CTRL-z, fg, bg, and jobs) seem to give you some of the same functionality.Are there any advantages of multitasking using traditional job control over the newer ways via tmux and screen?
What are the virtues of multitasking with traditional job control vs Tmux/Screen?
gnu screen;tmux;job control
Suppose you've just started a program outside screen. Suddenly you realize you wanted to do something else in that terminal. Ctrl+Z.Screen and tmux introduce a layer of isolation between the application and the terminal. This isn't always a good thing. For example, I find their scrollback a lot less convenient than xterm's, so I rarely use screen unless I intend to (be able to) connect to that session remotely.If you've set up environment variables, a current directory and other parameters in a shell (which may be in a screen window), carrying those settings over to a new screen window can be a lot of work. It's convenient to be able to run several programs in that terminal.Sometimes you want to run a program in the background and have nothing to to with it any more: nohup program & disown %-.If you have a GUI application that occasionally misbehaves, it can be convenient to start it from a terminal and fg; Ctrl+C or kill %1 it if needed.Screen and tmux may not be installed.