VSCode shows no extensions on the remote host. vscode-server-insiders folder in your home directory on the remote host as expected. If you need more details, it's all very well explained here. I installed the remote-ssh extension and my ssh config server names showed up in the VSCode connection menu. I suggest to get VSCode Insiders as the extensions are still in preview as of this writing. I did not install the pack, but remote-ssh and remote-container are now part of my favorite extensions. But I am sure Windows users will love it. I have no use for the 3rd extension for WSL (the Windows Subsystem for Linux). But the remote-ssh extension triggered my interest out of immediate necessity. He thought the remote-container extension would get my blood flowing. Then a colleague sent me a link to Remote Development: a VSCode extension pack that looked interesting. I was relieved, this was working pretty nice. I very quickly found how to configure it as a Python IDE. That's even better than my long gone power house Vim setup. One script later and missing auto completion, I decided to look for a better solution: SpaceVim. That took time, research, trial and errors, … I wasn't ready to invest the time for that, I wanted to start playing with little circuits. A few years ago, I had used vundle and a long list of plugins painstakingly configured and customised to make Vim a real power house. I'm far from being a guru at it, but I get things done pretty easily for my needs. Installing VSCode is going to be difficult.

I don't need the overhead of a graphical interface and feel at home in a shell. Obviously, that means coding tiny programs in C or Python. I bought a breadboard and a discovery pack to get going. But lately, I started to play with electronics. Until now, I used it mailny as a small linux host to run services, as a media server, as a NextCloud server, … You know, the usual suspects. Like a lot of people out there, I like to tinker with the Raspberry Pi.

Visual studio code python jedi