Text of code.visualstudio.com › updates › v1_52 as Styx crawled it on Nov 18, 2026. The page may have changed since. Only its words are kept, without pictures or layout, and only the first part of a long page.

Open the live page

November 2020 (version 1.52)

Join VS Code at Microsoft Ignite or catch the sessions online. A year of VS Code, wrapped. Explore the highlights. November 2020 (version 1.52) Update 1.52.1 : The update addresses these issues . Downloads for 1.52.1 Windows x64 Arm64 macOS Intel Linux .deb .rpm .tar.gz Arm instructions Snap Welcome to the November 2020 release of Visual Studio Code. As announced in the November iteration plan , we continued to focus for two weeks on housekeeping GitHub issues and pull requests as documented in our issue grooming guide .

Across all of our VS Code repositories, we closed (either triaged or fixed) 5242 issues, which is even more than during our last housekeeping iteration in October 2019 , where we closed 4622 issues. While we closed issues, you created 2937 new issues. The main vscode repository now has 2146 open feature requests and 884 open bugs. In addition, we closed 144 pull requests. Same as every year, we used the live tracker from Benjamin Lannon to track our progress: After focusing on housekeeping, we have also addressed several feature requests and community pull requests .

This resulted in many new features and settings, some of the key highlights include: Word wrap in diff editor - Both inline and side-by-side views now support word wrapping. New extension bisect feature - Troubleshoot which extensions are causing issues in VS Code. Keyboard shortcuts editor improvements - Create a keybinding from the Command Palette. Undo file operations in Explorer - Undo or redo file operations in the Explorer.

New Git commands and settings - Optimize your Version Control experience with new capabilities. Preview editor improvements - Turn off preview editors altogether, and try new interaction models. Sticky tab stops for spaces - Improved experience when indenting with spaces. Improved word-based suggestions - Display word-based suggestions from other open files. Terminal configuration support - Modify terminal settings from the terminal dropdown menu.

New Remote Development resources - Check out the new video and Learn module. Workbench Preview editor improvements We've made several updates to how we handle preview editors based on user feedback. The workbench.editor.enablePreviewFromQuickOpen setting is now disabled by default, so that editors opened from Quick Open will no longer appear in preview mode. When you start a code navigation (for example, with Go to Definition ), the editor you start from will move out of preview mode and stay open, while the new editor will be in preview mode until you navigate further.

We changed all of our custom trees (the ones used in the Extensions or Git views, for example) to work more consistently like other built-in trees (such as the File Explorer). This means, the following interactions now apply to all of them: Double-click or mouse-middle-click to open in non-preview. Enter to open in non-preview mode ( Space to open in preview mode). Alt+Click to open an editor to the side of the active one.

Note: If you are an extension author who is using our custom tree API, you get the benefit of this change as well. Make sure to use the vscode.open or vscode.diff commands for the TreeItem.command to get the new preview mode behavior. A new menu item, Keep Editors Open , in the editor overflow menu allows you to quickly turn off preview editors altogether: Restore previous session windows A new value preserve for the existing window.restoreWindows setting lets you force that every window you had opened before closing VS Code is restored when you restart VS Code, even if VS Code is explicitly asked to open a specific folder or file.

A common example is double-clicking on a file in your platform's file explorer to open it in VS Code or using the terminal to open a specific file or folder. Without the window.restoreWindows: preserve setting, VS Code will only open the file or folder as instructed, but not restore any other window. Disable editor group splitting on drag & drop A new setting workbench.editor.splitOnDragAndDrop prevents editor group splitting when using dragging and dropping editors.

There is also a way to toggle this conditionally during the drag and drop operation by pressing and holding the Shift key (macOS) or Alt key (Windows, Linux). Undo file operations in Explorer The File Explorer now supports Undo and Redo for all file operations: delete, rename, copy, move, new file, and new folder. Make sure the focus is in the File Explorer and trigger the Undo or Redo commands and your last file operation will be undone or redone respectively.

Keep in mind that we have separate undo stacks for the editor and the File Explorer, and we choose which one to undo based on focus. Progress for long running operations in Explorer We now show progress in the File Explorer and Status bar for long running file operations (longer than 500 ms). There is also initial support for canceling long running operations. This should be helpful when copying large folders or downloading resources from remote locations.

Open Editors sorting There is a new setting explorer.openEditors.sortOrder to control the sort order in the OPEN EDITORS list. The values are: editorOrder - Editors are listed in the same order as editor tabs are shown (default). alphabetical - Editors are listed in alphabetical order inside each editor group. The alphabetical sorting only has an effect on the Open Editors view - it will not "move tabs" in any way. This can be helpful when you have lots of files open and you want to match up files that are associated (for example, hello.component.js and hello.component.html).

Accessible progress control The workbench progress display has been made more accessible. VS Code sets the appropriate ARIA roles so that screen readers can report progress for all long running operations in VS Code. Most screen readers by default only announce progress if it is ongoing for more than 10 seconds. Source Control changes show their parent folder path Diff editors opened from the Source Control view will now reveal their file path (when tabs are disabled).

Previously, only the filename would show, but now the parent folder appears if the before and after files are within the same folder. New proxy login dialog enabled by default Our new proxy login dialog is now enabled by default. You can read our previous release notes for more details. The setting window.enableExperimentalProxyLoginDialog can be used to enable the old dialog, but we will remove this support in the near future.

If you find an issue with the new login dialog, please let us know by filing an issue . Improved terminal environment handling (Linux, macOS) When you start VS Code on Linux or macOS for the first time via the dock or a launcher (and not the terminal), VS Code starts a background process to resolve your shell environment (as defined or changed by .bashrc or .zshrc ). All environment variables detected are then used by VS Code so that starting from a terminal or the dock/launcher does not make any difference, which is important when debugging or executing tasks.

Unfortunately, VS Code does not open until this background process has executed. In order to not block startup for too long, VS Code will begin opening after 10 seconds. In this case, VS Code now informs you that it was unable to resolve the shell environment and offers a link to learn more: Similarly, VS Code now shows a warning after three seconds to indicate that VS Code startup was blocked resolving your shell environment: We are actively looking into changing our strategy to not block VS Code from starting while still resolving the shell environment in the background, but this will only be possible in future milestones.

Other noteworthy changes in this area are: You can now define and change environment variables from a terminal before launching a second window of VS Code, and these will properly overwrite the variables from the first launch, effectively allowing for per-window environment varia

The rest of this page is on the live site.