5 ms·
VS Code’s remote ssh extension could help here. It’s basically a “headless vscode” running on the remote instance that your local machine can connect to. (A la.
by jakear 6y ago
VS Code’s remote ssh extension could help here. It’s basically a “headless vscode” running on the remote instance that your local machine can connect to. (A la. emacs, from what I’ve been told.) The language services and etc. all run on the remote instance, so there isn’t the giant network penalty you get from sshfs or whatever either.
Disclaimer: on team, but not in this area specifically :)
- andreareina 6y agoConnecting to a remote emacs client is a bit of a pain. What it does do is handle remote paths via TRAMP: pretty much anything that takes a path (file editing, magit, shell mode, etc) handles ssh automatically.
- jakear 6y agoSounds like you know a bit about this, have you tried using the remote-ssh extension for VSCode? If so, how does it compare?
- andreareina 6y agoI've never used VSCode. A cursory look suggests that the VSCode way performs better (in particular, no need to ship files back-and-forth), but depends on the remote end also having VSCode installed. The TRAMP way suffers a bit when dealing with large files, or large numbers of files, but works anywhere ssh + the usual shell utilities does.
- rhabarba 6y agoYes: TRAMP can be a bit slow, but it is very portable.
- jakear 6y agoWe do try to make the remote install easy. It happens behind the scenes on first connect and will even tunnel through the ssh tunnel in cases where proxies/etc. would typically make things annoying.
- rhabarba 6y agoWhich operating systems are possible on the remote end?
- jakear 6y agoIn short: x86_64 and ARMv7/8 Linux, Windows 10 / server 2016/2019. MacOS Mojave. In length: https://code.visualstudio.com/docs/remote/ssh https://code.visualstudio.com/docs/remote/ssh
- rhabarba 6y agoI understand that it’s not a solution for my BSD servers then. Thank you though, I didn’t know about that and I might try it later.