Text of code.visualstudio.com › updates › v1_72 as Styx crawled it on Oct 9, 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

September 2022 (version 1.72)

🎬 Watch The Story of VS Code! VS Code is now on Instagram, follow @vscode.ig for updates, tips, and more. Rewatch GitHub Copilot Day. September 2022 (version 1.72) Downloads for 1.72.2 Windows x64 Arm64 macOS Universal Intel Apple silicon Linux .deb .rpm .tar.gz Arm instructions Snap Update 1.72.1 : The update addresses these security issues . Update 1.72.2 : The update addresses these issues . Welcome to the September 2022 release of Visual Studio Code.

There are many updates in this version that we hope you'll like, some of the key highlights include: Tool bar customization - Hide/show tool bar actions. Better editor autoscrolling - Scrolling speed tuned to cursor location. Extensions view updates - Highlights extensions with updates or needing attention. Search results in a tree view - Review search results in either list or tree view. Nested Git repo support - Detects and displays nested Git submodules.

Terminal Quick Fixes - Suggestions to correct command typos and set an upstream remote. Pin frequently used tasks - Pin tasks to the top of the Run Task dropdown for quick access. Markdown link validation - Automatically check header, file, and image links. GitHub Enterprise Server authentication - Improved login workflow no longer requires PAT. Dev Containers Features - Easily add and share functionality for development containers.

VS Code Community Discussions - Connect with other VS Code extension authors. 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. Workbench Hide actions from tool bars You can now hide actions from tool bars. Right-click on any action in a tool bar and select its hide command or any of the toggle commands.

Hidden actions are moved to the ... More Actions menu and can be invoked from there. To restore a menu, right-click the tool bar button area and select the Reset Menu command. To restore all menus, run Reset All Menus from the Command Palette ( ⇧⌘P (Windows, Linux Ctrl+Shift+P ) ). In the video below, the GitLens extension File Annotations menu is hidden from the editor tool bar and then restored via Reset Menu . Sorry, your browser doesn't support HTML 5 video.

Merge editor Opt in to use the 3-way merge editor After reviewing all the merge editor feedback we received and thinking about the experience as a whole, we decided to not show the 3-way merge editor by default (the git.mergeEditor setting is now false ) when conflicts are detected. The reasoning for this decision can be found in issue #160806 . For files with conflicts, users can now select Resolve in Merge Editor to open the 3-way merge editor: CodeLens UI User feedback indicated that checkboxes had some UX problems.

The checkboxes weren't very discoverable and they caused confusion by not properly representing all possible states. This iteration, we switched to CodeLens UI that uses textual labels ( Accept Incoming , Accept Current , Accept Both ): We will keep iterating on this design and closely monitor all the feedback we get. Result file recomputed from scratch In the last iteration, we tried to design the merge editor as an alternative view of a file with conflicts.

Instead of showing conflict markers, separate editor panes showed details of the conflict. This design had the advantage that opening the merge editor would not modify the file on disk and user changes made before opening the merge editor could be kept. Unfortunately, this was not only confusing, but also didn't work in all cases, as our merge algorithm and the Git merge algorithm didn't align perfectly. With this release, if a file with conflict markers is opened in the merge editor, as a first step, we use our merge algorithm to recompute the result file, without inserting any conflict markers.

One-sided conflicts are resolved automatically and proper conflicts are reset to the common ancestor of both versions and marked as unhandled . Base view The merge editor now has a separate base view that can be used to compare any side with the common ancestor. Tree view Find control improvements You can now move the tree view Find control vertically, in order to access the UI elements behind it. Press ⌥⌘F (Windows, Linux Ctrl+Alt+F ) inside tree views to display the Find control.

Additionally, the tree view Find control will remember the last search term when reopened. Built-in preview for some audio and video files VS Code now supports previewing some audio and video file formats: The following audio formats are currently supported: WAV MP3 Ogg FLAC And the following video formats can be previewed: H.264 VP8 For video files, keep in mind that both the video and audio track's media formats must be supported.

Many .mp4 files for example, use H.264 for video and AAC audio. VS Code will be able to play the video part of the .mp4 , but since AAC audio is not supported, there won't be any sound. You will need to use MP3 for the audio track. Disable incremental naming You can now disable incremental file naming in the File Explorer with the new disabled value for the explorer.incrementalNaming setting. This value disables logic for changing the file name on paste within the File Explorer.

If the file name is already present, you will be prompted to overwrite the existing file, similar to most native explorers. Warning when editing inside VS Code application folder When editing files inside the VS Code application folder, a warning is now shown in the editor. Accidentally modifying files in the application folder is a common mistake and not usually what someone intended. Editor Improved autoscroll behavior When selecting and dragging, the editor used to scroll in a way that was dependent on the display's frames per second (FPS), sometime making the editor scroll quickly as soon as the mouse reached the editor edges.

Now, the editor autoscrolls at a more manageable speed of about one viewport per second when the mouse is close to the edges, and faster when the mouse is further from the editor, independent of the FPS. In the video below, the scroll rate increases as the mouse cursor moves down away from the editor. Sorry, your browser doesn't support HTML 5 video. Improved hover The editor hover used to be very aggressive in hiding itself, especially when the mouse was going over an empty area of the editor.

This made it difficult to reach some of the actions shown in the hover. Now, the hover will stay visible as long as the mouse is moving towards it. The setting "editor.hover.sticky": false reverts to the previous behavior. In the "After" video on the right, it is much easier to select a Quick Fix from the hover: Sorry, your browser doesn't support HTML 5 video. Sorry, your browser doesn't support HTML 5 video. New Code Action groups There are two new groups available in the Code Action control , Inline and Move .

These groups correspond to that refactor.inline and refactor.move Code Action kinds. New Code Action colors You may notice that the Code Action control also looks a little different this iteration. The styling was updated to use more appropriate theme colors . The biggest change is that the control body now uses editorWidget.* colors instead of menu.* . We are still refining these colors, so let us know if they don't work well with a given theme or if any color customization options are missing.

Extensions Recently updated extensions VS Code now shows extensions updated during the last 7 days in a Recently Updated section of Updates in the Extensions view. Extensions requiring attention VS Code now shows extensions requiring attention sorted to the top of the default Installed section of the Extensions view. This includes extensions that have a pending update or have been updated or disabled and require VS Code to reload.

The badge on the Extensions icon in the Activity Bar now shows t

The rest of this page is on the live site.