Mosh

Post by MereInterest » Wed, Apr 08, 2020, 5:28 PM UTC

alexhutcheson wrote: post #98

MereInterest wrote: post #83

Earlier quoted context omitted.

Oh absolutely. I like using tramp to edit individual config files remotely. If there is one particular data acquisition computer that is performing incorrectly, I can quickly open up that file to compare, without needing to leave the editor. The issue I ran into with editing code through tramp is the integration with make. I use `M-x compile` to compile from emacs, with a few modifications to find the appropriate mak…

If you are in a buffer for a remote file, then M-x compile should run make on the remote machine. Docs are here: https://www.gnu.org/software/tramp/#index-compile

Post by acoard » Wed, Apr 08, 2020, 5:44 PM UTC

mbreese wrote: post #97

jasonpeacock wrote: post #87

Earlier quoted context omitted.

But you do see lag - if you have auto/tab-complete, history search, command suggestions, etc, those all will still lag because they are waiting for a response from the server. The lag that is eliminated is the local echo of characters as you type, as mosh is sending those asynchronously in the background. If you have fancy, more interactive prompt/cmdline on the remote server then you'll still see the issue. Ditto if…

But what’s the alternative? Local development with syncing back to a server? The lag is something that I can deal with. For me, the killer feature is the automatic reconnects. I usually only use mosh when I’m traveling and at conferences. In that scenario, I’m either using my iPad (with keyboard) where the client might be killed anytime I switch apps or I’m using the conference WiFi, with is always spotty. In either…

Post by anamexis » Wed, Apr 08, 2020, 6:06 PM UTC

acoard wrote: post #113

mbreese wrote: post #97

Earlier quoted context omitted.

But what’s the alternative? Local development with syncing back to a server? The lag is something that I can deal with. For me, the killer feature is the automatic reconnects. I usually only use mosh when I’m traveling and at conferences. In that scenario, I’m either using my iPad (with keyboard) where the client might be killed anytime I switch apps or I’m using the conference WiFi, with is always spotty. In either…

>But what’s the alternative? Local development with syncing back to a server? I'd say this is a perfectly fine solution for a lot of cases. Not all, of course, like your iPad one sounds a great fit for mosh (and I'm gonna try it out!) But even a RaspberryPi can power a really powerful terminal. You can use sshfs[0] to mount a remote drive over ssh. Obviously there will still be some lag - `ls` will require a round tr…

Post by [deleted] » Wed, Apr 08, 2020, 6:22 PM UTC

clarry wrote: post #58

polote wrote: post #53

As 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?

Post by Dylan16807 » Wed, Apr 08, 2020, 6:30 PM UTC

mprovost wrote: post #109

Dylan16807 wrote: post #60

Earlier quoted context omitted.

Mosh could easily load the skipped-over lines in the background. It's not incompatible with the design. It just requires a developer to put in the effort.

Can it though? How can a program manipulate the scrollback buffer of the terminal that it's running in? Other than by printing more output. But once it's updated the current line, it can't go back and add more lines - those lines have already been printed on the scroll.