←back to thread

Making TRAMP faster

(coredumped.dev)
226 points celeritascelery | 4 comments | 23 Jun 25 14:46 UTC | HN request time: 0.001s | 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 #
wging ◴[23 Jun 25 16:30 UTC] No.44357445[source]▶
I did the same thing when I was building on remote machines frequently. Either an internal one-way syncing tool or Unison, but basically the same as what I think you're implying. (Watchexec to notice changes, and kick off your local rsync to the remote machine, right?)

TRAMP rarely seemed worth it to fiddle with, especially when such a workflow supports all tools, even those run in a CLI outside of emacs: run a formatter or other automation locally and have the changes propagate? git pull locally, ditto? why not?

replies(2): >>44357805 #>>44359649 #
1. celeritascelery ◴[23 Jun 25 17:07 UTC] No.44357805[source]▶
> TRAMP rarely seemed worth it to fiddle with, especially when such a workflow supports all tools

The problem is that this workflow doesn't support all tools (or even most tools in my case). The remote machines are a different OS with more RAM and are set up with all the tools and production environments needed. I can't run most of the locally (at least not without massive effort and porting). If you have an environment where you can easily run locally or remotely, then your workflow would make sense.

replies(2): >>44358974 #>>44363305 #
2. wging ◴[23 Jun 25 19:06 UTC] No.44358974[source]▶
That's exactly the point of remote syncing: whatever changes to code you make locally are nearly instantly available on a remote machine, so you can compile and run your software on a production-like machine. By "supports all tools" I mean that you can run whatever you like on your source code locally, whether it runs through emacs or not, and the result is available remotely. And with bidirectional syncing the reverse is true too.
replies(1): >>44360841 #
3. anyfoo ◴[23 Jun 25 22:27 UTC] No.44360841[source]▶
But I cannot use the remote clangd for LSP, for example.
4. imiric ◴[24 Jun 25 06:13 UTC] No.44363305[source]▶
Right, I suppose it depends on your use case. For most of mine, my local machine has all the tooling, and I simply want to sync the files to a remote machine for deployment. But if you want to do all development remotely, then TRAMP might be the way to go.