October 2019 (version 1.40)
Join VS Code at Microsoft Ignite or catch the sessions online. A year of VS Code, wrapped. Explore the highlights. October 2019 (version 1.40) Update 1.40.1 : The update addresses these issues . Update 1.40.2 : The update addresses these issues . Downloads for 1.40.2 Windows x64 macOS Intel Linux .deb .rpm .tar.gz Snap Welcome to the October 2019 release of Visual Studio Code. As announced in the October iteration plan , we focused 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) 4622 issues, which is even more than during our last housekeeping iteration in September 2018, where we closed 3918 issues. While we closed issues, you created 2195 new issues. This resulted in a net reduction of 2427 issues. The main vscode repository now has 2162 open feature requests and 725 open bugs. In addition, we closed 287 pull requests.
As part of this effort, we have also tuned our process and updated the issue triaging workflow . Same as last year, we used the live tracker from Benjamin Lannon to track our progress: During this housekeeping milestone, we also addressed several feature requests and community pull requests . Read on to learn about new features and settings. Workbench Activity Bar indicator We've introduced a new indicator for the active item in Activity Bar to make it stand out better and increase readability.
We also tuned the inactive foreground colors for a stronger contrast with the active element. You can control the active indicator via the new color token, activityBar.activeBorder . We also introduced an optional background color for the active element, activityBar.activeBackground , and when configured can look like so: Themable window border We've introduced two new theme colors, window.activeBorder and window.inactiveBorder , for providing a border around the VS Code window.
The window.activeBorder applies to the active (focused) window, while the window.inactiveBorder applies to inactive (unfocused) windows. These new colors do not inherit from any color, so they must either be provided by the theme or by the workbench.colorCustomizations setting. If only one color is specified, a border with that color will be applied to both active and inactive windows. List and tree keyboard scrolling You can now press ⌘↑ (Windows, Linux Ctrl+Up ) and ⌘↓ (Windows, Linux Ctrl+Down ) to scroll lists and trees using the keyboard.
Fewer notifications in Zen mode While using Zen mode, notification toasts will no longer distract you unless they inform about errors. You can control this behavior with the new zenMode.silentNotifications setting. You can always access all notifications from the status bar by clicking on the notification icon in the bottom-right corner. Type filters for outline and breadcrumbs There are new settings to configure what symbols are displayed in the Outline view and breadcrumb navigation.
The settings are called outline.show{symbol type} and breadcrumbs.show{symbol type} . For example, outline.showVariables , outline.showFunctions , etc. The screen shot above shows the Outline view configured to not show local variables and you can see that the variable hidden isn't shown. Note that it's up to the language extension to assign the type of a symbol. You can hover over the symbol label in the Outline view to see which symbol type is being used (shown in parentheses).
Control the sizing behavior when splitting editors A new setting workbench.editor.splitSizing controls the layout of editors when splitting them. By default, the size will be distributed evenly among all editors as shown below: Change this setting to split for the current editor to be split in half and not affect the size of other editors: Disable GPU acceleration We have heard issue reports from users that seem related to how the GPU is used to render VS Code's UI.
These users have a much better experience when running VS Code with the additional --disable-gpu command-line argument. Running with this argument will disable the GPU hardware acceleration and fall back to a software renderer. To make life easier, you can add this flag as a setting so that it does not have to be passed on the command line each time. To add this flag: Open the Command Palette ( ⇧⌘P (Windows, Linux Ctrl+Shift+P ) ).
Run the Preferences: Configure Runtime Arguments command. This command will open a argv.json file to configure runtime arguments. You might see some default arguments there already. Add "disable-hardware-acceleration": true . Restart VS Code. Note: Do not use this setting unless you are seeing issues! Editor files.eol per language The files.eol setting can now be set per language. For example, you could define that all files of 'mylanguage' language identifier use \n as the default end-of-line sequence for all new files.
"[mylanguage]" : { "files.eol" : " \n " } The end-of-line sequence is used for new files. For existing files, the current end-of-line sequence is always preserved. To change the end-of-line sequence for an existing file, use the Change End Of Line Sequence command. Using a files.eol language setting, the default end-of-line sequence for 'shellscript' is now defined as \n . Minimap scaling and improved font rendering A new setting editor.minimap.scale configures the minimap's size to one of several constant values, particularly useful for high DPI or ultra-wide displays.
Also, the rendering of the minimap's font is now smoother and clearer. Definition Preview Hover from the keyboard There is a new command Show Definition Preview Hover for better accessibility of the definition preview hover widget, which can be triggered by hovering a symbol with the mouse and pressing a modifier key dependent on the platform and configuration. Previously, only the command Show Hover was provided, which is equivalent to hovering the mouse cursor over a symbol.
Now, with Show Definition Preview Hover , the detailed hover information can be shown via the keyboard. Improvements to bracket matching Previously, VS Code would only highlight matching brackets when the cursor was next to a bracket character. Now VS Code will always highlight enclosing brackets if they exist. We have also adjusted our Go to Bracket and Select to Bracket actions to use enclosing brackets. Duplicate selection We have added a new action named Duplicate Selection .
When executed, the current selection will be duplicated and the result will be selected. When there is no selection, the current line will be duplicated, all without writing to the system clipboard. Font feature settings There is now more fine grained control over the font features. When configuring "editor.fontLigatures": true , VS Code would turn on liga and calt . But some fonts have more settings, such as stylistic sets used by Fira Code .
We now allow these font features to be explicitly controlled, for example: "editor.fontFamily" : "Fira Code" , "editor.fontLigatures" : true , "[javascript]" : { "editor.fontLigatures" : "'ss02', 'ss19'" , }, The above settings configure the editor to use the Fira Code font family, turn on font ligatures for all languages, and in JavaScript files enable the 'Horizontal Bar' ('ss02') and the 'Dotted zero' ('ss19') font feature settings.
These make the >= ligature render with a horizontal bar and the 0 render with a dot inside it in JavaScript: Better handling for Unicode combining characters We have made improvements around handling of Unicode combining characters and we treat such sequences as atomic characters (in cursor movement, editing operations, or in block cursor rendering). This is best demonstrated using the block cursor style and a before/after animation: Before: After: In a related change, the status bar now shows the Unicode point count in the Col section.
Cursor Redo The Soft Undo command has been renamed to Cursor Undo . This action is useful, for example when using �
The rest of this page is on the live site.