←back to thread

Making TRAMP faster

(coredumped.dev)
226 points celeritascelery | 3 comments | 23 Jun 25 14:46 UTC | HN request time: 0.602s | source
Show context
imiric ◴[23 Jun 25 16:07 UTC] No.44357190[source]▶
TRAMP is neat, but I find watchexec+rsync to be a much more performant alternative. This way I keep editing files locally, and they're simply synced to the remote host when they change. This workflow also has the benefit of being able to use all my local tooling, it keeps a local copy which I often need, it supports any editor (forgive me, Father rms), and is easily configurable (include or exclude files, delete files on the remote, etc.).
replies(5): >>44357445 #>>44357699 #>>44357700 #>>44358773 #>>44364956 #
dima55 ◴[23 Jun 25 16:56 UTC] No.44357700[source]▶
But then you can't do other stuff. Remote LSP, gdb, etc, etc.
replies(1): >>44359046 #
1. kleiba ◴[23 Jun 25 19:13 UTC] No.44359046[source]▶
What the OP presumably means is that they just have a local copy of all the files. Then you only edit local (with LSP, gdb, etc.) and any change you make to a local file is mirrored back to the remote copy automagically.
replies(2): >>44359067 #>>44360829 #
2. ParetoOptimal ◴[23 Jun 25 19:16 UTC] No.44359067[source]▶
This won't work for things that use a docker container without wrapper scripts, but those have their own problems.
3. anyfoo ◴[23 Jun 25 22:26 UTC] No.44360829[source]▶
Which means you can’t remote LSP, gdb, etc.

In other words, it only works if your local platform is the same (or compatible) with the remote platform, or (in a limited capacity) if you have a viable cross compiling environment.