this post was submitted on 12 Oct 2023
2 points (100.0% liked)

Emacs

311 readers
1 users here now

A community for the timeless and infinitely powerful editor. Want to see what Emacs is capable of?!

Get Emacs

Rules

  1. Posts should be emacs related
  2. Be kind please
  3. Yes, we already know: Google results for "emacs" and "vi" link to each other. We good.

Emacs Resources

Emacs Tutorials

Useful Emacs configuration files and distributions

Quick pain-saver tip

founded 1 year ago
MODERATORS
rglullis@communick.news
raphael@communick.news
2
Future of remote development (alien.top)
submitted 1 year ago by marcbowes@alien.top to c/emacs@communick.news
28 comments fedilink hide all child comments
 

I'm interested to know what the future of remove development with emacs might look like. I'm a long time emacs user, and use rust, lsp-mode, magit and projectile heavily. The remote experience with tramp just isn't very good. I've had to work around several bugs that lead to hangs, and even though I'm only ~20millis away from my remote machine performance is pretty bad. I believe I've already done everything I can to make it fast (ssh control master, etc.), and I'm still not happy. On the other hand, VSCode (which I'm not familiar with) or IntelliJ make remote development a breeze. I really like how they hide latency, and handle reconnects well. I've also tried terminal emacs on the remote machine, but I just can't deal with the input lag.

It's remarkable how emacs has been able to adapt over the years, and so I'm interested to hear about some ideas to keep emacs relevant for this usecase.

you are viewing a single comment's thread
view the rest of the comments
[–] arthurno1@alien.top 1 points 1 year ago

If you use Magit, LSP and Projectile to code Rust, have you tried to clone the repo(s) you are working on to your local computer and enable git server on remote so you can push your changes. Or if you don't wish to enable git server, transfer files from the work machine to remote via some other means (sftp) and just commit when you know you are done. It would remove the latency for the most part. Otherwise you are perhaps better off running Emacs on the remote and forward X to your work station, have you tried? Or probably even faster, just ssh into remote and run Emacs in terminal.

I am not sure if it is tramp problem; it is probably that you are just generating too much traffic if you are using Emacs on a remote as if you would be using it on your workstation.