August 2022 (version 1.71)
Join VS Code at Microsoft Ignite or catch the sessions online. A year of VS Code, wrapped. Explore the highlights. August 2022 (version 1.71) Update 1.71.1 : The update addresses this security issue . Update 1.71.2 : The update addresses these issues . Downloads for 1.71.2 Windows x64 Arm64 macOS Universal Intel Apple silicon Linux .deb .rpm .tar.gz Arm instructions Snap Welcome to the August 2022 release of Visual Studio Code.
August is when many of the engineers on VS Code take their vacations, but there are still many updates in this version that we hope you'll like: Merge editor improvements - Easier transition between text and merge editors. Expanded codecs support - To help display embedded audio and video in notebooks and webviews. File rename selection - Pressing F2 selects filename, whole name, or file extension. New Code Action UI - Quickly find the Code Action you're looking for.
Terminal updates - Shell integration for fish and Git Bash, new smooth scrolling. Jupyter notebook image pasting - Paste and preview image files in notebook Markdown cells. TypeScript livestreams - Watch TS "Crash Course" or "Tips and Tricks" on YouTube. Live Preview extension - Live Preview now supports multi-root web projects. Markdown Language Server blog post - Learn how Markdown support moved to a Language Server.
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 Merge editor improvements Opening the merge editor from files with conflicts A file that has a conflict will now automatically show an Open in Merge Editor button to transition between the text and merge editors.
Merge editor file not modified on open VS Code no longer modifies the result file when opening it in the merge editor (conflicting regions were replaced with base). Instead, the conflict markers remain in the file but are hidden in the result view. The checkboxes can be used to replace the conflict markers with either side, a combination of both sides or, by unchecking them, with base. Restoring old conflict decorators The old inline conflict decorators are no longer disabled, so the merge editor and inline experience can be used together.
When the merge editor opens, you can get the previous experience with a single click in the editor toolbar: By clicking the same icon next to the file name in the Source Control view, you can skip the merge editor entirely. However, you can switch between the new and old experience at any time and even use them in parallel: Checkbox improvements We now make sure that the checkboxes of a conflict are always visible, even when the conflict is larger than the viewport.
Colors are used to emphasize the checkboxes for unhandled conflicts. Diffing algorithm improvements We started exploring alternative diffing algorithms to improve the quality of conflicts. A new experimental diffing algorithm can be enabled with the following setting: "mergeEditor.diffAlgorithm" : "experimental" , This new algorithm is not optimized for performance yet, but improves the merge editor experience for many edge-cases.
Going forward In this release, we focused on the most important UX issues of the merge editor and fixed many bugs . If you still find yourself confused by the new merge editor, we would love to hear from you! Please create a new issue in our repo , share a screenshot and your merge editor state (using the Copy Merge Editor State as JSON command). We really appreciate all the feedback we've gotten so far, and more feedback will help us make the merge editor experience great for everyone.
Our future work will focus on a separate base view , conflict minification , diffing algorithm refinement, and other improvements . FFmpeg codecs support The FFmpeg shared library that ships as part of the VS Code previously had only support for the FLAC codec. With this release, the library has been updated to support the following list of codecs and containers. This will allow more audio and video files to be played from notebooks or by extensions embedding audio and video into webviews.
Vorbis Flac H.264 VP8 WAV MP3 Ogg Theme: fairyfloss (preview on vscode.dev ) Explorer rename selection improvements After initiating a rename action on a file, pressing the F2 key will cycle through the file name, entire selection, and file extension to allow for more flexible keyboard-only interaction. Rounded buttons We've update all of our buttons to have a slight rounded corner to better match our design aesthetic.
Theme: Material Theme Palenight High Contrast Window Controls Overlay on Windows In release 1.68, VS Code adopted the Window Controls Overlay feature support from Electron behind an experimental flag and was off by default. We have resolved the remaining issues around this feature affecting VS Code, allowing us to enable it by default for all users on Windows. The Windows Controls Overlay feature lets VS Code users on Windows 11 select Snap Layouts to place VS Code on their desktop.
Tree view Expand Mode The setting Workbench > Tree: Expand Mode ( workbench.tree.expandMode ), which controls whether tree nodes expand on single-click or double-click, will now be respected by tree views that are contributed by extensions. Editor Sticky Scroll Sticky scroll shows the current scope at the top of the view port. The feature is no longer experimental and can be enabled through the settings with editor.stickyScroll.enabled .
Further improvements are: It is possible to set the maximum number of lines to display with the Editor > Sticky Scroll: Max Line Count ( editor.stickyScroll.maxLineCount ) setting. The default maximum is 5 lines. You can use Ctrl/Cmd + Click in the sticky scroll, to navigate to a definition. New Code Action control We've completely overhauled the Code Action control. Instead of a simple menu of Code Actions , there is now a custom control that makes it easier to find the Code Action you want: The new control also lets VS Code surface additional information.
For example, you can now hover over disabled Code Actions to learn why they are disabled: You can also customize the keyboard shortcuts used to navigate through the Code Action list by modifying the keybindings for the following commands: selectNextCodeAction selectPrevCodeAction acceptSelectedCodeAction Going forward, the new code action UI provides a great foundation for further UX improvements. Be sure to let us know if you have any suggestions!
Configure suggest matching There is a new setting to configure IntelliSense filtering. By default, the first character must match a word start, for example c must match console or WebContext but won't match description . The editor.suggest.matchOnWordStartOnly setting changes this behavior. When disabled, filtering takes any match into account - this leads to more results but filtering still happens by match quality. In the short video below, you can see that when matchOnWordStartOnly is disabled, suggestions for 'dir' include more items, such as 'mkdir' and 'makedirs'.
Source Control Commit action button improvements Users can globally control the secondary action (for example, pull , sync ) that is being executed following a successful commit operation using the git.postCommitCommand setting. This milestone we have added a new setting git.rememberPostCommitCommand that can be enabled to remember the last executed secondary action per repository. Terminal Shell integration improvements The following improvements to shell integration were made this release: Fish shell integration is available as an experimental manual install only.
See the Shell Integration documentation for how to install it. Git bash for Windows shell integration is available as an experimental manual install only. See the section on manual installation for details. Support for common alternative curr
The rest of this page is on the live site.