Edits after checking links
This commit is contained in:
Родитель
0a38b1d092
Коммит
cc3fbad52d
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:25b2f5d9899ce6d59f3f88c6d04b99ad84354b5eabb32df3a67af2629beeb978
|
||||
size 44771
|
|
@ -18,7 +18,7 @@ Welcome to the Feburary 2023 release of Visual Studio Code. There are many updat
|
|||
* **[Moveable Explorer view](#moveable-explorer-view)** - Place the Explorer in the secondary side bar or a panel.
|
||||
* **[Notebook kernel MRU list](#kernel-picker-default-mode-mru)** - Find and select recently used notebook kernels.
|
||||
* **[Markdown header link suggestions](#markdown-workspace-header-link-completions)** - Easily link to headers in files across your workspace.
|
||||
* **[Remote Development usability](#remote-indicator)** - New keyboard shortcut, streamlined remote options list.
|
||||
* **[Remote Development usability](#remote-menu)** - New keyboard shortcut, streamlined remote options list.
|
||||
* **[New Git/GitHub topics](#git-and-github-documentation)** - Articles for beginner and advanced Git source control users.
|
||||
* **[Jupyter IPyWidgets 8 support](#ipywidgets)** - Use the latest IPyWidgets version in your Jupyter notebooks.
|
||||
* **[Python pytest IntelliSense](#improved-intellisense-support-for-pytest)** - Completions for pytest fixtures and parameter arguments.
|
||||
|
@ -85,7 +85,7 @@ You can now create and customize profiles including remote extensions and switch
|
|||
|
||||
### Profiles documentation
|
||||
|
||||
Check out the new [Profiles](https://code.visualstudio.com/docs/editor/profiles) topic if you'd like to learn more about profiles and scenarios when they are useful. This article goes into detail on how to create, modify, share, and reuse profiles.
|
||||
Check out the new [Profiles in Visual Studio Code](https://code.visualstudio.com/docs/editor/profiles) topic if you'd like to learn more about profiles and scenarios when they are useful. This article goes into detail on how to create, modify, share, and reuse profiles.
|
||||
|
||||
## Workbench
|
||||
|
||||
|
@ -93,6 +93,12 @@ Check out the new [Profiles](https://code.visualstudio.com/docs/editor/profiles)
|
|||
|
||||
Most views and view containers within VS Code are moveable except for a few built-in ones. In this release, the Explorer view container (`kb(workbench.view.explorer)`) is now moveable and can be placed into the secondary side bar or the bottom panel to allow for further workbench customization.
|
||||
|
||||
Below the File Explorer view has been moved to the Panel area.
|
||||
|
||||
![Explorer moved to the panel area](images/1_76/file-explorer-panel.png)
|
||||
|
||||
If you'd like to reset all views back to the default layout, you can run **Views: Reset View Locations** from the Command Palette.
|
||||
|
||||
### Fixed-width centered layout
|
||||
|
||||
The centered layout **View: Toggle Central Layout** command (`workbench.action.toggleCenteredLayout`) now has a fixed-width layout option. This option is enabled with the new `workbench.editor.centeredLayoutFixedWidth` setting. When enabled and centered layout is active, the editor will be centered and attempt to maintain its width across window and panel resizes.
|
||||
|
@ -113,6 +119,8 @@ You can now configure the default log level for VS Code or for an extension from
|
|||
|
||||
![Default log level](images/1_76/default-log-level.png)
|
||||
|
||||
Selecting an extension will display the same log level dropdown as for the default log level.
|
||||
|
||||
### Verified publisher domain in Extension editor
|
||||
|
||||
The Extension editor now displays the verified publisher domain next to the verified indicator.
|
||||
|
@ -142,19 +150,19 @@ Whether you are new to source control or an experienced Git user, you can learn
|
|||
* [Using Git source control in VS Code](https://code.visualstudio.com/docs/sourcecontrol/overview) - An overview of VS Code's Git integration features.
|
||||
* [Introduction to Git](https://code.visualstudio.com/docs/sourcecontrol/intro-to-git) - Beginner level Git operations in VS Code.
|
||||
* [Working with GitHub](https://code.visualstudio.com/docs/sourcecontrol/github) - Move your code to [GitHub](https://github.com) to share and collaborate with others.
|
||||
* [Frequently Asked Questions](https://code.visualstudio.com/docs/sourcecontrol/faq) - Answers to common scenarios and gotchas.
|
||||
* [Frequently Asked Questions](https://code.visualstudio.com/docs/sourcecontrol/faq) - Get help for common scenarios and gotchas.
|
||||
|
||||
## Notebooks
|
||||
|
||||
### Notebook renderer performance diagnostics
|
||||
|
||||
When running notebook cells, some notebook output renderers may take a long time to render. To help identify these renderers, we've added some diagnostics to the hover in the notebook cell Status bar. This view shows the time it took to for each renderer to execute and the total execution time. Additionally, the links in the hover will open the issue reporter with the renderer's name and execution time pre-filled so that you can easily file an issue if you find the renderer is taking too long to execute.
|
||||
When running notebook cells, some notebook output renderers may take a long time to render. To help identify these renderers, we've added diagnostics to the hover in the notebook cell Status bar. This view shows the time it took for each renderer to execute and the total execution time. Additionally, the links in the hover will open the issue reporter with the renderer's name and execution time pre-filled so that you can easily file an issue if you find the renderer is taking too long to execute.
|
||||
|
||||
![image showing the cell Status bar hover with renderer execution times](images/1_76/notebook-renderer-performance-diagnostics.png)
|
||||
|
||||
### Kernel picker default mode: MRU
|
||||
|
||||
The kernel picker now shows the most recently used (MRU) kernel by default. This is a change from the previous behavior, which was to show all available kernels to users. You can still see all available kernels by a secondary picker **Select Another Kernel...**, which will group all kernels by their source (for example: Jupyter Kernel, Python Environment, etc.) when you have latest [Jupyter](https://marketplace.visualstudio.com/items?itemName=ms-toolsai.jupyter) and [Python](https://marketplace.visualstudio.com/items?itemName=ms-python.python) extensions installed.
|
||||
The kernel picker now shows the most recently used (MRU) kernel by default. This is a change from the previous behavior, which was to show all available kernels. You can still see all kernels by a secondary picker **Select Another Kernel...**, which will group kernels by their source (for example: Jupyter Kernel, Python Environment, etc.) when you have latest [Jupyter](https://marketplace.visualstudio.com/items?itemName=ms-toolsai.jupyter) and [Python](https://marketplace.visualstudio.com/items?itemName=ms-python.python) extensions installed.
|
||||
|
||||
![Notebook Kernel Picker](images/1_75/noterbook-kernel-picker.gif)
|
||||
|
||||
|
@ -178,7 +186,9 @@ Accept one of these completions to insert the full link to that header, even if
|
|||
|
||||
![Adding a link to the selected header in another file](images/1_76/md-workspace-header-suggestion-insert.png)
|
||||
|
||||
You can configure if/when workspace header completions show with the `markdown.suggest.paths.includeWorkspaceHeaderCompletions` setting. Valid setting values are:
|
||||
You can configure if/when workspace header completions show with the **Markdown > Suggest > Paths: Include Workspace Header Completions** setting (`markdown.suggest.paths.includeWorkspaceHeaderCompletions`).
|
||||
|
||||
Valid setting values are:
|
||||
|
||||
* `onDoubleHash` (the default) - Show workspace header completions only after you type `##`.
|
||||
* `onSingleOrDoubleHash` - Show workspace header completions after you type `#` or `##`.
|
||||
|
@ -204,7 +214,7 @@ You can learn about new extension features and bug fixes in the [Remote Developm
|
|||
|
||||
### Remote menu
|
||||
|
||||
This milestone we made several usability improvements to the remote menu, previously accessible by clicking on the remote indicator in the lower left of the Status bar:
|
||||
This milestone we made several usability improvements to the remote menu, accessible by clicking on the remote indicator in the lower left of the Status bar:
|
||||
|
||||
1. There is now a default keybinding to open the remote menu: `kb(workbench.action.remote.showMenu)`.
|
||||
|
||||
|
@ -263,7 +273,7 @@ Auto-selecting a kernel for the [Interactive Window](https://code.visualstudio.c
|
|||
|
||||
The [Pylance](https://marketplace.visualstudio.com/items?itemName=ms-python.vscode-pylance) extension now has powerful features that can help you work more efficiently and effectively when writing and maintaining clear, concise, and easy to understand tests with [pytest](https://docs.pytest.org):
|
||||
|
||||
* Support for completions, **Go to Definition**, **Find All References**, and **Rename Symbol** (F2) for pytest fixtures and parameterized arguments.
|
||||
* Support for completions, **Go to Definition**, **Find All References**, and **Rename Symbol** (`kb(editor.action.rename)`) for pytest fixtures and parameterized arguments.
|
||||
* Type annotation support for pytest parameters through inlay hints (enabled by the ``"python.analysis.inlayHints.pytestParameters"`` setting) and through Code Actions.
|
||||
* Type inference of parameterized pytest arguments, based on the parameter values provided to the decorator.
|
||||
|
||||
|
@ -293,6 +303,8 @@ Global search now supports showing results from notebooks as they would be displ
|
|||
Sorry, your browser doesn't support HTML 5 video.
|
||||
</video>
|
||||
|
||||
_Theme: [Community Material Theme](https://marketplace.visualstudio.com/items?itemName=Equinusocio.vsc-community-material-theme) (preview on [vscode.dev](https://vscode.dev/theme/Equinusocio.vsc-community-material-theme))_
|
||||
|
||||
### Asynchronous tokenization
|
||||
|
||||
This release ships the experimental asynchronous tokenization feature. This feature allows the editor to tokenize documents in a separate web worker, which can improve the responsiveness of the editor when the document is large.
|
||||
|
@ -306,7 +318,7 @@ This update includes support for the upcoming TypeScript 5.0 release. See the [T
|
|||
* New `switch` and `case` completions help you fill in both sections of `switch` statements more quickly.
|
||||
* Work on enabling project wide IntelliSense on [github.dev](https://github.dev) and [vscode.dev](https://vscode.dev).
|
||||
|
||||
To start using the TypeScript 5.0 nightly builds, install the [TypeScript Nightly](https://marketplace.visualstudio.com/items?itemName=ms-vscode.vscode-typescript-next) extension or install the latest [VS Code 1.76+ Insiders build](/insiders).
|
||||
To start using the TypeScript 5.0 nightly builds, install the [TypeScript Nightly](https://marketplace.visualstudio.com/items?itemName=ms-vscode.vscode-typescript-next) extension or install the latest [VS Code 1.76+ Insiders build](https://code.visualstudio.com/insiders).
|
||||
|
||||
## Extension authoring
|
||||
|
||||
|
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:cdcaa5ceccca717a96b340b33979e379ff25099cd3614b64af52846f6c48b767
|
||||
size 121729
|
||||
oid sha256:94269889f19918b4cc51b7ac7f4d842b8833ddd43422f10aa34e019b04c81cc2
|
||||
size 113697
|
||||
|
|
Загрузка…
Ссылка в новой задаче