June 2016 (version 1.3)
Join VS Code at Microsoft Ignite or catch the sessions online. A year of VS Code, wrapped. Explore the highlights. June 2016 (version 1.3) 1.3.1 Recovery build To fix several issues, we're releasing a 1.3.1 recovery build. You can view the resolved issues here . Downloads: Windows | OS X | Linux 64-bit .zip .deb .rpm | Linux 32-bit .zip .deb .rpm June Release Summary We're really excited about the June release of VS Code.
We've made some big changes to Extension management (dedicated Extensions View) and added Tabs (tabbed editor panes). Other new features include global Search and Replace, improved Drag and Drop and optional indentation guides. All of this along with enhancements to existing features like the Integrated Terminal and delivering a set of important bug fixes. Here are the highlights: Tabs : Tabbed editor panes allow you to quickly navigate to your files and organize your workbench.
Extensions : New in-product Extensions View to quickly find, install and manage your extensions. Workbench : Enhanced Drag and Drop, Preview Editors to conserve your editor panes, and multiple Integrated Terminals. Editor : Global Search and Replace, Indent Guides, Problems panel to view errors and warnings. Languages : Better, more complete Emmet support, Atom JavaScript grammar extension. Debugging : Lots of improvements including support for attaching to running Node.js processes and changing variable values during a debug session.
Extension Authoring : A new contribution point for menu bars and context menus. New APIs to open non-text resources and add editor decorator attachments. Tabs With this release, VS Code shows open files as Tabs in the title area above the editor. You can move Tabs around via Drag and Drop to organize your files or right-click on a Tab to perform useful file specific actions. If you prefer not to use Tabs, you can disable them through the workbench.editor.showTabs setting.
When there is not enough available space to show all files, you will see Tabs overflowing to the left and right. You can always use the mouse to scroll left and right across all tabs. The little overflow icon (see image below) is enabled as soon as there are Tabs outside of the visible view. Clicking on the overflow icon shows a list of all Tabs opened in the group. You can use the new workbench.editor.openPositioning setting to control where new editors should open.
By default they open to the right of the active Tab, but you can change this to open to the left, or to the beginning or end of all editors. Open Editors View The new OPEN EDITORS view in the Explorer is the replacement to the previous WORKING FILES view. The OPEN EDITORS view is a visual representation of the editor (open file) stacks: Each editor group with the editors that belong to it is shown. Clicking on an editor will make it active and open it in the corresponding group.
Top level actions to close all or save all open editors. Editor level actions to close or save an editor. Context menu actions provide more refined actions. It is possible to drag and drop editors between editor groups or from the Explorer You can hide the OPEN EDITORS view by setting the number of visible items to 0, with "explorer.openEditors.visible": 0 . Note: Since the WORKING FILES view has been deleted, please refer to this issue to get an overview of the new or changed command identifiers.
More on Editor Stacks As a preparation for enabling Tabs in the workbench, we revisited how you can interact with editors in VS Code. Many users coming from other tools were confused by some of the editor (open file) behavior in VS Code. For example: Closing a dirty editor (an editor with an unsaved file) did not prompt for saving. Closing an editor, closed the entire group without revealing the previous editor. The editor history showed a list of all editors ever opened and not a list of editors you opened in a group.
WORKING FILES view in the Explorer was a confusing concept. With editor stacks , we've tried to address these issues: You can open up to 3 editor groups side by side and each group contains a stack of editors . Every time you open an editor, it is added to the top of the stack. Closing an editor from a group reveals the editor that was previously opened in that group until the last editor closes and the group hides. You get prompted to save for dirty editors.
Use ⌃Tab (Windows, Linux Ctrl+Tab ) to bring up a list of most recently used editors of a group for navigation. Use the View: Show All Editors command to show a list of all open editors across all groups. Note that the behavior of editor stacks is independent from having Tabs enabled or not. You will benefit from these changes even if you don't want to use Tabs. Note: Due to the large conceptual impact of editor stacks, many command ids have been renamed and new commands introduced.
Please refer to this issue that documents the changes. It also provides guidance if you liked the previous behavior and explains how to change key bindings back to the old behavior. Extension Management We have introduced a new Extensions View to improve finding, installing, and updating VS Code extensions . To display the Extensions View, click the Extensions View icon or press ⇧⌘X (Windows, Linux Ctrl+Shift+X ) : By clicking on the ...
More Actions button, it is possible to show: The list of currently installed extensions The list of outdated extensions that can be updated The list of recommended extensions based on your workspace The list of globally popular extensions Clearing the search box, shows the list of installed extensions. Browsing through a list of extensions, it is possible to install, uninstall or update them. Clicking on an extension will display the detailed description in the editor area.
Workbench Errors and Warning in the Problems panel With the June release, we now offer a new Problems panel, docked at the bottom of VS Code, that shows errors, warnings and other information generated by different sources like language servers, linters and others. In previous releases, we showed the errors and warnings in the quick box at the top of the editor. We have received feedback from users that this made it difficult to review errors and warnings while editing files.
The new panel makes it easy to navigate through your errors and warnings and fix them while the editor is still open. A filter box is provided to search and filter among the problems shown. You can either filter by type or by text. For example, 'errors' will filter for all problems of type error. 'character' will filter for problems with messages containing the word 'character'. You can open the Problems panel by: Using ⇧⌘M (Windows, Linux Ctrl+Shift+M ) From the View | Problems menu From the View > Show Problems command in the Command Palette The key binding ⇧⌘M (Windows, Linux Ctrl+Shift+M ) that was used to show errors and warnings in the quick open/quick box will now open the Problems panel.
By default, the Problems panel scrolls and shows problems for your active file. If you don't want this automatic reveal behavior, you can disable it through a setting problems.autoReveal . Set problems.autoReveal to false to prevent your Problems view from changing as you switch between active files. Note: This view is just a representation of markers generated by the language servers or linters or build tasks or any external builders configured in or outside your workspace.
You have to configure or customize them appropriately in order to see the expected problems. More powerful Drag and Drop With all the work on Tabs, we also looked at improving the Drag & Drop support in the editor. We always allowed you to drop files from outside VS Code into the editor to open the files and now there is a lot more that you can do: Drop to Split Drag some files to the left or right area of an editor to open it to the side of that editor.
You can either drag from the Explorer or a Tab if Tabs are enabled. Drop Fee
The rest of this page is on the live site.