Earlier quoted context omitted.
But if you're running tmux then the "never get disconnected or lose terminal sessions" of mosh goes from major feature to minor feature.
You should anyway run mosh+tmux. Not sure about this though, ssh still disconnects and you have to reconnect and then launch tmux attach again. I agree it doesn’t seem like much, but just opening any device and continue from where you left off without any extra interaction feels great. It is kinda like auto save on iOS, you could argue that pressing the save and open button isn’t that big of a deal, but once you expe…
Mosh
61–70 of 152 posts
Re: Mosh
#62Re: Mosh
#63Earlier quoted context omitted.
> one trick i use is to change the tmux command key to be something different on each nesting level. This is exactly the difficulty I never want to see...
If you just want a persistent connection, you never have to press the command key or even acknowledge it exists, do you? And you didn't answer what difficulties you've personally faced.
And I what I said that the problem was the moment I have to have different tmux config for every machine, just like she/he is doing.
Re: Mosh
#64As someone who codes on a remote server the whole day, mosh is absolutely necessary and it is fantastic Advantages: - you dont see any lag when you type, it is exactly as if you were on your local machine - when network disconnect, the terminal freeze and when network is up again, the terminal becomes interactive again preserving everything in between - connection is preserved as long as the terminal is open, so even…
Why do you code on a remote server?
Re: Mosh
#65If you spend any time using a terminal to remotely manage servers, it's worth using at least tmux (and mosh because it provides a better experience with imperfect connections).
Re: Mosh
#66Earlier quoted context omitted.
If you just want a persistent connection, you never have to press the command key or even acknowledge it exists, do you? And you didn't answer what difficulties you've personally faced.
If I just want a persistent connection, then the nested tmux that takes 2+ useless lines in the bottom already falls into the "it doesn't work well" category. And I what I said that the problem was the moment I have to have different tmux config for every machine, just like she/he is doing.
And when you're setting up a server it's easy to turn off the tmux status bar.
Re: Mosh
#67You need to install a server in the server for this to work. That is, if you are using SSH to log in to server farms as a "user" (as opposed to a server farm admin), then you cannot just "use mosh".
When I first found out about mosh, I imagined it would work seamlessly even with servers that don’t have the mosh server installed by auto-installing itself. If mosh could do this, I would `alias ssh=mosh` and use it all the time. Otherwise I need to remember which servers have mosh installed, and for those that don’t I need to ssh in, apt-get mosh, disconnect, and reconnect with mosh. I’d imagine it could either jus…
Re: Mosh
#68Earlier quoted context omitted.
I sometimes use Prompt with the on-screen keyboard when I'm working out on a treadmill. It's neither pleasant nor productive, but it's okay. Btw, tmux scrollback sucks except when the terminal emulator's native scrollback is supported through control mode.
May I ask, why do you keep using Prompt? Full disclosure, I’m one of Blink Shell devs.
Re: Mosh
#69Earlier quoted context omitted.
Why do you code on a remote server?
I'm creating a PoC (well more the MVP of a company) and this includes a scrapper which requires a very reliable connection, which I don't have locally
Re: Mosh
#70Earlier quoted context omitted.
I'm creating a PoC (well more the MVP of a company) and this includes a scrapper which requires a very reliable connection, which I don't have locally
There are solutions to mount the remote filesystem locally and use any regular code editor