July 2017 (version 1.15)
🎬 Watch The Story of VS Code! VS Code is now on Instagram, follow @vscode.ig for updates, tips, and more. Rewatch GitHub Copilot Day. July 2017 (version 1.15) Update 1.15.1 : The update addresses these issues . Downloads: Windows | Mac | Linux 64-bit: .tar.gz .deb .rpm | Linux 32-bit: .tar.gz .deb .rpm Welcome to the July 2017 release of Visual Studio Code. There are a number of significant updates in this version that we hope you will like, some of the key highlights include: Large file support - Improved performance for large files, no size limit on 64-bit machines.
64-bit Windows builds - Use your computer's full address space with the 64-bit builds. Find in Markdown preview - Full search for Release Notes, Markdown preview, and Extensions. Auto-indent, Emmet 2.0 on by default - Source code auto-indenting and new Emmet support. Custom syntax highlighting - Easily adjust editor colors to your liking. Terminal environment variables - Preconfigure the Integrated Terminal environment.
Color picker UI - Quickly create colors in your CSS, SASS, and Less files. Loaded Scripts Explorer - Easily review and step through loaded scripts during Node.js debugging. Markdown preview plugins - Add styles, scripts or plug-ins to Markdown previews. code.visualstudio.com updates - Tutorials for React, Angular and deploying Node.js to Azure. Preview: Multi-root workspaces - Settings and debug configurations across multiple projects (Insiders build).
If you'd like to read these release notes online, you can go to Updates on code.visualstudio.com . The release notes are arranged in the following sections related to VS Code focus areas. Here are some further updates: Editor - Predefined snippet choices, improved auto-indenting and diff editor. Workbench - Customizable Explorer sort order and view layout, prefilled Quick Open actions. Integrated Terminal - Improved switching, delete word keyboard shortcuts.
Tasks - Less and Sass compiler output parsing, new Status Bar display. Extension Authoring - Multi-root support for debugging and settings, new Markdown Preview API. Insiders: Want to see new features as soon as possible? You can download the nightly Insiders build and try the latest updates as soon as they are available. Editor Large file support Large files are always a great way to stress-test an editor. We currently use a line based representation of the text buffer, which has some serious advantages, but also disadvantages, especially in terms of memory consumption (for example, a file with very many short lines).
Any file that is over 30MB or over 300K lines will now be considered a large file and will be handled specially in some circumstances. By disabling certain features for large files, for example tokenization, line guides, and wrapping or folding, we were able to optimize memory usage, in some cases, by as much as 50%. Additionally, large files will never travel to our web worker, which computes diff information, link detection, or word based completions.
This helps in reducing the memory pressure on the operating system. Some of the optimizations will impact all files, although the effects should not be noticeable for small files. We decided to remove the hard-coded file size limit of 50MB on 64-bit installations and enforce a 300MB file size limit on 32-bit installations. Refer to #30180 for more information about the different optimizations. Color Picker We've introduced a color picker for color customizations in this release.
It supports configuration of hue, saturation and opacity for the color that is picked up from the editor. It also provides the ability to trigger between different color modes by clicking on the color string at the top of the picker. The picker appears on a hover when you are over the color definition in a document. For the preview, we enabled it for CSS, Sass and LESS files, supporting RGBA, HSLA and Hex color modes.
We plan to extend the picker with more functionality as well as to enable extension authors to contribute their own color modes together with color definitions for their languages in future releases. Auto indentation In this milestone, we've turned on auto-indenting by default ( "editor.autoIndent": true ). If the language you are working with has proper indentation rules (for example, TypeScript, JSON, CSS), the indentation will be adjusted when you type, move lines and paste blocks of code.
Emmet 2.0 Two releases ago, we introduced a new Emmet implementation ("Emmet 2.0"). During its preview, users could opt-in and try new features such as showing Emmet abbreviations in the suggestion/auto-completion list and multi-cursor support for most of the Emmet actions . In this release, Emmet 2.0 and these features are enabled by default. Now that Emmet abbreviations are displayed in the suggestion/auto-completion list, VS Code no longer triggers Emmet abbreviations with the Tab key by default.
This solves 2 major issues: Unexpected Emmet expansions occurring when the user wanted to just add an indent using the Tab key. Items from the suggestion list getting inserted when the user actually wanted to expand an Emmet abbreviation. You can still bind any keyboard shortcut (other than Tab key) to the editor.emmet.action.expandAbbreviation command or use Emmet: Expand Abbreviation from the Command Palette . Note : To continue to expand Emmet abbreviations and snippets using the Tab key, set emmet.triggerExpansionOnTab to true .
Custom Emmet Snippets If you use custom Emmet snippets, you will have to modify them slightly to make them work in the new Emmet. HTML: Custom Emmet snippets in HTML should be a valid abbreviation. For example: use ul>li instead of <ul><li></li></ul> . CSS: Name the custom Emmet snippets in CSS such that they only contain letters from the snippet value in the order that they appear in the latter, so that the fuzzy matching algorithm of the suggestion list can make the right match.
For example, don't use bc or darkc as the name for color: black . Use cb or cob instead. Read more about the new Emmet in Emmet 2.0 blog post . Support for snippet choices With snippet choices, a placeholder can be prefilled with a set of values. The syntax is ${<number>|option_1,...,option_n|} . Below is a working sample specifying a fixed set of color choices: "color" : { "prefix" : "color" , "body" : "> Pick your favorite color ${1|red,green,blue,pink|}. \n < He likes $1." } Last but not least, when inserting snippets via IntelliSense a preview is now shown.
Improved diff editor results In this release, we made some changes to our diff algorithm to adjust the differences (which are found with the help of a Longest-Common-Substring algorithm) in such a way that they are more pleasing to the human eye. In some cases, this means we will be more aligned with the output of git diff (which also incorporates some of these heuristics), but in other cases (like when only trim whitespace has changed), our result will no longer contain the LCS, so it will be different than git diff , but in our opinion it will also be more pleasing.
Workbench User definable syntax highlighting colors Thanks to Cody Hoover (@hoovercj) , you can now customize the editor syntax highlighting colors in user settings. This is a great way to easily adjust your editor colors without creating a full color theme. The new color will be applied on top of the current theme. It will applied live and no reloading of VS Code is required. A pre-configured list of syntax tokens ('comments', 'strings', ...) is available for the most common constructs.
If you want more, you can do so by directly specifying TextMate theme color rules. Check out the theme section in our docs for more details. File Explorer sort order Thanks to Dmitry Zabello (@foreverest) , a new setting explorer.sortOrder configures how files and folders are sorted in the File Explorer. You can choose between: filesFirst - Sort files before folders mixed - Sort files and folders without separation
The rest of this page is on the live site.