3 ms·

I've never learnt Vim or Emacs, have always used Nano when editing via the terminal. However I increasingly find myself firing up a VSCode remote session if I n

I've never learnt Vim or Emacs, have always used Nano when editing via the terminal. However I increasingly find myself firing up a VSCode remote session if I need to edit more than a single line. Remote VSCode is kind of magic, I'm increasingly working in (local) VMs via it. I have one project that is probably never going to never going to support ARM, and I'm close to needing to upgrade my MacBook. I really want an M2, but this project would be hard to run locally on it. VSCode on a remove VM is probably going to be the answer.

forgotpwd16 4y ago
I don't understand something. In order to remote develop you've to install VSCode to the remote machine?
- samwillis 4y ago
  Sort of... VSCode will temporarily download and install its remote server on the remote machine, under your user home, when you connect to it. You don't have to do it yourself. To connect it's just plain ssh, so as long as you can login you can use it remotely. As soon as you connect it gives you a file file browser to select the root for VSCodes built in file browser side bar. My understanding is VSCode has a client/server architecture and so this was considered in its architectural design from the beginning. Along with file io, it's runs the language servers, git, terminal, and many other plugins remotely. Not all your plugins will initially be installed on the remote, but it's just a case of going to the plugins panel and clicking one button to install and enable on the remote.
  - yakshaving_jgt 4y ago
    FWIW, vim can edit files over ssh. You still use your local vim, so you don’t need to [even temporarily] download/install your configuration/plugins on the remote machine. An alternative approach might be to mount the remote directory as a file system with sshfs.
Aperocky 4y ago
I liked Atom before I jumped into vim. I installed about 10 plugins that made my vim look almost exactly like Atom, except much faster, I also had a script that could install the exact plugins in any unix system in a few seconds, very useful since I work with VMs. Best of both worlds, people often forgets/don't know that vim are actually more configurable than other editors - colors, layouts, you name it.

forgotpwd16 4y ago

I don't understand something. In order to remote develop you've to install VSCode to the remote machine?

samwillis 4y ago
Sort of... VSCode will temporarily download and install its remote server on the remote machine, under your user home, when you connect to it. You don't have to do it yourself. To connect it's just plain ssh, so as long as you can login you can use it remotely. As soon as you connect it gives you a file file browser to select the root for VSCodes built in file browser side bar. My understanding is VSCode has a client/server architecture and so this was considered in its architectural design from the beginning. Along with file io, it's runs the language servers, git, terminal, and many other plugins remotely. Not all your plugins will initially be installed on the remote, but it's just a case of going to the plugins panel and clicking one button to install and enable on the remote.
- yakshaving_jgt 4y ago
  FWIW, vim can edit files over ssh. You still use your local vim, so you don’t need to [even temporarily] download/install your configuration/plugins on the remote machine. An alternative approach might be to mount the remote directory as a file system with sshfs.

Aperocky 4y ago

I liked Atom before I jumped into vim. I installed about 10 plugins that made my vim look almost exactly like Atom, except much faster, I also had a script that could install the exact plugins in any unix system in a few seconds, very useful since I work with VMs. Best of both worlds, people often forgets/don't know that vim are actually more configurable than other editors - colors, layouts, you name it.