February 2022 (version 1.65)
Join VS Code at Microsoft Ignite or catch the sessions online. A year of VS Code, wrapped. Explore the highlights. February 2022 (version 1.65) Update 1.65.1 : The update addresses these security issues . Update 1.65.2 : The update addresses these issues . Downloads for 1.65.2 Windows x64 Arm64 macOS Universal Intel Apple silicon Linux .deb .rpm .tar.gz Arm instructions Snap Welcome to the February 2022 release of Visual Studio Code.
New editor history navigation - Scope Go Back/Go Forward history to editor group or single editor. Light High Contrast theme - Light theme for enhanced VS Code editor visibility. New audio cues - Audio cues for warnings, inline suggestions, and breakpoint hits. Drag and drop Problems and Search results - Drag results to new or existing editor groups. Source Control diff editor management - Automatically close diff editors after Git operations.
Debugger lazy variable evaluation - Lazy evaluation of JavaScript/TypeScript property getters. Preview: Terminal shell integration - Rerun terminal commands, command status decorations. VS Code for the Web - Reopen recent local files and folders, improved Git integration. If you'd like to read these release notes online, go to Updates on code.visualstudio.com . Workbench New editor history navigation The editor history navigation feature in VS Code drives some popular commands, such as Go Back and Go Forward .
Numerous feature requests accumulated over time to improve this feature and also add more capabilities. This milestone editor history navigation was rewritten from scratch to address most of these requests. Editor group aware navigation Editor groups are now taken into account when navigating in the editor history. Navigating back and forward in editor history will activate and focus editors in exactly those editor groups as they were.
When an editor group is removed, all associated history entries are discarded. In the short video below, the first Go Back places the cursor in the new editor group and then the second Go Back navigation returns to the original editor group. Theme: GitHub Light New setting to scope navigation to editor group or editor A new setting workbench.editor.navigationScope makes it possible to scope editor history navigation to just the active editor group or even editor.
Supported values are: default : Editor navigation works across all opened editor groups and editors. editorGroup : Editor navigation is limited to opened editors of the active editor group. editor : Editor navigation is limited to the active editor. If you configure the scope to editorGroup or editor , each editor group or editor will have their own navigation stack that can be navigated individually. Notebook support You can now navigate between cells you have selected in any notebook.
Navigation works across editors, in the same way as you can navigate between cursor locations in a text editor. Theme: GitHub Light New commands to navigate edit or navigation locations By default, editor navigation locations are added whenever you navigate across editors but also when navigating within editors (for example, when switching notebook cells or changing selection in text editors). If you feel that too many locations are being recorded, new commands have been added that reduce locations to either: Navigation locations - For example, when using Go to Definition .
Edit locations - Whenever an editor is changed. For example, when typing in a text editor. You can assign your favorite keybinding to these commands to change your navigation accordingly. Commands for edit locations: workbench.action.navigateForwardInEditLocations - Go forward in edit locations. workbench.action.navigateBackInEditLocations - Go back in edit locations. workbench.action.navigatePreviousInEditLocations - Go previous in edit locations. workbench.action.navigateToLastEditLocation - Go to last edit location (this command already existed before).
Commands for navigation locations: workbench.action.navigateForwardInNavigationLocations - Go forward in navigation locations. workbench.action.navigateBackInNavigationLocations - Go back in navigation locations. workbench.action.navigatePreviousInNavigationLocations - Go previous in navigation locations. workbench.action.navigateToLastNavigationLocation' - Go to last navigation location. Associated context keys have been added to make assigning keybindings more powerful.
Context keys for edit locations: canNavigateBackInEditLocations - Whether it is possible to go back in edit locations. canNavigateForwardInEditLocations - Whether it is possible to go forward in edit locations. canNavigateToLastEditLocation - Whether it is possible to go to the last edit location. Context keys for navigation locations: canNavigateBackInNavigationLocations - Whether it is possible to go back in navigation locations. canNavigateForwardInNavigationLocations - Whether it is possible to go forward in navigation locations. canNavigateToLastNavigationLocation - Whether it is possible to go to the last navigation location.
New layout control options Last milestone, we introduced the experimental layout control in the title bar (enabled by setting workbench.experimental.layoutControl.enabled to true ). We have heard feedback that, while the actions in the control are useful, they require too many clicks. For that reason, we are adding several UI options for everyone to try out with the setting workbench.experimental.layoutControl.type . This setting has the following options: menu : The previous behavior with a single button that opens a menu (default). toggles : A new option that shows three buttons to toggle the Panel, Side Bar, and Side Panel. both : A new option that shows the toggles followed by the menu button, which still allows you to fairly quickly access the customize layout Quick Pick.
The image below shows layoutControl.type set to both to display the three toggle buttons along with the menu dropdown. Light High Contrast theme A new Light High Contrast theme has been added to improve legibility and readability of the editor. Audio cues New audio cues have been added with this release, including audio cues for warnings, inline suggestions, and debugger breakpoint hits. The sounds have been tuned and the general setting audioCues.enabled has been deprecated in favor of the individual audioCues.* settings: All audio cues except lineHasWarning are enabled by default for screen reader users (setting value auto ).
A new audio cue command Help: List Audio Cues lists all available audio cues, lets you hear each audio cue as you move through the list, and review which cues are currently enabled. Drag and drop Problems and Search results You can now drag and drop a Problem, Search, or Reference result into the editor, opening the file and revealing the result position. This can be useful if you want to start a new editor group or drop a result into an existing editor group.
Settings editor split view The Settings editor now uses an adjustable split view to separate the table of contents from the settings list. Improved automatic language detection When the new setting workbench.editor.historyBasedLanguageDetection is enabled, untitled editors will use an improved automatic language detection algorithm that factors in your editor history and the contents of the current workspace. The new algorithm requires much less text input than before to provide detection results.
Below is an example of using this across JavaScript, TypeScript, Markdown, Python, PHP, and C++ (many more languages are supported): Theme: GitHub Light + HC Customizations Improved language extension recommendations Language feature extension recommendations now take into consideration other prominent language extensions in the Marketplace while recommending. For example, VS Code does not recommend the Java Extension Pack if you have the Apache NetBeans Java extension installed.
Keyboard shortcut for extension tree hovers You can trigger
The rest of this page is on the live site.