September 2021 (version 1.61)
Join VS Code at Microsoft Ignite or catch the sessions online. A year of VS Code, wrapped. Explore the highlights. September 2021 (version 1.61) Update 1.61.1 : The update addresses these issues . Update 1.61.2 : The update addresses these issues . Downloads for 1.61.2 Windows x64 Arm64 macOS Universal Intel Apple silicon Linux .deb .rpm .tar.gz Arm instructions Snap Welcome to the September 2021 release of Visual Studio Code.
There are many updates in this version that we hope you will like, some of the key highlights include: Split editors within the same group - Quickly create side-by-side editors for the same file. Locked editor groups - Select editor types to automatically lock in an editor group. Better display of deleted and readonly files - Tab decorations highlight deleted and readonly files. Bracket pair guides - Display vertical guides to link matching bracket pairs.
Fixed terminal dimensions - Set an active terminal's width and height. Jupyter Notebook improvements - Table of Contents view, full debugging support. Platform-specific extensions - Publish different extension versions for Windows, macOS, and Linux. Virtual Workspaces extension guide - Learn how to update your extension for virtual environments. Advanced container configuration - Tips, code samples, and videos to help configure development containers.
If you'd like to read these release notes online, go to Updates on code.visualstudio.com . Watch a highlight of the new features in this version in the VS Code team's release party. You can find the recording of the event on our YouTube channel. 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. Workbench Split an editor without creating a new group A new command Split in Group ( ⌘K ⇧⌘\ (Windows, Linux Ctrl+K Ctrl+Shift+\ ) ) was added to split an editor into two sides without requiring a second editor group.
This allows you to work in two editors side by side on the same file. You can also toggle the layout between splitting vertically or horizontally via the Toggle Layout button as seen in the short video. There is a new setting workbench.editor.splitInGroupLayout if you prefer the splitting to be either vertical or horizontal. There are new commands to use this feature via keybindings: workbench.action.splitEditorInGroup workbench.action.toggleSplitEditorInGroup workbench.action.joinEditorInGroup workbench.action.toggleSplitEditorInGroupLayout And to navigate between the sides: workbench.action.focusFirstSideEditor workbench.action.focusSecondSideEditor workbench.action.focusOtherSideEditor The new color sideBySideEditor.border sets the color for the border to separate one side from the other.
Locked editor groups We introduced locked editor groups last milestone as an experimental new feature. During this milestone, the settings experience was improved allowing you to easily select an editor that should lock a group automatically when opening: The setting is now called workbench.editor.autoLockGroups . Similarly, the commands related to editor group locking have been renamed and are no longer experimental: workbench.action.lockEditorGroup workbench.action.unlockEditorGroup workbench.action.toggleEditorGroupLock Indicate deleted and readonly editors via decorations Opened editors can indicate whether they are readonly or whether their associated resource has been deleted from disk.
This indication was given by appending "deleted" and/or "readonly" to the editor label, requiring quite a bit of space. VS Code now uses decorations for this purpose: Editors with deleted resource appear with strikethrough and in red. Editors with readonly resources appear with a lock icon. Split an editor into an existing group When you split an editor to the side, VS Code opens a new editor group, even if an existing group is present to the side.
However, there are times when you want to split an editor into an already existing group. To support this, new commands were added: workbench.action.splitEditorToPreviousGroup : Split into the previous group. workbench.action.splitEditorToNextGroup : Split into the next group. workbench.action.splitEditorToAboveGroup : Split into the group above the current one. workbench.action.splitEditorToBelowGroup : Split into the group below the current one. workbench.action.splitEditorToLeftGroup : Split into the group to the left of the current one. workbench.action.splitEditorToRightGroup : Split into the group to the right of the current one. workbench.action.splitEditorToFirstGroup : Split into first group. workbench.action.splitEditorToLastGroup : Split into last group.
Shorter labels for diff editors When you compare two files, the workspace relative folder path was prefixed on file names, making it hard to see the names of the files being compared. In this release, the folder is now hidden from the label, unless both file names are the same, matching the behavior for normal editor labels. If both file names are identical, a description is shown that hints at the folder difference: macOS: File menu changes On macOS, if you select the Open... menu item from the File menu, you can open both files and folders.
For new users, this may come as a surprise, and people tried to use the Open Workspace command to open a folder, when that menu item is specifically to open a .code-workspace file. To avoid confusion, we made slight adjustments to the file menu on macOS: A new entry Open Folder... opens a folder. Open Workspace... was renamed to Open Workspace from File... Telemetry settings There is a new telemetry setting, telemetry.telemetryLevel that provides higher configuration granularity and lets users select whether they want to only send error telemetry and not general usage data.
The values are on , error , and off . The values of on and error will also enable the crash reporter. The existing settings telemetry.enableTelemetry and telemetry.enableCrashReporter have been marked for deprecation in favor of the new telemetry.telemetryLevel setting but will continue to be respected. Minimap background transparency It is now possible to configure the minimap background opacity independently of the minimap text's opacity using the newly added minimap.foregroundOpacity color.
Updated Help menu items With the ongoing improvements to the getting started experience, the Help menu items were updated to more commonly used names. This is based on learnings from new users but hopefully make it easier for everyone to find help. Introductory Videos is now Video Tutorials and Interactive Playground became Editor Playground . You will find the new names in both the Help menu and the Command Palette. The Help menu also has a Show All Commands entry as an additional entry point to open the Command Palette.
Editor Bracket pair guides The editor now supports rudimentary bracket pair guides. Bracket pair guides use the same colors and the same algorithms as the bracket pair colorization feature. The bracket pair matching algorithms are described in detail in the recent "Bracket pair colorization 10,000x faster" blog post. Similar to indentation guides, the active bracket pair guide is highlighted. Bracket pair guides can be enabled by configuring the editor.guides.bracketPairs setting (defaults to false ).
We will continue iterating on this feature and explore vertical guides in the next release. Indentation guides settings The editor.renderIndentGuides and editor.highlightActiveIndentGuide settings have been deprecated in favor of editor.guides.indentation and editor.guides.highlightActiveIndentation . Source Control Publish or Sync "action button" for Git repositories The Git extension now adds a new "action" button to the Source Control view, to allow you to more easily publish or sync any unpushed changes.
Theme: Amethyst Theme By default, the Git extension will add a Sync Changes button as shown above, if there are u
The rest of this page is on the live site.