Small edits
This commit is contained in:
gregvanl
Родитель
091e2e1c75
Коммит
7b300be346
|
|
@ -22,6 +22,7 @@ Until the March milestone release notes are available, you can still track our p
|
|||
We really appreciate people trying our new features as soon as they are ready, so check back here often and learn what's new.
|
||||
|
||||
If you find issues or have suggestions, you can enter them in the [VS Code repository](https://github.com/Microsoft/vscode/issues) on GitHub.
|
||||
|
||||
## Updated brand icons for macOS Big Sur
|
||||
|
||||
[](images/1_55/brand-icon-example.png)
|
||||
|
|
@ -32,22 +33,18 @@ We've been working on updating the VS Code brand icons on macOS to match the new
|
|||
|---|---|---|
|
||||
||||
|
||||
|
||||
|
||||
## Accessibility
|
||||
|
||||
### Multi cursor support
|
||||
|
||||
We have added an initial screen reader support for [multi cursors](https://code.visualstudio.com/docs/editor/codebasics#_multiple-selections-multicursor). Whenever a new cursor is added we now announce that along with the cursor line and column position. We also announce when secondary cursors have been removed. We plan to further improve multi cursor with regards to accessibility as we recieve more and more feedback.
|
||||
We have added initial screen reader support for [multi cursors](https://code.visualstudio.com/docs/editor/codebasics#_multiple-selections-multicursor). Whenever a new cursor is added, VS Code now announces it along with the cursor line and column position. VS Code also announces when secondary cursors have been removed. We plan to further improve multi-cursor accessibility as we receive more feedback.
|
||||
|
||||
### Lifted limit of 100 lines for screen reader
|
||||
|
||||
Thanks to the related upstream issues being fixed we have lifted the limit of lines that a "Say All" command can read. Previously we had a hard limit of 100 lines to be announced by a screen reader at once and thanks to the upstream fix we have now lifted this limit to 1000. Further upstream fixes are needed in order for us to not have any limit at all.
|
||||
|
||||
Thanks to upstream issues being fixed, we have increased the number of lines that a "Say All" command can read. Previously we had a hard limit of 100 lines to be announced by a screen reader at once and thanks to the upstream fix we have now lifted this limit to 1000. Further upstream fixes are needed in order for us to not have any limit at all.
|
||||
|
||||
Due to the this the setting `editor.accessibilityPageSize` is now deprecated. We will still support this setting in the next couple of releases, however we plan to fully drop it in the future.
|
||||
|
||||
###
|
||||
|
||||
## Workbench
|
||||
|
||||
### Improved sash customization
|
||||
|
|
@ -65,13 +62,17 @@ Additionally, <kbd>Shift Click</kbd> range selections behave more deterministica
|
|||
|
||||
Keyboard shortcuts editor is refactored to use the new table widget thereby allowing users to resize the columns in the editor.
|
||||
|
||||
### Extensions Management improvements
|
||||
### Extension management improvements
|
||||
|
||||
VS Code window now detects extensions installed/unistalled through VS Code CLI and activate/de-activate these extensions in the window and also updates these extensions in the extensions view.
|
||||
VS Code now detects extensions installed/uninstalled through the VS Code CLI. Extensions can be activated/de-activated in the active window (instance) and will be correctly displayed in the Extensions view.
|
||||
|
||||
### Negative text filtering in Problems view
|
||||
|
||||
You can now filter problems those do not contain specific text from Problems view by prepending `!` to the filter text.
|
||||
You can now filter problems those do not contain specific text from the Problems view by prepending `!` to the filter text.
|
||||
|
||||
### Emmet
|
||||
|
||||
The `emmet.extensionsPath` settings now takes in only string arrays, and can be directly edited in the Settings Editor.
|
||||
|
||||
## Integrated Terminal
|
||||
|
||||
|
|
@ -103,7 +104,7 @@ VS Code will automatically detect and surface some of the more commonly used she
|
|||
}
|
||||
```
|
||||
|
||||
The recommended way to initially add a profile is via the `Select Default Profile` command which allows creating profiles based on either an existing profile or other detected shells.
|
||||
The recommended way to initially add a profile is via the **Select Default Profile** command which allows creating profiles based on either an existing profile or other detected shells.
|
||||
|
||||
|
||||
|
||||
|
|
@ -111,7 +112,7 @@ The recommended way to initially add a profile is via the `Select Default Profil
|
|||
|
||||
Along with the new profiles feature, we now auto detect WSL profiles and show them in the list by default, this can be turned off with the `terminal.integrated.useWslProfiles` setting.
|
||||
|
||||
Cygwin is also now auto detected and exposed in the `Select Default Profile` command and Git Bash will run as a login shell (running `~/.bash_profile`).
|
||||
Cygwin is also now auto detected and exposed in the **Select Default Profile** command and Git Bash will run as a login shell (running `~/.bash_profile`).
|
||||
|
||||
### WebGL renderer is the new default
|
||||
|
||||
|
|
@ -135,10 +136,6 @@ Last release we introduced automatic relaunching of terminals when an extension
|
|||
|
||||
There is also a new setting to disable this automatic relaunching all together `terminal.integrated.environmentChangesRelaunch`.
|
||||
|
||||
### Emmet
|
||||
|
||||
`emmet.extensionsPath` now takes in only string arrays, and can be directly edited in the Settings Editor.
|
||||
|
||||
## Debugging
|
||||
|
||||
### Improvements to breakpoints
|
||||
|
|
|
|||
|
|
@ -10,9 +10,10 @@ This also saw the departure of the `terminal.integrated.serverSpawn` and `termin
|
|||
|
||||
### Commands keybinding changes in browsers
|
||||
|
||||
Due to overlap with existing browser keybindings we have changed the following commands:
|
||||
* `Step Over` is now using `Alt + F10` instead of `F10` on all browsers
|
||||
* `Step Into` is now using `Alt + F11` instead of `F11` on Windows browsers
|
||||
Due to overlap with existing browser keybindings, we have changed the following commands:
|
||||
|
||||
* **Step Over** is now using `Alt + F10` instead of `F10` on all browsers.
|
||||
* **Step Into** is now using `Alt + F11` instead of `F11` on Windows browsers.
|
||||
|
||||
## Containers (version 0.163.x)
|
||||
|
||||
|
|
|
|||
Загрузка…
Ссылка в новой задаче