4 ms·
Why not just use mosh to establish & maintain the connection then then use tmux/screen to manage the terminal sessions?
by 0xADADA 10y ago
Why not just use mosh to establish & maintain the connection then then use tmux/screen to manage the terminal sessions?
- Camillo 10y agoBecause of: https://github.com/mobile-shell/mosh/issues/640 https://github.com/mobile-shell/mosh/issues/640
- hxegon 10y agoAlso wondering this. Why not both?
- mbrock 10y agoThat's what I do. My laptop moshes into a tmux. It's like I'm just always connected to my servers; the network is abstracted away. Mosh even has a very useful "7 seconds since connection dropped" message for when the café WiFi lags etc.
- geofft 10y agoYeah, this is what I use, and that's also the official recommendation for managing scrollback. https://github.com/mobile-shell/mosh/issues/122 https://github.com/mobile-shell/mosh/issues/122
- shirro 10y agoIt is practically necessary with mosh to run tmux/screen anyway because mosh removes scrollback. I find mosh adds little benefit for me most days and it makes a few things worse. mosh is a great idea and sometimes useful when you are changing connections or opening and closing a laptop all day but most days I think I am better off without it. Also I rarely have a remote connection open without forwarding some ports about so mosh often doesn't do what I need anyway. Unfortunately every layer of terminal emulation tends to filter out some terminal capabilities. It is a small thing but I like to be able to yank a selection out of a remote vim and paste it locally and last I saw mosh's terminal emulation eats the necessary control codes.