{"id":5545,"date":"2020-04-22T10:12:04","date_gmt":"2020-04-22T17:12:04","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/commandline\/?p=5545"},"modified":"2020-05-15T12:05:17","modified_gmt":"2020-05-15T19:05:17","slug":"windows-terminal-preview-v0-11-release","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/commandline\/windows-terminal-preview-v0-11-release\/","title":{"rendered":"Windows Terminal Preview v0.11 Release"},"content":{"rendered":"

We are back with one last major update before the 1.0 release of Windows Terminal! Releases between now and then will be revisions of this version. This is the v0.11 release and you can download the Terminal from the Microsoft Store<\/a> or from the GitHub releases page<\/a>. Let’s see what has changed with this update!<\/p>\n

\"Image<\/a> Azure visualization – https:\/\/github.com\/msleal\/asciivmssdashboard<\/a><\/em><\/p>\n

Localization<\/h2>\n

This is the first Windows Terminal version that has support for non-English UI languages. We are still working out the bugs with this, so please bear with us. \ud83d\ude0a If you find any translation issues, please file them on our GitHub<\/a>!<\/p>\n

Settings updates<\/h2>\n

We have made some changes to our settings that we’d like to bring to your attention. We recommend you move your settings file out of the folder and have the Terminal automatically generate a new one. Then, you can copy your settings back over.<\/p>\n

Settings.json<\/h3>\n

The profiles.json file has been renamed to settings.json. If you already have the Terminal installed, your file name will automatically update.<\/p>\n

Cascadia Code<\/h3>\n

Cascadia Code<\/a> has been set as the default font for all profiles automatically generated by the Terminal. If you want to change your font, you can add the fontFace<\/code> property to any profile or to the defaults<\/code> section.<\/p>\n

Tango color schemes<\/h3>\n

Terminal now ships with the Tango Dark and Tango Light color schemes.<\/p>\n

\"Image<\/a><\/p>\n

\"Image<\/a><\/p>\n

Copy and paste<\/h3>\n

Copy and paste are bound to ctrl+c<\/code> and ctrl+v<\/code>, respectively, in the newly generated settings.json file. This means these key bindings will work alongside ctrl+shift+c<\/code> and ctrl+shift+v<\/code> and you can easily remove them. Ctrl+shift+c<\/code> and ctrl+shift+v<\/code> are still included in the defaults.json file, so you will still have a key combination you can use to copy and paste if you choose to remove ctrl+c<\/code> and ctrl+v<\/code>.<\/p>\n

\ud83d\udc49 Note:<\/strong> If you want to free up a default key combination, you can set it to unbound<\/code> or null<\/code> in your settings.json file.<\/p>\n

{ \"command\": \"unbound\", \"keys\": \"ctrl+shift+c\" },\n{ \"command\": null, \"keys\": \"ctrl+shift+v\" }\n<\/code><\/pre>\n
Formatted copying<\/h3>\n
We have changed the default behavior of copying to copy plain text by default. A new global setting has been added to the newly generated settings.json file called copyFormatting<\/code>. This is set to false<\/code> by default, however you can change it to true<\/code> to always copy the HTML and RTF formatting.<\/p>\n
\ud83d\udc49 Note:<\/strong> In defaults.json, copyFormatting<\/code> is set to true<\/code> in order to not break existing users.<\/p>\n
Removed settings<\/h3>\n
In preparation for v1.0, we have removed some previously deprecated settings. We know this will likely impact your workflows, but we are hoping this is a one-time event.<\/p>\n
“Globals” namespace<\/h4>\n
The Terminal no longer supports the globals<\/code> property in the JSON file. If you have settings inside the globals<\/code> object, they will be ignored. To fix this, remove the globals<\/code> object and move your global settings into the root of the JSON file.<\/p>\n
Application theme<\/h4>\n
The global setting requestedTheme<\/code> has been renamed to theme<\/code>. This helps clean up the naming and provide flexibility for theming in the future.<\/p>\n
\"theme\": \"system\"\n<\/code><\/pre>\n
Copying as a single line<\/h4>\n
The copyTextWithoutNewlines<\/code> command and the argument trimWhitespace<\/code> for copy<\/code> have been removed in favor of the singleLine<\/code> argument. This naming change helps better explain how the feature works. If you enable this as true for a copy<\/code> key binding, the content copied from the Terminal will be on one line when pasted.<\/p>\n
{ \"command\": { \"action\": \"copy\", \"singleLine\": true ), \"keys\": \"ctrl+alt+c\" }\n<\/code><\/pre>\n
Creating a tab of a specific profile<\/h4>\n
The first iteration of creating a new tab of a specific profile had key binding commands from newTabProfile0<\/code> to newTabProfile8<\/code>. We removed these commands in favor of a more flexible alternative.<\/p>\n
\ud83d\udc49 Note:<\/strong> Indexing in the Terminal starts at 0.<\/p>\n
{ \"command\": { \"action\": \"newTab\", \"index\": NUMBER }, \"keys\": \"ctrl+shift+NUMBER\" }\n<\/code><\/pre>\n
Navigating to a specific tab<\/h4>\n
Tab navigation now has the same structure as new tab creation, where switchToTab0<\/code> through switchToTab8<\/code> have been removed in favor of the index<\/code> property.<\/p>\n
\ud83d\udc49 Note:<\/strong> Indexing in the Terminal starts at 0.<\/p>\n
{ \"command\": { \"action\": \"switchToTab\", \"index\": NUMBER }, \"keys\": \"ctrl+alt+NUMBER\" }\n<\/code><\/pre>\n
Splitting panes<\/h4>\n
To allow for more options when splitting panes, the splitHorizontal<\/code> and splitVertical<\/code> commands have been removed in favor of the new key binding format. Additionally, if you don’t provide a split direction, the Terminal will default to splitting using auto<\/code>, which will split to provide the largest surface area.<\/p>\n
{ \"command\": { \"action\": \"splitPane\", \"split\": \"horizontal\"}, \"keys\": \"alt+shift+-\" },\n{ \"command\": { \"action\": \"splitPane\", \"split\": \"vertical\"}, \"keys\": \"alt+shift+plus\" }\n<\/code><\/pre>\n
Focusing between panes<\/h4>\n
Originally, you could use moveFocusDown<\/code>, moveFocusUp<\/code>, moveFocusLeft<\/code>, moveFocusRight<\/code> as key binding commands to navigate between panes. We have removed these and have added the following formats as replacements:<\/p>\n
{ \"command\": { \"action\": \"moveFocus\", \"direction\": \"down\" }, \"keys\": \"alt+down\" },\n{ \"command\": { \"action\": \"moveFocus\", \"direction\": \"up\" }, \"keys\": \"alt+up\" },\n{ \"command\": { \"action\": \"moveFocus\", \"direction\": \"left\" }, \"keys\": \"alt+left\" },\n{ \"command\": { \"action\": \"moveFocus\", \"direction\": \"right\" }, \"keys\": \"alt+right\" }\n<\/code><\/pre>\n
Resizing panes<\/h4>\n
To follow the same key binding architecture, the pane resizing commands (resizePaneDown<\/code>, resizePaneUp<\/code>, resizePaneLeft<\/code>, resizePaneRight<\/code>) have been removed. Below is the new format for resizing panes.<\/p>\n
{ \"command\": { \"action\": \"resizePane\", \"direction\": \"down\" }, \"keys\": \"alt+shift+down\" },\n{ \"command\": { \"action\": \"resizePane\", \"direction\": \"up\" }, \"keys\": \"alt+shift+up\" },\n{ \"command\": { \"action\": \"resizePane\", \"direction\": \"left\" }, \"keys\": \"alt+shift+left\" },\n{ \"command\": { \"action\": \"resizePane\", \"direction\": \"right\" }, \"keys\": \"alt+shift+right\" }\n<\/code><\/pre>\n
Changing the font size<\/h4>\n
The following key binding commands allowed you to change your font size, but they are now removed: decreaseFontSize<\/code>, increaseFontSize<\/code>.<\/p>\n
You can modify your font size by using the below key bindings, which use a delta<\/code> that defines the font size change in points.<\/p>\n
{ \"command\": { \"action\": \"adjustFontSize\", \"delta\": -1 }, \"keys\": \"ctrl+-\" },\n{ \"command\": { \"action\": \"adjustFontSize\", \"delta\": 1 }, \"keys\": \"ctrl+=\" }\n<\/code><\/pre>\n
Bug fixes<\/h2>\n
\ud83d\udc1b The lines that appeared between solid blocks of background color are gone!<\/p>\n
\ud83d\udc1b Command line arguments should trigger more reliably in the order you expect them to.<\/p>\n
\ud83d\udc1b The input stack has been changed to address some issues with non-US-104 QWERTY keyboard layouts.<\/p>\n
\ud83d\udc1b The window borders now respect your application theme.<\/p>\n
Top Contributors<\/h2>\n
We love working with the community on GitHub and we’d like to recognize some individual contributors who have made an impact on this release!<\/p>\n
Contributors Who Opened the Most Non-Duplicate Issues<\/h3>\n
\ud83c\udfc6 Qantex<\/a><\/p>\n
\ud83c\udfc6 j4james<\/a><\/p>\n
\ud83c\udfc6 codeofdusk<\/a><\/p>\n
\ud83c\udfc6 AnuthaDev<\/a><\/p>\n
\ud83c\udfc6 Chips1234<\/a><\/p>\n
Contributors Who Created the Most Merged Pull Requests<\/h3>\n
\ud83c\udfc6 pi1024e<\/a><\/p>\n
\ud83c\udfc6 j4james<\/a><\/p>\n
\ud83c\udfc6 jsoref<\/a><\/p>\n
Contributors Who Provided the Most Comments on Pull Requests<\/h3>\n
\ud83c\udfc6 jsoref<\/a><\/p>\n
\ud83c\udfc6 pi1024e<\/a><\/p>\n
\ud83c\udfc6 j4james<\/a><\/p>\n
Until next time<\/h2>\n
We hope you’ve been enjoying the Windows Terminal so far and we’re eager to release v1.0 very soon. If you have any questions or feedback, feel free to reach out to Kayla on Twitter (@cinnamon_msft<\/a>). If you find any bugs or would like to file a feature request, you can create a new issue on our GitHub page<\/a>. We’ll see you soon with our 1.0 release!<\/p>\n
\"\"<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
We are back with one last major update before the 1.0 release of Windows Terminal! Releases between now and then will be revisions of this version. This is the v0.11 release and you can download the Terminal from the Microsoft Store or from the GitHub releases page. Let’s see what has changed with this update! […]<\/p>\n","protected":false},"author":3539,"featured_media":5559,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[10,1,2,3,4,5,6,8,9,782],"tags":[22,27,29,31,42,45,59,69,70,72],"class_list":["post-5545","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-cmd","category-commandline","category-command-line","category-linux-tools","category-ms-dos","category-windows-10","category-windows-console","category-windows-store","category-bash-on-ubuntu-on-windows","category-windows-terminal","tag-bash","tag-cmd","tag-command-line","tag-console","tag-linux","tag-ms-dos","tag-terminal","tag-windows","tag-windows-10","tag-wsl"],"acf":[],"blog_post_summary":"
We are back with one last major update before the 1.0 release of Windows Terminal! Releases between now and then will be revisions of this version. This is the v0.11 release and you can download the Terminal from the Microsoft Store or from the GitHub releases page. Let’s see what has changed with this update! […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/commandline\/wp-json\/wp\/v2\/posts\/5545","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/commandline\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/commandline\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/commandline\/wp-json\/wp\/v2\/users\/3539"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/commandline\/wp-json\/wp\/v2\/comments?post=5545"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/commandline\/wp-json\/wp\/v2\/posts\/5545\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/commandline\/wp-json\/wp\/v2\/media\/5559"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/commandline\/wp-json\/wp\/v2\/media?parent=5545"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/commandline\/wp-json\/wp\/v2\/categories?post=5545"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/commandline\/wp-json\/wp\/v2\/tags?post=5545"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}