Small edits
This commit is contained in:
Greg Van Liew
Родитель
eea1286d0d
Коммит
2de244b712
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:8b1bc56cb6e5e61c7a3cabe81cdf2916909abfa8798b21c78a9c8166a8cb2182
|
||||
size 19113
|
||||
oid sha256:acdd5a68d63a892575511e5c6fdb93cc85f4b99bc9fda0ccc296343c77594235
|
||||
size 15238
|
||||
|
|
|
|||
|
|
@ -35,51 +35,56 @@ To learn more about turning on and configuring Settings Sync, you can go to the
|
|||
|
||||
### Quick Open rewrite
|
||||
|
||||
Quick open (`kb(workbench.action.quickOpen)` and friends) was using a very old version of our tree widget and in this iteration was finally migrated to use our latest list control which is already being used in the rest of the VSCode UI. Visually you should not be able to tell a difference, all commands will work as before.
|
||||
The Quick Open (`kb(workbench.action.quickOpen)`) control was using an old version of our tree widget, and in this iteration it was migrated to use our latest list control, already used in the rest of the VS Code UI. Functionally, you should not be able to tell the difference, as all commands will work as before.
|
||||
|
||||
But we took the time to add some features here and there that you might find useful.
|
||||
We did take this opportunity to add some features that you might find useful.
|
||||
|
||||
|
||||
|
||||
#### Navigate from files into symbols
|
||||
**Navigate from files to symbols**
|
||||
|
||||
You can now continue to navigate into symbols of a file result simply by typing `@`. For the file that is currently selected, all symbols will appear and the editor will open in the background to reveal the active symbol.
|
||||
You can now continue to navigate to the symbols of a file result simply by typing `@`. For the file that is currently selected, all symbols will appear and the editor will open in the background to reveal the active symbol.
|
||||
|
||||
|
||||
|
||||
|
||||
#### Narrow down results by separating multiple queries with spaces
|
||||
**Filter results by separating multiple queries with spaces**
|
||||
|
||||
If you are getting too many results for a file search, simply add more patterns to search for after typing space. This for example allows you to narrow down results by folder if you type `<file name> <folder name>` one after the other.
|
||||
If you are getting too many results for a file search, you can add more search patterns after typing a space. For example, you can narrow down results by folder if you type `<file name> <folder name>` one after the other.
|
||||
|
||||
|
||||
|
||||
|
||||
**Note:** This also works for editor (`kb(workbench.action.gotoSymbol)`) and workspace (`kb(workbench.action.showAllSymbols)`) symbols picker: any filter after a space character will be used to filter by the container of that symbol.
|
||||
**Note:** This also works for the editor (`kb(workbench.action.gotoSymbol)`) and workspace (`kb(workbench.action.showAllSymbols)`) symbol picker. Any filter after a space character will be used to filter by the container of that symbol.
|
||||
|
||||
#### Input is preserved when switching providers
|
||||
**Input is preserved when switching providers**
|
||||
|
||||
When you leave quick open visible and switch to another provider (e.g. from file search to symbol search), we take whatever is typed and use it for the new provider. That for example allows to quickly use the typed input for a symbol search when it was used for a file search.
|
||||
If you leave Quick Open visible and switch to another provider (for example, from file search to symbol search), VS Code will apply whatever filter is typed and use it for the new provider. This allows you to quickly reuse the typed input for symbol search when it was previously used for a file search.
|
||||
|
||||
#### New setting to sort editor history strictly by recency
|
||||
### Sort editor history strictly by recency
|
||||
|
||||
A new setting `"search.quickOpen.history.filterSortOrder": "recency"` allows to sort editor history entries by recency even when starting to search. By default, editor history results will be sorted by relevance based on the filter pattern that was used.
|
||||
A new setting `"search.quickOpen.history.filterSortOrder": "recency"` allows you to sort editor history by the most recently opened items, even when starting to search. By default, editor history results will be sorted by relevance based on the filter pattern that was used.
|
||||
|
||||
### New setting to control height of tabs scrollbar
|
||||
### Control height of tabs scroll bar
|
||||
|
||||
A new setting `workbench.editor.titleScrollbarSizing` allows to increase the size of the scrollbar for editor tabs and breadcrumbs. Configure it to `large` for a larger scrollbar:
|
||||
A new setting `workbench.editor.titleScrollbarSizing` lets you increase the size of the scroll bar for editor tabs and breadcrumbs.
|
||||
|
||||
Configure it to `large` for a larger scroll bar:
|
||||
|
||||
|
||||
|
||||
### Web: remote indicator and navigational links
|
||||
## Contributions to extensions
|
||||
|
||||
For VSCode for web we have enabled the remote indicator. This gives you a hint to what remote environment you are connected when using the web version of VSCode and gives extensions a chance to include additional commands associated with the remote. As such, the "Open in Desktop" link was removed from the status bar and will move into the remote picker.
|
||||
### Docker
|
||||
|
||||
**Note:** we currently do not support to connect to a different remote - such as SSH, containers or WSL - from the web.
|
||||
The 1.0 version of the Microsoft [Docker](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-docker) extension is now available. The Docker extension helps you build applications using Docker containers. The extension can add required Docker files to your project, build Docker images, let you debug your app inside a container, and includes an Explorer that makes it easy to start, stop, inspect, and remove containers and images.
|
||||
|
||||
|
||||
|
||||
|
||||
In addition, a new menu location allows extensions in the web to contribute links to the hamburger menu.
|
||||
Feature highlights in 1.0 include:
|
||||
|
||||
|
||||
* Improved Dockerfile scaffolding for Python Django & Flask web frameworks.
|
||||
* A Compose.yml file is now optional when adding Docker files to a workspace.
|
||||
* Node.js, Python, and .NET Core support integrated debugging of a single service using a Dockerfile.
|
||||
* Work easily with multiple containers and images.
|
||||
|
||||
## Proposed extension APIs
|
||||
|
||||
|
|
@ -122,20 +127,21 @@ These collections are extension and workspace-specific and VS Code handles how c
|
|||
|
||||
The plan is to surface these environment modifications to the user and some indicator that allows updating or "stale" terminal environments but this is still a work in progress. You can follow the discussion in [#46696](https://github.com/Microsoft/vscode/issues/46696).
|
||||
|
||||
## Contributions to extensions
|
||||
## Browser support
|
||||
|
||||
### Docker
|
||||
### Remote indicator
|
||||
|
||||
The 1.0 version of the Microsoft [Docker](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-docker) extension is now available. The Docker extension helps you build applications using Docker containers. The extension can add required Docker files to your project, build Docker images, let you debug your app inside a container, and includes an Explorer that makes it easy to start, stop, inspect, and remove containers and images.
|
||||
When using VS Code in a browser, there is now a remote indicator. This lets you know the remote environment you are connected to and allows extensions to add additional commands associated with the remote. With this change, the **Open in Desktop** link was removed from the Status bar and will move into the remote picker.
|
||||
|
||||
|
||||
**Note:** VS Code currently does not support connecting to a different remote - such as SSH, a container, or WSL - from the browser.
|
||||
|
||||
Feature highlights in 1.0 include:
|
||||
|
||||
|
||||
* Improved Dockerfile scaffolding for Python Django & Flask web frameworks.
|
||||
* A Compose.yml file is now optional when adding Docker files to a workspace.
|
||||
* Node.js, Python, and .NET Core support integrated debugging of a single service using a Dockerfile.
|
||||
* Work easily with multiple containers and images.
|
||||
### Navigational links
|
||||
|
||||
A new menu location lets extensions running in the browser contribute links to the hamburger menu in the upper left.
|
||||
|
||||
|
||||
|
||||
## New Commands
|
||||
|
||||
|
|
|
|||
|
|
@ -0,0 +1,9 @@
|
|||
# March 2020 (version 1.44)
|
||||
|
||||
## Visual Studio Code Remote Core
|
||||
|
||||
## SSH
|
||||
|
||||
## Containers
|
||||
|
||||
## WSL
|
||||
Загрузка…
Ссылка в новой задаче