←back to thread

Making TRAMP faster

(coredumped.dev)
226 points celeritascelery | 1 comments | | HN request time: 0.209s | source
Show context
jonnycomputer ◴[] No.44356898[source]
I kinda gave up on using it because so many of my remotes are tunneled through a jump host and I never could get it to connect seamlessly. It seems like it ought to, but when vscode just works with my ssh config, I decided debugging it was not a good use of my time. Might have something to do with being on a Mac, idk.
replies(4): >>44357207 #>>44357418 #>>44357476 #>>44361649 #
1. dietr1ch ◴[] No.44361649[source]
You can jump through bastion hosts transparently™ with ~/ssh:you_but_jumping@bastion|ssh:you@remote:path/to/file~ (https://stackoverflow.com/a/16408592)

The thing that I had to fiddle with, was getting ssh and tramp to use the same ControlPath to share sockets because it helped make things smooth if you had setup ssh to use ssh-agent and persist connections already.

But yeah, I get why just giving up on tramp has been easier over the years. Besides connecting there's also annoyances on spotty internet that make avoiding it usually a better experience. I think I haven't relied much on tramp after trying to use it and realising tmux+emacs was overall better at the time, mainly because I could just hop on my workstation to the exact same session I was using once RTO happened. Nowadays I use it mostly for sudo and one off things, but not remote projects with remote compile and lsp anymore.