June 2023 (version 1.80)
Join VS Code at Microsoft Ignite or catch the sessions online. A year of VS Code, wrapped. Explore the highlights. June 2023 (version 1.80) Update 1.80.1 : The update addresses these issues . Update 1.80.2 : The update addresses this security issue . Downloads for 1.80.2 Windows x64 Arm64 macOS Universal Intel Apple silicon Linux .deb .rpm .tar.gz Arm instructions Snap Welcome to the June 2023 release of Visual Studio Code.
There are many updates in this version that we hope you'll like, some of the key highlights include: Accessibility improvements - Accessible View for better screen reader support, Copilot audio cues. Better editor group and tab resizing - Set min tab size, avoid unnecessary editor group resizing. Skip subwords when expanding selection - Control whether to use camel case for selection. Terminal image support - Display images directly in the integrated terminal.
Python extensions for mypy and debugpy - For Python type checking and debugging in VS Code. Remote connections to WSL - Connect to WSL instances on remote machines using Tunnels. Preview: GitHub Copilot create workspace/notebook - Quickly scaffold projects and notebooks. New C# in VS Code documentation - Learn about C# development with the C# Dev Kit extension. If you'd like to read these release notes online, go to Updates on code.visualstudio.com .
Insiders: Want to try new features as soon as possible? You can download the nightly Insiders build and try the latest updates as soon as they are available. Accessibility Accessible View A new command Open Accessible View ( ⌥F2 (Windows Alt+F2 , Linux Shift+Alt+F2 ) ) allows screen reader users to inspect content character by character, line by line. Invoke this when a hover or chat panel response is focused. Accessibility help improvements A new command Open Accessibility Help ( ⌥F1 (Windows Alt+F1 , Linux Shift+Alt+F1 ) ) opens a help menu based on the current context.
It currently applies to the editor, terminal, notebook, chat panel, and inline chat features. Disable the accessibility help menu hint and open additional documentation, if any, from within the help menu. Accessibility help for notebooks A new accessibility help menu was added for notebooks to provide information about the editor layout and navigating and interacting with the notebook. Chat audio cues There are now audio cues for the GitHub Copilot chat experience and can be enabled via audioCues.chatRequestSent , audioCues.chatResponsePending , and audioCues.chatResponseReceived .
Chat accessibility improvements Chat responses are provided to screen readers as soon as they come in and the inline and chat panel accessibility help menus contain more detailed information about what to expect and how to interact with each feature. Settings editor alt text improvements The Settings editor (accessible through the Preferences: Open Settings (UI) command) is now less verbose when navigating with a screen reader.
In particular, the Settings scope switcher announces the actual name of the scope rather than a file path, and the settings description alt text has been cleaned up to not include raw Markdown formatting. Workbench Auto playing and looping for previewed videos You can now enable video autoplaying and looping for the built-in video file preview. The relevant settings are: mediaPreview.video.autoPlay — Enable video autoplay.
Autoplayed videos are automatically muted. mediaPreview.video.loop — Enable video looping. These settings are off by default. More help when editor is readonly With the introduction of readonly mode in VS Code last milestone, editors can be readonly due to workspace configuration. This milestone, we enhanced the notification message in the editor when you try to type in a readonly editor and in some cases provide a link to change the files.readonly settings.
Default file dialog location A new setting files.dialog.defaultPath can configure the default location that file dialogs (for example when opening or saving files or folders) should show when they open. This default is used only as a fallback when no other location is known, for example in empty VS Code windows. Disable maximizing editor groups on tab double click A new setting workbench.editor.doubleClickTabToToggleEditorGroupSizes disables toggling the size of an editor group from maximized to restored when double-clicking on a tab of that group.
Control minimal width of fixed width tabs A new setting workbench.editor.tabSizingFixedMinWidth controls the minimum size of a tab when workbench.editor.tabSizing is set to fixed . Fixed tab widths are explained in more detail in the 1.79 release notes . Editor group split sizing changed to 'auto' A new value for the workbench.editor.splitSizing setting called auto is the new default. In this mode, splitting an editor group distributes the available size evenly to all editor groups only if none of the editor groups has been resized.
Otherwise, the space of the split editor group is divided in half and placed in the new editor group. The intent of this change is to not break layouts that you have created when you split, but still preserve the previous default behavior of distributing the size evenly otherwise. Search .gitignore exclude behavior When search.useIgnoreFiles is set to true , the workspace's .gitignore is now respected regardless of whether the workspace is initialized as a Git repository or not.
Max height for comments The setting comments.maxHeight lets you disable the max height restriction on the comments, such as those displayed for pull requests when using the GitHub Pull Requests and Issues extension. Troubleshoot issues in VS Code There is a new command Help: Troubleshoot Issue in the Command Palette to help you troubleshoot an issue in VS Code. The launched workflow helps you identify the cause for an issue using a special Troubleshoot profile and the extension bisect feature of VS Code.
Extension bisect will enable and disable your installed extensions in a binary search while you indicate whether the issue reproduces or not. This narrows down the extension causing the issue and helps you provide the right information when reporting an issue. Disable Chromium sandbox If you have scenarios where launching VS Code desktop as an elevated user is unavoidable, for example you are launching VS Code with sudo on Linux or as administrator in an AppLocker environment on Windows, then you need to launch VS Code with the --no-sandbox --disable-gpu-sandbox command line options to have the application work as expected.
Based on the feedback in issue #184687 , there are now two new settings to make it easier when you need to disable the Chromium sandbox: A new command line option --disable-chromium-sandbox to disable the Chromium sandbox for all processes in the application. This new option can be used as a replacement for --no-sandbox --disable-gpu-sandbox . This option applies to any new process sandboxes that might be added by the runtime in future releases.
To persist disabling the Chromium sandbox across launches, do the following: Open the Command Palette ( ⇧⌘P (Windows, Linux Ctrl+Shift+P ) ). Run the Preferences: Configure Runtime Arguments command. This command opens a argv.json file to configure runtime arguments. You might see some default arguments there already. Add "disable-chromium-sandbox": true . Restart VS Code. Note: Do not use this setting unless you are seeing issues!
Editor Skip subword when shrinking and expanding selection The Expand and Shrink Selection commands can now be configured to skip subwords. This is done via the editor.smartSelect.selectSubwords setting. By default, subwords are selected but this can now be disabled. true -> Co | deEditor selects [Code]Editor , then [CodeEditor] false -> Co | deEditor selects [CodeEditor] This setting comes in handy when you use expand and shrink selection frequently with multiple cursors and on heterogeneous words.
Improved Emmet support for CSS modules
The rest of this page is on the live site.