sqlite-tui VS Mosh

> I usually use Mosh

Mosh as in "mobile shell"? https://mosh.org/

> Would you suggest I try slime-tramp?

I don't know yet, I've just started trying it out.

What made me want to try it was that I could use GUI Emacs to connect to emacs running on a different machine and still have full access to all the emacs keybindings.

So far, the downsides that I have encountered are that M-. and C-c C-k (slime-compile-and-load-file) don't quite work. The work-around would be to visit each file using the remote path and re-compile them so that the running Lisp image can map what's in the image to a path tramp recognizes. Then M-. and C-c C-k should work.

To recompile, select all then compile (X-c X-p C-c C-c) works, or I think C-c M-k also works. Not a great solution if there are a lot of files, though.

IIUC the problem boils down to M-. eventually calling (xref-find-definitions) which is an emacs built-in, and I think that's why the tramp paths aren't translating until a re-compile is done.

Seems so: I like the idea. Would be, however, to integrate with mosh [1] and feel much better if there was a well audited SSH implementation beneath the hole punching and rendezvous layer.

[1] https://github.com/mobile-shell/mosh

https://mosh.org/#faq:~:text=Q%3A%20What%20is%20Mosh%27s%20s...

The cryptography is standard AES-128 in OCB3 mode. It's been around long enough, and has had enough security scrutiny to at least discover a few minor DoS vulnerabilities, that it isn't entirely unreviewed.

For the cipher itself, see https://en.wikipedia.org/wiki/OCB_mode#Attacks

I’m not sure about resuming from sleep, but does mosh address your network stability issues?

https://mosh.org/

Use mosh (https://mosh.org/) instead of ssh

This is something I've been tracking pretty closely. My understanding of the current options: 1. Use sshfs. Pros: nothing to install on the remote server. Cons: will choke on huge filesystems when doing some operations (e.g. fuzzy finding). Also requires all your LSP/linting/analysis tools to be installed locally, which may not be the case if your company is transitioning to remote developer environments. 2. Use netrw or similar. Pros: nothing to install. Cons: will not play nice with LSP, fuzzy finding, or anything else. 3. Use distant.nvim. At this point, basically the same as netrw except that maybe remote LSP will work. 4. SSH to the server and use nvim there. Pros: simple and everything works. Cons: Have to install nvim on the server. SSH connection may cause typing lag if the RTT is high (some people report that Mosh can help the lag issue)

In my experience, vscode remote code editing is very buggy and resource hungry. Not very fitting if your Internet is unstable/slow and/or your target workstation is not that powerful (why is 8GB of RAM not enough?). I've had more success with Neovim either with distant.nvim[0] or directly on the Workstation with mosh[1]

0: https://distant.rocks/

1: https://mosh.org/

The Mosh SSH client for intermittent connectivity ( https://mosh.org/ ) has definitely saved me at least 100 hours. Too bad that it's only available for Windows as a Chrome extension, and Chrome will discontinue support for it starting in the new year. Really not looking forward to having to search for an alternative...

mosh is supposed to be pretty good for ssh latency: https://mosh.org

Today, my project uses SSH to authenticate with a remote machine, start up the server, and report back the address, port, and key that are used for encrypted communication with my server. This mirrors how mosh and eternal terminal work.