4 ms·
Emacs Power: remote servers and shell commands
- DavidSJ 17y agoIn my experience, TRAMP is unbearably slow.
- yason 17y agoThere's some natural and unavoidable latency due to ssh/smb/ftp/whatever you're using but I use tramp daily and in practice it's quite unnoticeable. Local machines respond immediately, machines in the same country are very much usable as well. Just make tramp keep the connections alive longer and cache the password. And set backup directory to something local! C-c C-s is still faster than using a shell in another console and scp/rsync.
- davidw 17y agoIt's a tradeoff - it might be a little bit slower in opening a file, but then you get to edit it locally, which can be way better than using an editor on a remote machine through a slow link.
- deleted 17y ago[deleted]
- pqs 17y agomy experience tells that over ftp it can be very slow, but over ssh it is fine.
- DavidSJ 17y agoI was referring to ssh.
- jrockway 17y agoI have never gotten TRAMP to work. I just use sshfs, which is much easier to use. ("sshfs user@host:~ my_home_at_host") I will also point out that eshell and ansi-term are much better shells for use inside emacs. I used ansi-term for a long time, but gradually weaned myself off bash and into eshell. Now I can write "shell commands" as (loop) invocations. :)
- pqs 17y agoThat's strange. I never had problems with tramp!
- jrockway 17y agoYeah, it is strange. I have seen other people use it successfully... but there must be something about my config that is strange... it connects OK, but opening files often times out or they show up truncated. sshfs just works better. (+1 for abstraction.)
- omouse 17y agoI've had problems using TRAMP with OpenBSD. SSH works and I think FTP does too, but for some reason, TRAMP just hangs. It does seem to connect but then it hangs. Does TRAMP expect a certain type of shell prompt?
- daemianmack 17y agoIt does. The relevant snippet from my .emacs.d: ;; For tramp with my bash config, the prompt of which terminates ;; in a newline. Tell tramp how to detect the end of my prompt. (setq shell-prompt-pattern " ") The value of the shell-prompt-var is a literal newline. (That newline entered, naturally, with a C-q C-j.)