Small edits to recent updates
This commit is contained in:
Greg Van Liew
Родитель
3db86f46b7
Коммит
0a74a649e7
|
|
@ -331,7 +331,7 @@ Either use an SSH key without a passphrase, clone using HTTPS, or run `git push`
|
|||
|
||||
On Linux, you can use your distribution's package manager to install SSHFS. For Debian/Ubuntu: `sudo apt-get install sshfs`
|
||||
|
||||
> **Note:** WSL 1 does not support FUSE or SSHFS, so the instructions differ for Windows currently. **WSL2 does include FUSE and SSHFS support**, so this will change soon.
|
||||
> **Note:** WSL 1 does not support FUSE or SSHFS, so the instructions differ for Windows currently. **WSL 2 does include FUSE and SSHFS support**, so this will change soon.
|
||||
|
||||
On macOS, you can install SSHFS using [Homebrew](https://brew.sh/): `brew install sshfs` In addition, if you would prefer not to use the command line to mount the remote filesystem, you can also install [SSHFS GUI](https://github.com/dstuecken/sshfs-gui).
|
||||
|
||||
|
|
@ -610,7 +610,6 @@ Open the Debian WSL shell to add `wget` and `ca-certificates`:
|
|||
sudo apt-get update && apt-get install wget ca-certificates
|
||||
```
|
||||
|
||||
|
||||
#### Alpine
|
||||
|
||||
Open the Alpine WSL shell as root (`wsl -d Alpine -u root`) to add `libstdc++`:
|
||||
|
|
@ -625,7 +624,6 @@ On Windows 10 April 2018 Update (build 1803) and older, `/bin/bash` is required:
|
|||
apk update && apk add bash
|
||||
```
|
||||
|
||||
|
||||
### Selecting the distribution used by Remote - WSL
|
||||
|
||||
**Remote-WSL: New Window** will open the WSL distro registered as default.
|
||||
|
|
@ -651,14 +649,14 @@ wslconfig /l
|
|||
### Configure the environment for the server startup
|
||||
|
||||
When the Remote WSL extension starts the VS Code server in WSL, it does not run any shell configuration scripts. This was done to avoid that custom configuration scripts can prevent the startup.
|
||||
If you need to configure the startup environment, you can use the environment setup script as described here [here](https://code.visualstudio.com/docs/remote/wsl#_advanced-environment-setup-script).
|
||||
|
||||
If you need to configure the startup environment, you can use the environment setup script as described [here](/docs/remote/wsl.md#advanced-environment-setup-script).
|
||||
|
||||
### Configure the environment for the remote extension host
|
||||
|
||||
The environment for the remote extension host and terminal are based on the default shell's configuration scripts:
|
||||
To evaluate the environment variables for the remote extension host process, the server creates an instance of the default shell as _interactive login shell_. It probes the environment variables from it and uses them as initial environment for the remote extension host process. The values of environment variables therefore depend on what shell is configured as default and the content of the configuration scripts for that shell.
|
||||
The environment for the remote extension host and terminal are based on the default shell's configuration scripts. To evaluate the environment variables for the remote extension host process, the server creates an instance of the default shell as an **interactive login shell**. It probes the environment variables from it and uses them as the initial environment for the remote extension host process. The values of environment variables therefore depend on what shell is configured as the default and the content of the configuration scripts for that shell.
|
||||
|
||||
See [here](https://github.com/rbenv/rbenv/wiki/unix-shell-initialization) for an overview of each shells configuration scripts. Most WSL distributions have `/bin/bash` configured as the default shell. `/bin/bash` will look for startup files under `/etc/profile` first and for any startup files under `~/.bash_profile`, `~/.bash_login`, `~/.profile`.
|
||||
See [Unix shell initialization](https://github.com/rbenv/rbenv/wiki/unix-shell-initialization) for an overview of each shells configuration scripts. Most WSL distributions have `/bin/bash` configured as the default shell. `/bin/bash` will look for startup files under `/etc/profile` first and for any startup files under `~/.bash_profile`, `~/.bash_login`, `~/.profile`.
|
||||
|
||||
To change the default shell of a WSL distro, follow the instructions of [this blog post](https://medium.com/@vinhp/set-and-use-zsh-as-default-shell-in-wsl-on-windows-10-the-right-way-4f30ed9592dc).
|
||||
|
||||
|
|
@ -684,7 +682,7 @@ But, if you used the **System Installer**, the install path is:
|
|||
/mnt/c/Program Files (x86)/Microsoft VS Code/bin
|
||||
```
|
||||
|
||||
It's a feature of WSL that paths are inherited from the PATH variable in Windows. To change the Windows PATH variable, use the `Edit environment variables for your account` command from the start menu in Windows.
|
||||
It's a feature of WSL that paths are inherited from the PATH variable in Windows. To change the Windows PATH variable, use the **Edit environment variables for your account** command from the start menu in Windows.
|
||||
|
||||
If you have disabled the path sharing feature, edit your `.bashrc`, add the following, and start a new terminal:
|
||||
|
||||
|
|
@ -699,18 +697,17 @@ export PATH="$PATH:/mnt/c/Windows/System32:/mnt/c/Users/${WINDOWS_USERNAME}/AppD
|
|||
|
||||
```
|
||||
|
||||
> **Note:** Be sure to quote or escape spaces in the directory names.
|
||||
> **Note:** Be sure to quote or escape space characters in the directory names.
|
||||
|
||||
### I see EACCESS: permission denied error trying to rename a folder in the open workspace
|
||||
|
||||
That's a known problem with the WSL file system implementation ([Microsoft/WSL#3395](https://github.com/Microsoft/WSL/issues/3395), [Microsoft/WSL#1956](https://github.com/Microsoft/WSL/issues/1956)) caused by the file watcher active by VSCode. The issue will only be fixed in WSL2.
|
||||
This is a known problem with the WSL file system implementation ([Microsoft/WSL#3395](https://github.com/Microsoft/WSL/issues/3395), [Microsoft/WSL#1956](https://github.com/Microsoft/WSL/issues/1956)) caused by the file watcher active by VS Code. The issue will only be fixed in WSL 2.
|
||||
|
||||
To avoid the issue, set `remote.WSL.fileWatcher.polling` to true. However, polling based has a performance impact for large workspaces.
|
||||
|
||||
For large workspace you want to increase the polling interval: `remote.WSL.fileWatcher.pollingInterval` and control the folders that are watched: `files.watcherExclude`.
|
||||
|
||||
[WSL2](https://docs.microsoft.com/en-us/windows/wsl/wsl2-index) does not have that file watcher problem is also not affected by the new setting.
|
||||
For large workspace you may want to increase the polling interval, `remote.WSL.fileWatcher.pollingInterval`, and control the folders that are watched with `files.watcherExclude`.
|
||||
|
||||
[WSL 2](https://docs.microsoft.com/en-us/windows/wsl/wsl2-index) does not have that file watcher problem and is not affected by the new setting.
|
||||
|
||||
### Resolving Git line ending issues in WSL (resulting in many modified files)
|
||||
|
||||
|
|
@ -772,7 +769,7 @@ While many extensions will work unmodified, there are a few issues that can prev
|
|||
|
||||
### Resolving errors about missing dependencies
|
||||
|
||||
Some extensions rely on libraries not found in the vanilla install of certain WSL Linux distributions. You can add additional libraries into your Linux distribution by using its package manager. For Ubuntu and Debian based distributions, run `sudo apt-get install <package>` to install the needed libraries. Check the documentation for your extension or the runtime that is mentioned for additional installation details.
|
||||
Some extensions rely on libraries not found in the basic install of certain WSL Linux distributions. You can add additional libraries into your Linux distribution by using its package manager. For Ubuntu and Debian based distributions, run `sudo apt-get install <package>` to install the needed libraries. Check the documentation for your extension or the runtime that is mentioned in the error message for additional installation details.
|
||||
|
||||
### Local absolute path settings fail when applied remotely
|
||||
|
||||
|
|
|
|||
|
|
@ -25,7 +25,7 @@ To get started, you need to:
|
|||
|
||||
1. Install the [Windows Subsystem for Linux](https://docs.microsoft.com/windows/wsl/install-win10) along with your preferred Linux distribution.
|
||||
|
||||
> **Note:** WSL1 does have some [known limitations](#known-limitations) for certain types of development and WSL2 support is **experimental**. Also, extensions installed in Alpine Linux may not work due to `glibc` dependencies in native code inside the extension. See the [Remote Development and Linux](https://aka.ms/vscode-remote/linux) article for details.
|
||||
> **Note:** WSL 1 does have some [known limitations](#known-limitations) for certain types of development and WSL 2 support is **experimental**. Also, extensions installed in Alpine Linux may not work due to `glibc` dependencies in native code inside the extension. See the [Remote Development and Linux](https://aka.ms/vscode-remote/linux) article for details.
|
||||
|
||||
2. Install [Visual Studio Code](https://code.visualstudio.com/) on the **Windows** side (not in WSL).
|
||||
|
||||
|
|
@ -203,13 +203,13 @@ Some extensions rely on libraries not found in the vanilla install of certain WS
|
|||
|
||||
### I see EACCESS: permission denied error trying to rename a folder in the open workspace
|
||||
|
||||
That's a known problem with the WSL file system implementation ([Microsoft/WSL#3395](https://github.com/Microsoft/WSL/issues/3395), [Microsoft/WSL#1956](https://github.com/Microsoft/WSL/issues/1956)) caused by the file watcher active by VSCode. The issue will only be fixed in WSL2.
|
||||
That's a known problem with the WSL file system implementation ([Microsoft/WSL#3395](https://github.com/Microsoft/WSL/issues/3395), [Microsoft/WSL#1956](https://github.com/Microsoft/WSL/issues/1956)) caused by the file watcher active by VSCode. The issue will only be fixed in WSL 2.
|
||||
|
||||
To avoid the issue, set `remote.WSL.fileWatcher.polling` to true. However, polling based has a performance impact for large workspaces.
|
||||
|
||||
For large workspace you want to increase the polling interval: `remote.WSL.fileWatcher.pollingInterval` and control the folders that are watched: `files.watcherExclude`.
|
||||
|
||||
WSL2 does not have that file watcher problem is also not affected by the new setting.
|
||||
WSL 2 does not have that file watcher problem is also not affected by the new setting.
|
||||
|
||||
### What are the connectivity requirements for the Remote - WSL extension?
|
||||
|
||||
|
|
|
|||
|
|
@ -253,7 +253,7 @@ You can learn about new extension features and bug fixes in the [Remote Developm
|
|||
You can also read two recent blog posts describing:
|
||||
|
||||
* [Remote SSH Tips and Tricks](https://code.visualstudio.com/blogs/2019/10/03/remote-ssh-tips-and-tricks)
|
||||
* [WSL2 with Visual Studio Code](https://code.visualstudio.com/blogs/2019/09/03/wsl2).
|
||||
* [WSL 2 with Visual Studio Code](https://code.visualstudio.com/blogs/2019/09/03/wsl2).
|
||||
|
||||
## Preview features
|
||||
|
||||
|
|
|
|||
|
|
@ -85,7 +85,7 @@ You can now press `kb(list.scrollUp)` and `kb(list.scrollDown)` to scroll lists
|
|||
|
||||
### `files.eol` per language
|
||||
|
||||
The `files.eol` setting can now also be set per language. For example you could define that all files of 'mylanguage' use `\n` as the default end-of-line sequence for all new files.
|
||||
The `files.eol` setting can now also be set per language. For example, you could define that all files of 'mylanguage' use `\n` as the default end-of-line sequence for all new files.
|
||||
|
||||
```jsonc
|
||||
"[mylanguage]": {
|
||||
|
|
@ -93,10 +93,7 @@ The `files.eol` setting can now also be set per language. For example you could
|
|||
}
|
||||
```
|
||||
|
||||
The end-of-line sequence is used for new files. For existing files the existing end-of-line sequence is always preserved. To change the end-of-line sequence for an existing file, use the `Change End Of Line Sequence` command.
|
||||
|
||||
Using that mechanism, the default end-of-line sequence for shellscript if now defined as `\n`.
|
||||
|
||||
The end-of-line sequence is used for new files. For existing files, the existing end-of-line sequence is always preserved. To change the end-of-line sequence for an existing file, use the **Change End Of Line Sequence** command.
|
||||
|
||||
### Minimap scaling and improved font rendering
|
||||
|
||||
|
|
|
|||
|
|
@ -90,7 +90,7 @@ The WSL extension now downloads the VS Code server build on the Windows side ins
|
|||
|
||||
### Use polling for file watching in WSL
|
||||
|
||||
You can now configure that file watching in WSL uses polling with a new setting: `remote.WSL.fileWatcher.polling`. This fixes the WSL1 issue that non-empty folders can not be renamed when watched. However, polling has a performance impact for large workspaces. You can also tune the polling by setting the polling interval: `remote.WSL.fileWatcher.pollingInterval` and control the folders that are watched with `files.watcherExclude`. WSL2, which does not have this problem, is not affected by the new setting.
|
||||
You can now configure that file watching in WSL uses polling with a new setting: `remote.WSL.fileWatcher.polling`. This fixes the WSL 1 issue that non-empty folders can not be renamed when watched. However, polling has a performance impact for large workspaces. You can also tune the polling by setting the polling interval: `remote.WSL.fileWatcher.pollingInterval` and control the folders that are watched with `files.watcherExclude`. WSL 2, which does not have this problem, is not affected by the new setting.
|
||||
|
||||
Due to the performance impact, polling is disabled by default.
|
||||
|
||||
|
|
|
|||
Загрузка…
Ссылка в новой задаче