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

March 2020 (version 1.44)

Join VS Code at Microsoft Ignite or catch the sessions online. A year of VS Code, wrapped. Explore the highlights. March 2020 (version 1.44) Update 1.44.1 : The update addresses this security issue . Update 1.44.2 : The update addresses these issues . Downloads for 1.44.2 Windows x64 macOS Intel Linux .deb .rpm .tar.gz Snap Welcome to the March 2020 release of Visual Studio Code. There are a number of updates in this version that we hope you will like, some of the key highlights include: Accessibility improvements - Easier diff view navigation, clearer role designations for UI controls.

Timeline view - See time-series events like Git commit history from within VS Code. Better Quick Open for files - Navigate smoothly from files to symbols, filter files by folder name. Extension Pack display - Quickly see what is bundled in an Extension Pack. Persisted Undo/Redo stack - Undo/Redo stack preserved for reopened files. Remote Development - Directly check out Pull Requests into containers, support for Kubernetes.

Settings Sync preview - Settings Sync now lets you share snippets and UI state across machines. New Python tutorials - Tutorials for creating Python containers and building Data Science models. 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.

And for the latest Visual Studio Code news, updates, and content, follow us on Twitter @code ! Accessibility This milestone we received great feedback from our community, which helped us identify and tackle many accessibility issues . Diff view is now more accessible. Use F7 and ⇧F7 (Windows, Linux Shift+F7 ) to navigate through changes in the Accessible Diff Viewer and use the Stage / Unstage / Revert Selected Ranges commands to stage, unstage, or revert the current change.

Better roles used across our widgets. The listbox role is used for the Suggest widget and Quick Pick, list for static lists, and document for read-only content such as the Welcome view and Markdown preview. Tuned the behavior of our Quick Pick widget. The current line CodeLens can now be shown in the Quick Pick with the Show CodeLens Commands For Current Line command. Timeline view The Timeline view is now out of preview and enabled by default.

This is a unified view for visualizing time-series events (for example, Git commits, file saves, test runs, etc.) for a file. The Timeline view automatically updates showing the timeline for the currently active editor, by default. You can control this default behavior by toggling the eye icon in the view toolbar. Also, similar to other views, the Timeline view supports find or filter as you type. The Timeline view is collapsed by default at the bottom of the File Explorer.

Selecting the Timeline sash will expand the Timeline view. In this release, the built-in Git extension contributes a timeline source that provides the Git commit history of the specified file. Selecting a commit will open a diff view of the changes introduced by that commit. A context menu provides commands to Copy Commit ID and Copy Commit Message . There is also a new Open Timeline command on the File Explorer's context menu, to quickly show the timeline for the selected file.

Here is the Timeline view in action: Theme: Dark Amethyst Additional timeline sources can be contributed by extensions (although the API is still in the proposed stage), which will be shown in the unified Timeline view. Extensions can also contribute menu items to the Timeline view, and to individual timeline items. You can also easily choose which sources you'd like included in the view. Workbench Quick Open rewrite The Quick Open ( ⌘P (Windows, Linux Ctrl+P ) ) control was using an old version of our tree widget, and in this iteration, it was migrated to use our latest list control, already used in the rest of the VS Code UI.

Functionally, you should not be able to tell the difference, as all commands will work as before. We did take this opportunity to add some features that you might find useful. Navigate from files to symbols You can now continue to navigate to the symbols of a file result simply by typing @ . For the file that is currently selected, all symbols will appear and the editor will open in the background to reveal the active symbol.

The video below also shows that you can group symbols by category by following @ with : . Filter results by separating multiple queries with spaces If you are getting too many results for a file search, you can add more search patterns after typing a space. For example, you can narrow down results by folder if you type <file name> <folder name> one after the other. Note: This also works for the editor ( ⇧⌘O (Windows, Linux Ctrl+Shift+O ) ) and workspace ( ⌘T (Windows, Linux Ctrl+T ) ) symbol picker.

Any text after a space character will be used to filter by the container of that symbol. Input is preserved when switching providers If you leave Quick Open visible and switch to another provider (for example, from file search to symbol search), VS Code will apply whatever filter is typed and use it for the new provider. This allows you to quickly reuse the typed input for symbol search when it was previously used for a file search.

Sort editor history by most recently used A new setting "search.quickOpen.history.filterSortOrder": "recency" allows you to sort editor history by the most recently opened items, even when starting to search. By default, editor history results will be sorted by relevance based on the filter pattern that was used. New command to open editor to the side A new command workbench.action.alternativeAcceptSelectedQuickOpenItem lets you add an additional keyboard shortcut to open files or symbols from Quick Open to the side.

By default, Ctrl+Enter (macOS: Cmd+Enter ) will open the file to the side in a new editor group, rather than in the current one. Improved Extension Pack display To identify Extension Packs in the Extensions view, there is now a number badge that shows the number of extensions included in the Extension Pack. Theme: GitHub Sharp with Customizations The Extension details page now shows all extensions bundled in the Extension Pack.

Theme: GitHub Sharp with Customizations Adjust height of editor tabs scroll bar A new setting workbench.editor.titleScrollbarSizing lets you increase the size of the scroll bar for editor tabs and breadcrumbs. This makes it easier to scroll through a long list of open editors. Configure it to large for a larger scroll bar: File Explorer can show hidden files If a file is hidden (via the files.exclude setting) but it is open and visible in the editor, the file is shown in the File Explorer along with its parent chain.

Those files and their parents are displayed in the File Explorer using a dimmed color as long as the file is visible in the editor area. View: Reopen with The new View: Reopen with command lets you reopen the currently active file using a different custom editor . You can use this command to switch between VS Code's standard text editor and the custom editor, or to switch between multiple custom editors for a resource. workbench.editorAssociations setting Also for custom editors , the new workbench.editorAssociations setting lets you configure which editor is used for a specific resource.

The example below configures all files ending in .catScratch to open using the example custom text editor from our extension samples. "workbench.editorAssociations" : [ { "viewType" : "catCustoms.catScratch" , "filenamePattern" : "*.catScratch" } ] View progress now shown on the view We have changed progress indication for custom views to now show on each view itself, rather than at the top of the view container. This allows for a more direct connection between the long-running operation and its progress.

There is also a new API option for exten

The rest of this page is on the live site.