2 ms·
One problem of course is that you miss the output of the process from before you took over control. Perhaps shells could be extended to better support this way
by amelius 4y ago
One problem of course is that you miss the output of the process from before you took over control. Perhaps shells could be extended to better support this way of using tmux/screen.
By the way another approach is of course to use VNC (e.g. some process started in an xterm at work you can access by opening your entire desktop at home.)
- linsomniac 4y agoDoesn't really feel like the shell would be the right place to do this, as the shell really has no idea, in most cases, of the output history. The whole idea of the scrollback is in the terminal, so it'd probably be, ultimately, the terminal that is the source of this information. kitty probably has some abilities to do this easily from the shell, as it has all sorts of abilities to interact programmatically with the scrollback history.
- amelius 4y agoGood point. How about starting tmux by default inside a terminal, rather than running the shell directly inside the terminal? Of course, an ssh session would also need to start tmux.
- deleted 4y ago[deleted]
- cbm-vic-20 4y agoThis sounds like something that mosh was built for. https://mosh.org/ https://mosh.org/
- freedomben 4y agoMosh helps of course by not killing the child process on timeout, but you'll miss all the console output without something like tmux
- cryptonector 4y agoNo need to `bg` the process. The `reptyr` tool should set it to run once it's gotten ptrace control over it.