diff --git a/docs/languages/markdown.md b/docs/languages/markdown.md index 12337dc63..76570187a 100644 --- a/docs/languages/markdown.md +++ b/docs/languages/markdown.md @@ -69,17 +69,17 @@ Accept one of these completions to insert the full link to that header, even if You can configure if/when workspace header completions show with the `markdown.suggest.paths.includeWorkspaceHeaderCompletions` setting. Valid setting values are: -- `onDoubleHash` (the default) — Show workspace header completions only after you type `##`. -- `onSingleOrDoubleHash` — Show workspace header completions after you type `#` or `##`. -- `never` — Never show workspace header completions. +* `onDoubleHash` (the default) — Show workspace header completions only after you type `##`. +* `onSingleOrDoubleHash` — Show workspace header completions after you type `#` or `##`. +* `never` — Never show workspace header completions. Keep in mind that finding all headers in the current workspace can be expensive, so there may be a slight delay the first time they are requested, especially for workspaces with lots of Markdown files. ### Inserting images and links to files -Use the `Markdown: Insert Image from Workspace` command to quickly add an image in the current markdown file. This command lets you select one or more images to insert from the current workspace. +Use the **Markdown: Insert Image from Workspace** command to quickly add an image in the current markdown file. This command lets you select one or more images to insert from the current workspace. -Similarly, the `Markdown: Insert Link to File in Workspace` command inserts a link to one or more files that you select in the current workspace. +Similarly, the **Markdown: Insert Link to File in Workspace** command inserts a link to one or more files that you select in the current workspace. You can also insert images and links by dragging and dropping. To start, drag a file from VS Code's explorer over your Markdown code and then hold down `kbstyle(Shift)` to start dropping it into the file. The preview cursor shows where it will be inserted when you drop it. @@ -153,9 +153,9 @@ You can also use `kb(editor.action.rename)` on: With automatic Markdown link updating, VS Code will automatically update Markdown links whenever a linked to file is moved or renamed. You can enable this feature with the `markdown.updateLinksOnFileMove.enabled` setting. Valid setting values are: -- `never` (the default) — Don't try to update links automatically. -- `prompt` — Confirm before updating links. -- `always` — Update links automatically without confirmation. +* `never` (the default) — Don't try to update links automatically. +* `prompt` — Confirm before updating links. +* `always` — Update links automatically without confirmation. Automatic link updating detects renames of Markdown files, images, and directories. You can enable it for additional file types with `markdown.updateLinksOnFileMove.include`. diff --git a/release-notes/v1_76.md b/release-notes/v1_76.md index 0fa67f385..12334f52b 100644 --- a/release-notes/v1_76.md +++ b/release-notes/v1_76.md @@ -82,7 +82,7 @@ Check out the new [Profiles](https://code.visualstudio.com/docs/editor/profiles) ### Moveable Explorer view -Most views and view containers within VS Code are moveable with the exception of a few built-in ones. This release, the Explorer view container (`kb(workbench.view.explorer)`) has been made moveable and can now be moved into the secondary side bar or the bottom panel to allow for further workbench customization. +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. ### Fixed-width centered layout @@ -90,7 +90,7 @@ The centered layout **View: Toggle Central Layout** command (`workbench.action.t ### Multiple quick diffs -With the introduction of the proposed [multiple quick diff API](https://github.com/microsoft/vscode-docs/blob/main/release-notes/v1_75.md#quick-diff), multiple extensions can provide a quick diff. When there are multiple quick diffs in a file, you'll now see a dropdown to choose which diff base to view: +With the introduction of the proposed [multiple quick diff API](https://code.visualstudio.com/updates/v1_75#_quick-diff), multiple extensions can provide a quick diff. When there are multiple quick diffs in a file, you'll now see a dropdown to choose which diff base to view: ![Multiple quick diffs](images/1_76/multiple-quick-diff.png) @@ -98,17 +98,17 @@ With the introduction of the proposed [multiple quick diff API](https://github.c The **Comments** view has a new **Expand All** command to go with the existing **Collapse All**. The gutter icon for unresolved comments is now the same icon that is used in the **Comments** view. -### Configure Default Log Level +### Configure default log level You can now configure the default log level for VS Code or for an extension from the **Developer: Set Log Level...** command. This is persisted across restarts and is synced across machines. -![Default Log Level](images/1_76/default-log-level.png) +![Default log level](images/1_76/default-log-level.png) -### Verified Publisher Domain in Extension Editor +### Verified publisher domain in Extension editor -The extension editor now displays the verified publisher domain next to the veirified indicator. +The Extension editor now displays the verified publisher domain next to the verified indicator. -![Verified Publisher Domain](images/1_76/verified-publisher-domain.png) +![Prettier extension in the extension editor displaying verified publisher domain prettier.io](images/1_76/verified-publisher-domain.png) ## Editor @@ -120,8 +120,6 @@ It is now possible to sort JSONC (JSON documents with comments) files by key. To In this iteration, we changed the behavior when both `editor.language.brackets` and `editor.language.colorizedBracketPairs` are configured. Before, setting `editor.language.colorizedBracketPairs` would override `editor.language.brackets` for bracket matching (as both use the same [bracket pair tree](https://code.visualstudio.com/blogs/2021/09/29/bracket-pair-colorization#_the-basic-algorithm)). Now, the union of both settings is used for bracket matching, but only brackets configured in `editor.language.colorizedBracketPairs` are colorized. -## Terminal - ## Source Control ### Git @@ -130,7 +128,7 @@ VS Code has adopted a new Git grammar, which provides syntax highlighting for Gi ### New documentation -Whether you are new to source control or an experienced Git user, you can learn more about VS Code's Git integration in the [Source Control](https://code.visualstudio.com/docs/sourcecontrol/overview) section of our documentation. Topics include: +Whether you are new to source control or an experienced Git user, you can learn more about VS Code's Git integration in the [Source Control](https://code.visualstudio.com/docs/sourcecontrol/overview) section of our documentation. Articles include: * [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. @@ -147,19 +145,17 @@ When running notebook cells, some notebook output renderers may take a long time ### Kernel picker default mode: MRU -The kernel picker now shows the most recently used 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 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. ![Notebook Kernel Picker](images/1_75/noterbook-kernel-picker.gif) -### Better link support for builtin Error Renderer +### Better link support for built-in error renderer -The builtin Error Renderer now supports links to files and line numbers. This allows you to click on a file path in the error message and open the file in the editor. +The built-in error renderer now supports links to files and line numbers. This allows you to click on a file path in the error message and open the file in the editor. -Jupyter extension's Error Renderer is now removed in favor of the builtin Error Renderer. +Jupyter extension's error renderer is now removed in favor of the built-in error renderer. -![Notebook builtin error renderer](images/1_76/notebook-error-renderer.gif) - -## Debugging +![Notebook built-in error renderer](images/1_76/notebook-error-renderer.gif) ## Languages @@ -175,29 +171,25 @@ Accept one of these completions to insert the full link to that header, even if You can configure if/when workspace header completions show with the `markdown.suggest.paths.includeWorkspaceHeaderCompletions` setting. Valid setting values are: -- `onDoubleHash` (the default) — Show workspace header completions only after you type `##`. -- `onSingleOrDoubleHash` — Show workspace header completions after you type `#` or `##`. -- `never` — Never show workspace header completions. +* `onDoubleHash` (the default) - Show workspace header completions only after you type `##`. +* `onSingleOrDoubleHash` - Show workspace header completions after you type `#` or `##`. +* `never` - Never show workspace header completions. Keep in mind that finding all headers in the current workspace can be expensive, so there may be a slight delay the first time they are requested, especially for workspaces with lots of Markdown files. ### Configure preferred file extension style for Markdown links -The new `markdown.preferredMdPathExtensionStyle` setting configures if VS Code prefers using file extensions for links to Markdown files. This preference is used for language tools such as [path completions](/docs/languages/markdown.md#path-completions) and [link renames](/docs/languages/markdown.md#rename-headers-and-links). + +The new `markdown.preferredMdPathExtensionStyle` setting configures if VS Code prefers using file extensions for links to Markdown files. This preference is used for language tools such as [path completions](https://code.visualstudio.com/docs/languages/markdown#_path-completions) and [link renames](https://code.visualstudio.com/docs/languages/markdown#_rename-headers-and-links). Valid setting values are: -- `auto` — Try to preserve the existing style of the file extension. -- `includeExtension` — Include the trailing `.md` in the link. -- `removeExtension` — Remove the trailing `.md` from the link. - - -## Extensions +* `auto` - Try to preserve the existing style of the file extension. +* `includeExtension` - Include the trailing `.md` in the link. +* `removeExtension` - Remove the trailing `.md` from the link. ## Remote Development -The [Remote Development extensions](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.vscode-remote-extensionpack), allow you to use a [Dev Container](https://code.visualstudio.com/docs/devcontainers/containers), remote machine via SSH or [Remote Tunnels](https://code.visualstudio.com/docs/remote/tunnels), or the [Windows Subsystem for Linux](https://learn.microsoft.com/windows/wsl) (WSL) as a full-featured development environment. - - +The [Remote Development extensions](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.vscode-remote-extensionpack), allow you to use a [Dev Container](https://code.visualstudio.com/docs/devcontainers/containers), remote machine via SSH or [Remote Tunnels](https://code.visualstudio.com/docs/remote/tunnels), or the [Windows Subsystem for Linux](https://learn.microsoft.com/windows/wsl) (WSL) as a full-featured development environment. You can learn about new extension features and bug fixes in the [Remote Development release notes](https://github.com/microsoft/vscode-docs/blob/main/remote-release-notes/v1_76.md). @@ -254,7 +246,7 @@ The [Jupyter](https://marketplace.visualstudio.com/items?itemName=ms-toolsai.jup #### Interactive Window kernel selection -Auto-selecting a kernel for the Interactive Window was modified to work better with the new kernel picker UI. The current active interpreter is used unless another kernel was previously chosen for an Interactive Window in that workspace, in which case the previously selected kernel is used. +Auto-selecting a kernel for the [Interactive Window](https://code.visualstudio.com/docs/python/jupyter-support-py) was modified to work better with the new kernel picker UI. The current active interpreter is used unless another kernel was previously chosen for an Interactive Window in that workspace, in which case the previously selected kernel is used. ### Python @@ -317,7 +309,7 @@ This iteration, we introduced support for links in `InputBox` prompts and valida [link text](link target) ``` -The link target can be a URL or a command ID. When the user clicks on the link, the link target will be opened in the browser or executed as a command, respectively. +The link target can be a URL or a command ID. When the user clicks on the link, the link target is opened in the browser or executed as a command, respectively. Example: @@ -347,19 +339,19 @@ This behavior works for both `showInputBox` and `createInputBox` APIs. ### Information diagnostic for * activation event -When an extension uses the `*` (star) activation event, it will be activated while VS Code is in the process of starting up. This can cause a delay in the startup time of VS Code. To help extension authors understand the impact of using the `*` activation event, we have added an information diagnostic that will be shown when an extension uses the `*` activation event. The diagnostic will be shown in the Problems view and will also be shown in the extension editor: +When an extension uses the `*` (star) activation event, it is activated while VS Code is in the process of starting up. This can cause a delay in the startup time of VS Code. To help extension authors understand the impact of using the `*` activation event, we have added an information diagnostic that is shown when an extension uses the `*` activation event. The diagnostic is displayed in the Problems view and is also visible in the extension editor: ![diagnostic for * activation event](images/1_76/star-activation.png) -For more information about `*` (star) activation, please see the [Activation Events](https://code.visualstudio.com/api/references/activation-events#Start-up) documentation. +For more information about `*` (star) activation, you can read the [Activation Events](https://code.visualstudio.com/api/references/activation-events#Start-up) documentation. ### Upcoming changes in when clause contexts parsing -[When clauses](https://code.visualstudio.com/api/references/when-clause-contexts) used in extension manifest files (i.e., `package.json`) allow to selectively enable and disable various extension contributions such as commands and UI elements (e.g., menus or views). The next VS Code release is planned to include a new parser of when clauses. The new parser will offer more features and correctness, but it will also enforce stricter rules for when clauses that may result in some breakages for the existing when clauses. Please, see this [issue](https://github.com/microsoft/vscode/issues/175540) to learn more about the breakages and new features. You are also encouraged to subscribe to that issue for updates on the new parser, including new features, breakages, and migration guideline. +[When clauses](https://code.visualstudio.com/api/references/when-clause-contexts) used in extension manifest files (`package.json`) allow to selectively enable and disable various extension contributions such as commands and UI elements (for example, menus or views). The next VS Code release is planned to include a new parser of when clauses. The new parser offers more features and correctness, but it also enforces stricter rules for when clauses that may result in some breakages for the existing when clauses. Review [issue #175540](https://github.com/microsoft/vscode/issues/175540) to learn more about the breakages and new features. You are also encouraged to subscribe to that issue for updates on the new parser, including new features, breakages, and migration guideline. ## Language Server Protocol -New versions of the LSP client (8.1.0) and server (8.1.0) npm packages have been released. They are bug fix releases (mainly to address problems with request ordering problem when using full text document sync) and contain API additions for custom message handling to the JSON-RPC library. +New versions of the [Language Server Protocol](https://microsoft.github.io/language-server-protocol) (LSP) client (8.1.0) and server (8.1.0) npm packages have been released. They are bug fix releases (mainly to address problems with request ordering problem when using full text document sync) and contain API additions for custom message handling to the JSON-RPC library. ## Proposed APIs @@ -410,15 +402,15 @@ We think that this API is a good addition to the Quick Pick API and we are looki ## Engineering -### More Electron `UtilityProcess` adoption +### More Electron UtilityProcess adoption -As part of our [process sandbox journey](https://code.visualstudio.com/blogs/2022/11/28/vscode-sandbox) we want to make sure that there is no more node.js enabled browser window in our application. This milestone we started to convert our last remaining process from a hidden node.js browser window to a Electron [`UtilityProcess`](https://www.electronjs.org/docs/latest/api/utility-process). As part of this work, the file watcher process had to move out into its own utility process as well. +As part of our [process sandbox journey](https://code.visualstudio.com/blogs/2022/11/28/vscode-sandbox), we want to make sure that there are no more Node.js enabled browser windows in our application. This milestone we started to convert our last remaining process from a hidden Node.js browser window to an Electron [UtilityProcess](https://www.electronjs.org/docs/latest/api/utility-process). As part of this work, the file watcher process had to move out into its own utility process as well. -A new setting `window.experimental.sharedProcessUseUtilityProcess` allows to enable the use of `UtilityProcess` and we plan to make this the default in the next release. +A new setting `window.experimental.sharedProcessUseUtilityProcess` enables the use of `UtilityProcess` and we plan to make this the default in the next release. ### macOS 10.11 and 10.12 support has ended -As mentioned in our [v1.75 release notes](https://code.visualstudio.com/updates/v1_75#_eol-warning-for-macos-1011-and-1012), `v1.76` is the last release that will be supported to run on macOS 10.11 (OS X El Capitan) and 10.12 (macOS Sierra). Please refer to our [FAQ](https://code.visualstudio.com/docs/supporting/faq#_can-i-run-vs-code-on-old-macos-versions) for additional information. +As mentioned in our [1.75 release notes](https://code.visualstudio.com/updates/v1_75#_eol-warning-for-macos-1011-and-1012), `1.76` is the last release that will support macOS 10.11 (OS X El Capitan) and 10.12 (macOS Sierra). Refer to our [FAQ](https://code.visualstudio.com/docs/supporting/faq#_can-i-run-vs-code-on-old-macos-versions) for additional information. ## Notable fixes @@ -429,6 +421,18 @@ As mentioned in our [v1.75 release notes](https://code.visualstudio.com/updates/ Last but certainly not least, a big _**Thank You**_ to the contributors of VS Code. +### Issue tracking + +Contributions to our issue tracking: + +* [@gjsjohnmurray (John Murray)](https://github.com/gjsjohnmurray) +* [@IllusionMH (Andrii Dieiev)](https://github.com/IllusionMH) +* [@ArturoDent (ArturoDent)](https://github.com/ArturoDent) +* [@starball5 (starball)](https://github.com/starball5) +* [@tjx666 (余腾靖)](https://github.com/tjx666) + +### Pull requests + Contributions to `vscode`: * [@davidnx](https://github.com/davidnx): Escape special glob chars when using "Find in Folder" [PR #166318](https://github.com/microsoft/vscode/pull/166318) @@ -474,19 +478,5 @@ Contributions to `monaco-editor`: * [@mathedu4all (Bao Hongchang)](https://github.com/mathedu4all): Update api doc url in README.md [PR #3550](https://github.com/microsoft/monaco-editor/pull/3550) -### Issue tracking - -Contributions to our issue tracking: - -* [@gjsjohnmurray (John Murray)](https://github.com/gjsjohnmurray) -* [@IllusionMH (Andrii Dieiev)](https://github.com/IllusionMH) -* [@ArturoDent (ArturoDent)](https://github.com/ArturoDent) -* [@starball5 (starball)](https://github.com/starball5) -* [@tjx666 (余腾靖)](https://github.com/tjx666) - -### Pull requests - -Contributions to `vscode`: - diff --git a/remote-release-notes/v1_76.md b/remote-release-notes/v1_76.md index f52985b53..989b0d871 100644 --- a/remote-release-notes/v1_76.md +++ b/remote-release-notes/v1_76.md @@ -1,7 +1,5 @@ # February 2023 (version 1.76) -## Core - ## Dev Containers ### Note on bind mount performance @@ -30,7 +28,4 @@ The deprecated legacy features are: ### Download WSL server build in the background -When VS Code detects a new update and donwloads it in the background, the WSL extension now also downloads the matching server build. -When the VS Code update is applied, VS Code is able to open WSL windows without a extra download. This will come handy when the update is applied while the machine has no connection to the internet. - -## SSH +When VS Code Desktop detects a new update and downloads it in the background, the WSL extension now also downloads the matching server build. When the VS Code update is applied, VS Code is able to open WSL windows without a extra download. This will come handy when the update is applied while the machine has no connection to the internet.