Hacker News Reader

I haven't used Emacs in a while, so I'm very rusty, but why would you run a remote Emacs in SSH, and not use your local Emacs to access remote stuff via TRAMP?

In my Emacs days, I've never really used the terminal version. Multiple frames, yay!

View on HN

On my remote systems, about the first thing I do after a reboot is call "emacs --daemon" via SSH and then use emacsclient to edit files. For one thing, TRAMP has higher latency, and it also keeps state across disconnects and reboots of my desktop system. I regulary have lots of configuration files open, tail-mode buffers to watch log files, an eshell session, man pages, web pages (using w3m), and it is just too much of a hassle to open these all over again all the time.

Also, if you have to access the remote machine through a low-bandwidth line, the terminal version at least feels more efficient than using TRAMP from my workstation. For most purposes, the GUI does not offer that much of an advantage.

Some people run their dev environments on remote linux machines (VPSs), it makes them OS agnostic, you just need a ssh client, while tramp is awesome, imo not using it gives you a faster and more streamline workflow.

Reply on news.ycombinator.com