←back to thread

Making TRAMP faster

(coredumped.dev)
226 points celeritascelery | 3 comments | | HN request time: 1.171s | source
Show context
IceDane ◴[] No.44357681[source]
Tramp is tolerable, but it is absolutely not great. You went on to demonstrate that right after making that claim, where you manually (and insufficiently) hack around its issues to arrive at something that is only barely comparable to eg what vs code can do.
replies(1): >>44357713 #
kleiba ◴[] No.44357713[source]
Forgive my ignorance, but what does VSCode do?
replies(1): >>44358232 #
kristjansson ◴[] No.44358232[source]
Download a copy of itself onto the remote, run it there, and allow interaction with that copy
replies(3): >>44358522 #>>44358844 #>>44359062 #
1. skydhash ◴[] No.44359062[source]
To be fair, for some dev workflows, TRAMP is lacking (LSPs), but it's more than enough if you're fine with grepping and ctags, I think. For the former scenario, I either run terminal emacs or use distrobox/toolbox (they setup everything for the wayland socket that graphical emacs needs)
replies(1): >>44360895 #
2. anyfoo ◴[] No.44360895[source]
LSPs should work fine with TRAMP. In practice I have a problem with it, since there is some bad interaction between eglot, TRAMP, and clangd in certain cases, but that is a specific situation and a bug.
replies(1): >>44361060 #
3. skydhash ◴[] No.44361060[source]
gopls was a bit of a pain. By default it uses stdio, and there were some integration issues with eglot, tramp, amd gopls. I also had some issues trying to use tcp ports. I switched to terminal emacs over ssh, the. use distrobox (I didn’t want to install dev tools locally).