4 ms·
TRAMP used to be my reasons to use emacs too, but VS code's ssh remote plug in is amazing.
by xxpor 6y ago
TRAMP used to be my reasons to use emacs too, but VS code's ssh remote plug in is amazing.
- Scarbutt 6y agoHe meant running Emacs on the remote server which IMO is even better than using vscode's remote plugin.
- jonnycomputer 6y agoYeah, I do use Tramp mode, but have, at times, had problems with it and actually found an smb mount to be more reliable (ha!) when editing files. But often what is the case is that I'm using a variety of bash tools while ssh'd in, and then quickly find I need to edit a file and so launch the server's copy of emacs. Theoretically, I could do everything in Emacs terminal mode, or eshell, either using Tramp, or in the remote instance of Emacs, but I never seem to find that it works hassle free, which is too bad, because I really like being able to move about the terminal field as if it were a text file (e.g. doing a regex on already existing output, etc.).
- cmrdporcupine 6y agoRemote SSH plus indexing a code base of my size over a 10mbpsa connection is just... oh nope, no way. Can't even reliably index it locally.
- xxpor 6y agoThe indexing runs on the remote server. Now, not sure what traffic autocomplete and such ends up using, but most of the hard work happens remotely.