May 2023 (version 1.79)
Join VS Code at Microsoft Ignite or catch the sessions online. A year of VS Code, wrapped. Explore the highlights. May 2023 (version 1.79) Update 1.79.1 : The update addresses this security issue . Update 1.79.2 : The update addresses these issues . Downloads for 1.79.2 Windows x64 Arm64 macOS Universal Intel Apple silicon Linux .deb .rpm .tar.gz Arm instructions Snap Welcome to the May 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: Read-only mode - Mark specific files and folders in your workspace as read-only. 'Paste as' options - Choose how you'd like item links pasted into the editor. Automatic copy of external files - Drag or paste to Markdown adds new files to your workspace. Default Git repo branch name - Use "main" as the default or override via a user setting.
Notebooks rich content search - Search based on Notebook output or filter on cell type. Linked editing for JSX tags - Simultaneously change opening and closing JSX tags. Preview: GitHub Copilot Chat improvements - Easily manage your chat session history. Inline chat "live preview." VS Code at Microsoft Build 2023 - Catch up on the sessions in the YouTube playlist. 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 Verbosity settings Additional accessibility.verbosity settings have been added to inform screen reader users how to interact with features when they are focused. For GitHub Copilot , there are hints describing how to access the accessible help menus for the Copilot chat view and in editor code chat via: accessibility.verbosity.panelChat accessibility.verbosity.inlineChat These help menus provide information about what to expect, how to navigate from the input box to other elements, and more.
Other new verbosity settings provide information for specific VS Code UI: accessibility.verbosity.keybindingsEditor - when in the Keyboard Shortcuts editor. accessibility.verbosity.notebook - when in a notebook. The accessibility.verbosity settings are enabled by default (set to 'true') but you can silence them individually. Settings editor VoiceOver on macOS now reads the descriptions of enum setting options in the Settings editor.
Try it out with enum settings such as files.autoSave and editor.accessibilitySupport . Workbench Readonly mode In some development scenarios, it can be helpful to explicitly mark some of a workspace's folders or files as read-only. For example, if the folder or file contents is being managed by a different process (such as the node_modules folder that is managed by Node.js package manager), marking them are read-only can avoid inadvertent changes.
For this use case, there are new settings to mark file paths as read-only in the Explorer and in text and notebook editors: files.readonlyInclude - Paths or glob patterns to make a file read-only if matching. files.readonlyExclude - Paths or glob patterns to skip files from being read-only when they match files.readonlyInclude . files.readonlyFromPermissions - Whether a file that has no write-permissions on disk should be read-only.
According to the rules of the settings, if a path is considered to be read-only, you cannot modify it from the Explorer (for example, delete it) and the text or notebook editor is read-only. For more ad-hoc toggling of the read-only mode, there are new commands to change the mode for the current session only, overruling your setting configurations: Set Active Editor Readonly in Session - Mark active editor read-only. Set Active Editor Writeable in Session - Mark active editor writeable.
Toggle Active Editor Readonly in Session - Toggle between read-only and writeable. Reset Active Editor Readonly in Session - Reset the session state. Windows UNC host allowlist improvements As part of an important security fix , VS Code introduced an allowlist for UNC hosts. This milestone we addressed many of the usability problems reported by Windows users when they have UNC paths in their day to day work with VS Code.
Dialog improvements The confirmation dialog to allow a UNC host on startup now updates the security.allowedUNCHosts setting and adds the host when you select the checkbox. In addition, clicking the Learn More button no longer closes the dialog. New security.restrictUNCAccess setting A new setting security.restrictUNCAccess lets you disable the UNC allowlist for hosts and restore the behavior to how it was before this security fix.
We strongly advise against changing this setting, as it makes your system vulnerable again to the Information Disclosure Vulnerability . New tab sizing option fixed The workbench.editor.tabSizing setting has a new option fixed that makes each tab equal width. When space becomes limited, tabs will shrink equally up to a minimum. The new setting workbench.editor.tabSizingFixedMaxWidth sets the initial size of the tab. In this mode, when you rapidly close tabs using the mouse, the widths of tabs remain stable to allow for closing each tab by clicking onto the same point.
The width is then adjusted when you leave the mouse from the editor tab area. Network quality indication When you are connected to a remote machine, the best experience for VS Code remote editing capabilities requires a good network connection with low latency. In this milestone, we updated the remote indicator in the Status bar to give you some feedback when either latency is very high or the network connection appears to be offline.
High latency (web, desktop) We periodically measure the latency to the remote you are connected to. When a certain threshold is hit, the remote indicator updates to reflect that. Offline detection (web only) If you are using a web browser to connect to a remote and you suddenly lose internet connection, the remote indicator updates to reflect that. Continue Working On The Continue Working On feature allows you to store and retrieve working changes between VS Code development environments for the same repository, for example, when you upgrade from a local Git repository to a GitHub codespace, or when you switch between different machines for the same repository.
You can now transfer working changes between development environments for a GitHub repository even if it is configured with an HTTP remote in one environment and an SSH remote in another. Additionally, we have started to transfer additional workbench state, such as your Source Control view state preference, for a more seamless transition. Editor Paste as When pasting a file into a text editor, there are multiple ways you might want to insert it.
You may want an absolute path point to the file. You may want a path relative to the current workspace. Or you may even want something specific to the current editor's language, such as inserting a Markdown link to the file when pasting into Markdown. VS Code's new 'paste as' functionality gives you control over how the pasted content is inserted. After pasting, VS Code now shows a small 'paste as' control if there are other ways the pasted content could have been inserted: You can open the 'paste as' control by clicking on it or using the ⌘. (Windows, Linux Ctrl+. ) keyboard shortcut.
The paste selector goes away as soon as you start typing or move the cursor outside of the inserted text. You can also fully disable the drop selector control using "editor.pasteAs.showPasteSelector": "never" . When you paste content into a Markdown cell in a notebook, for example, the 'paste as' control lets you switch between: Inserting the image as an attachment Inserting a Markdown image reference Inserting a relative path (for files in the workspace) Inserting an absolute path If you prefer selecting how content in the clipboard should be pasted before actually pasting, you can instea
The rest of this page is on the live site.