![]() This is the final part of our VS Code and WSL series of blog posts. To learn more, see the VS Code Remote Development documentation, where you’ll find guides and tutorials.Īnd keep following the Windows Command Line Tools blog and the Visual Studio Code release notes for further improvements to WSL and the Remote – WSL extension. WSL and VS Code lets you do productive Linux development from the convenience of your Windows machine. It’s still in the experimental stage and requires you use the VS Code Insiders build, but you can run VS Code in Alpine distributions. The next version of WSL ( WSL2, which is in preview) fixes this issue and provide significantly better file system performance. You will need to reload VS Code ( Developer: Reload Window from the Command Palette (F1)) for these settings to take effect. You can also tune how often VS Code polls using the setting, which is by default every 5 seconds. Polling is resource heavy, so it is not turned on by default. In your user settings.json, add: "": true To work around this issue, you can tell VS Code to “poll” for file system changes rather than apply a lock to the folder. In the current version of WSL (WSL1), there is a limitation where it is not possible to rename a non-empty folder from VS Code. ![]() If you are connected to a WSL instance, you’ll see all of the shells defined in /etc/shells: Choose Select Default Shell and if you are on the Windows side, you’ll see Command Prompt, PowerShell, or WSL Bash: Open a new terminal Terminal > New Terminal (Ctrl+`) and open on the dropdown. When running in WSL, you can choose bash or zsh or whatever shell you might have installed. For example, when running on the Windows side, you can specify PowerShell or WSL. You can easily set up different default shells when opening a terminal in VS Code.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |