![]() bashrc listed if you scroll down, but you can simply type in. In the menu that comes up when you press Ctrl+ O, it should say /home/ you/, but with your username (on the WSL system) in place of you. bashrc file in place, you probably wouldn't want to do that. You can also open folders (in the usual way) in this mode, which you may often want to do, especially if you want Git integration in the editor. If you go to open a file in the remote editing window, then instead of showing you a native file-open dialog, you get menus in Visual Studio Code through which you can navigate to any location in the system you're connected to. In the new window, on the lower-left corner, it will show WSL: Ubuntu. You'll probably want to select Remote-WSL: New Window most of the time. When you click that, a menu appears at the top of the window with various actions to start remote editing. With the necessary extension(s) installed, you should see a > < button at the lower-left corner of every Visual Studio Code window, with the mouseover text Open a remote window. (I've tried.) If you installed Visual Studio Code packages inside the WSL system, I suggest removing them, and doing so may even get your code command to start working properly.Īnyway, you can connect to the WSL system within the editor, which is what I recommend. the client program, inside a WSL system is not supported and is not particularly likely to work even on a Windows system with an X server like VcXsrv on which other graphical Ubuntu programs usually work. Note that installing the Visual Studio Code itself, i.e. ![]() Once it's installed, you should be able to run code from within the WSL system and open editor windows on the host system that connect to the WSL system, though I've always found this awkward at best. (The Remote Development Extension Pack installs that extension as well as others for remote editing on non-WSL systems via SSH.) You can install it from within Visual Studio Code those links are mainly for reference. But really you only need the Remote - WSL extension for this. I recommend installing the Remote Development Extension Pack in Visual Studio Code, if you haven't already. ![]() Furthermore, depending on what's going wrong, the procedure of setting that up may also make the code command work the way you want. The only difference from a user interface perspective is which menu item you select to connect. This works almost the same way as remote editing via SSH of files on another machine (which can be done both from Windows and GNU/Linux clients and is itself separate from WSL). You can start Visual Studio Code in Windows, then connect to your WSL system with it and open whatever files you want to edit.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |