Text of code.visualstudio.com › updates › v1_60 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

August 2021 (version 1.60)

Join VS Code at Microsoft Ignite or catch the sessions online. A year of VS Code, wrapped. Explore the highlights. August 2021 (version 1.60) Update 1.60.1 : The update addresses these issues . Update 1.60.2 : The update addresses these issues . Downloads for 1.60.2 Windows x64 Arm64 macOS Universal Intel Apple silicon Linux .deb .rpm .tar.gz Arm instructions Snap Welcome to the August 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: Automatic language detection - Programming language detected when you paste into VS Code. Built-in fast bracket colorization - Fast bracket matching and colorization for large files. Settings editor syntax highlighting - Rich syntax highlighting for setting description code blocks. Custom terminal glyph rendering - Better display of box drawing and block element characters.

Set debugging Watch values - Change watched values during a debugging session. Notebook improvements - Markdown link navigation, faster rendering of large outputs. JavaScript/TypeScript inlay hints - Inline hints for parameter names and types, and more. Locked editor group preview - Keep a preferred editor layout by locking the editor group. Python extension testing updates - Better support for test discovery, navigation, and status.

Web extension authors guide - Learn how to update your extension for VS Code in the browser. If you'd like to read these release notes online, go to Updates on code.visualstudio.com . Join us live at the VS Code team's livestream on Thursday, September 2 at 8am Pacific (4pm London) to see a demo of what's new in this release, and ask us questions live. 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 Automatic language detection Last release, we introduced an experimental feature for untitled files that would automatically set the language mode for the file based on the contents. The automatic language detection feature uses machine learning to guess the language and the machine learning model runs entirely local on your machine. The model is powered by the open-source ML library, Tensorflow.js , and the ML model from Guesslang by GitHub user @yoeo .

This release we are enabling automatic language detection by default and also expanding detection to include files that don't have a file extension. In Notebooks, we provide an easy way to ask for language detection using the language picker. We added this feature because we found that some new users of VS Code didn't know how to set the language mode and didn't know that this is needed in order to get VS Code's rich feature set (language colorization and extension recommendations).

Enabling new users to quickly see the language features and extensions available for VS Code helps them as they ramp up on the editor. In addition, power users who use untitled text editors as a scratch pad, no longer need to explicitly set the language mode, which we hope will streamline their workflow. Below are several fun scenarios enabled by automatic language detection. Grab an example from online and paste it in an untitled editor: Theme: Panda Theme "Pipe into code" language detection (showing off detection of extension-less files): Theme: Panda Theme Auto detect option in the Notebooks language picker: Theme: Panda Theme Terminal editor confirmation dialog The dialog presented when closing a terminal editor with running child processes is now specific for the terminal editor and will no longer offer a way to "Save" the terminal.

Keep editors open instead of closing when they fail to restore Previously, when an editor failed to restore after reload of the window or restart of the application, the editor would automatically close until an editor was found that successfully loads. This behavior led to frustrating results, where a carefully created editor layout would go away due to editors closing. With this release, an editor that was once successfully opened will not close, even if it fails to restore.

The editor indicates the problem and offers to retry the operation: Syntax highlighting of codeblocks in the Settings editor Fenced code blocks in setting descriptions are now syntax highlighted: Open Settings editor to the side It's now possible to open the Settings editor in a side group by configuring a keybinding using the openToSide argument. { "key" : "cmd+," , "command" : "workbench.action.openSettings" , "args" : { "openToSide" : true } } This also works with the workbench.action.openSettingsJson command.

Editor High performance bracket pair colorization The editor now supports native bracket pair colorization: Bracket pair colorization can be enabled by setting "editor.bracketPairColorization.enabled": true . All colors are themeable and up to six colors can be configured. We implemented this feature to address performance issues of the famous Bracket Pair Colorizer extension by CoenraadS . Now, even changes in huge documents are reflected immediately: Inline suggestions in autocomplete Inline suggestions can now extend the suggestion preview when the autocomplete widget is shown.

If a suggestion that is selected in the autocomplete widget can be extended by an inline completion provider, the extension is shown in italic. Pressing Tab once will still only accept the autocomplete suggestion. Pressing Tab a second time will then accept the inline suggestion. This feature requires the suggest preview to be enabled ( "editor.suggest.preview": true ). Updated Peek views We've given the Peek views a visual refresh to align with the rest of the other editor views: Terminal Custom rendering of box drawing and block element characters Box drawing and block element characters now use pixel-perfect custom glyphs instead of using the font when GPU acceleration is on ( terminal.integrated.gpuAcceleration ).

This means, for example, that boxes are drawn without gaps, even if you set line height or letter spacing in the terminal. Here is an example of the terminal app Zenith that shows the box drawing characters around sections as well as block elements for the charts: This can be disabled by setting "terminal.integrated.customGlyphs": false . Improved rendering of underscore for certain fonts There were some historical issues with how underscore is rendered in the terminal, most of which were fixed by switching to the WebGL renderer (default).

There was one exception to this, where the underscore character in the font is unexpectedly drawn below the bounds of the cell on Linux. Notice how the underscore on the lower row is rendered below the cell: While this works fine in most cases, it fails on the bottom row because it is drawn outside the bounds of the canvas. We now work around this problem by detecting such a font and shifting the underscore texture up until it is within the bounds of the cell.

This solution also applies to the canvas renderer, which previously wouldn't show underscores for any rows because of how it clips the rows to avoid overlapping. Faster reconnection after reloading the window Previously, when reloading a window, it could take up to 300 ms to parse the state of a terminal's buffer and there was also the possibility of corruption. For several busy terminals, this can quickly add up! To fix this, the method of restoring the buffer has changed from recording a large number of recent raw terminal events on the pty host to maintaining a headless terminal frontend on the pty host and writing all data to that.

This approach brings several benefits: The amount of scrollback to restore can be fine-tuned. The default is now 100, which is a good balance between speed and the amount of data. The scrollback amount can be changed with the terminal.integrated.persistentSessionScrollback setting. Thanks to xterm.js' fast parser, this should have minimal impact on CPU usage and

The rest of this page is on the live site.