{"id":8607,"date":"2023-05-24T09:55:36","date_gmt":"2023-05-24T16:55:36","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/commandline\/?p=8607"},"modified":"2023-09-25T15:47:19","modified_gmt":"2023-09-25T22:47:19","slug":"windows-terminal-preview-1-18-release","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/commandline\/windows-terminal-preview-1-18-release\/","title":{"rendered":"Windows Terminal Preview 1.18 Release"},"content":{"rendered":"

Welcome back to another Windows Terminal release! This release updates Windows Terminal to version 1.17 and includes all of the features from this previous blog post<\/a>. Additionally, Windows Terminal Preview is getting an update to version 1.18 and will include all the features detailed here, so let’s talk all about them!<\/p>\n

As always, you can install Windows Terminal<\/a> and Windows Terminal Preview<\/a> from the Microsoft Store, from the GitHub releases page<\/a>, or by using winget.<\/p>\n

Tab Tearout<\/h2>\n

Yes! We finally have tab tearout! This has been a highly requested feature since the dawn of Terminal time. Starting in Windows Terminal Preview 1.18, you will now be able to tear out the tabs in Windows Terminal.<\/p>\n

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

You will also be able to move tabs from one terminal window into the other.<\/p>\n

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

Environment Variable Updates<\/h2>\n

The Windows Terminal will now reload the environment variables automatically when a new tab or pane is opened! No longer do you need to fully shut down the Terminal after installing something and changing the PATH – just open a new tab (or restart the current one) and head off to the races.<\/p>\n

In addition, you can now add environment variables in your settings.json<\/code>. Shoutout to @ianjoneill<\/a> for this community-contributed feature! This can be done in defaults<\/code> or in any profile.
\nIn the example below, I set two environment variables, both named MY_ENVIRONMENT_VARIABLE<\/code>, in defaults<\/code> and in my PowerShell<\/code> profile:<\/p>\n

JSON<\/h3>\n
\"profiles\": \n    {\n        \"defaults\": \n        {\n            \"environment\": {\n                \"MY_ENVIRONMENT_VARIABLE\": \"Hi from defaults!\"\n            },\n        },\n        \"list\": \n        [\n            {\n                \"guid\": \"{574e775e-4f2a-5b96-ac1e-a2962a402336}\",\n                \"name\": \"PowerShell\",\n                \"source\": \"Windows.Terminal.PowershellCore\",\n                \"environment\": \n                {\n                    \"MY_ENVIRONMENT_VARIABLE\": \"Hi from PowerShell!\"\n                }\n            }\n        ]\n    }\n<\/code><\/pre>\n
The environment variables you set in defaults<\/code> will be available to all of your profiles. The environment variables that you set within a specific profile will only be available for that specific profile.<\/p>\n
This means that if I print the value of MY_ENVIRONMENT_VARIABLE<\/code> in my PowerShell profile, then I will see “Hi from PowerShell!”<\/p>\n
\"MY_ENVIRONMENT_VARIABLE<\/a><\/p>\n
If I print the value of MY_ENVIRONMENT_VARIABLE<\/code> in any other profile such as Command Prompt, then I will see “Hi from defaults!”<\/p>\n
\"MY_ENVIRONMENT_VARIABLE<\/a><\/p>\n
Right-Click Context Menu (Experimental)<\/h2>\n
This is an experimental feature that needs to be manually enabled. To manually enable this feature, add \"experimental.rightClickContextMenu\": \"true\"<\/code> in the defaults<\/code> section of your profiles<\/code> section of your settings.json<\/code>:<\/p>\n
JSON<\/h3>\n
\"profiles\": \n{\n    \"defaults\": \n    {\n        \"experimental.rightClickContextMenu\": true\n    },\n    ...\n<\/code><\/pre>\n
After enabling this feature, you will be able to see a context menu after right-clicking the shell in your terminal.<\/p>\n
\"Moving<\/a><\/p>\n
By default, you will see Paste, Split Pane, Duplicate Tab, and Close Tab as your options.
\nIf you highlight text and open the right click context menu, you will also see a Copy option next to Paste. If you have another pane open, then you will also see Close Pane as another option.<\/p>\n
If you have our experimental shell integration feature enabled, then you will also see Select Command and Select Output as options.<\/p>\n
\"Shell<\/a><\/p>\n
Enabling shell integration marks vary from shell to shell. To learn how to enable shell integration for your favorite shell, visit this Shell integration tutorial<\/a> to find out more!<\/p>\n
Atlas Engine Improvements<\/h2>\n
Our experimental text rendering engine, the AtlasEngine<\/code>, has gotten major improvements in Windows Terminal Preview 1.18. This text rendering engine has been nearly, completely rewritten to support overlapping text and, as a result, will no longer cut off italic text, emojis, or complex scripts. It will continue to clip box glyphs to their cells.
\nBelow is a series of “before” and “after” pictures of the Atlas Engine rewrites.<\/p>\n
Here is a before image of Fira Code with the old AtlasEngine<\/code><\/p>\n
\"Old<\/a>
\nHere is an after image of Fira Code with our new AtlasEngine<\/code> in 1.18 Preview.<\/p>\n
\"AtlasEngine<\/a>
\nWe can see that the old AtlasEngine shrinks glyphs. In our new AtlasEngine, we now handle those glyphs correctly.<\/p>\n
We also have a before image of the Code New Roman font as an example.<\/p>\n
\"Old<\/a><\/p>\n
Here is an after image for the Code New Roman font with AtlasEngine<\/code> in 1.18 Preview.<\/p>\n
\"Old<\/a><\/p>\n
In the screenshots above, you can see how our AtlasEngine<\/code> rewrite in 1.18 Preview fixed powerline rendering. We now have no weird gaps, no cut off glyphs, and no shrunken glyphs. There is now also proper overlapping glyphs in the APL set, \u2714\ufe0f in the Misc. glyphs row, and proper inversion of complex Unicode (without making the glyphs larger than they are supposed to be.)<\/p>\n
We have also ensured that the AtlasEngine<\/code> continues to support animated shaders, Han unification, and loc1<\/code> glyph variants in Windows Terminal Preview 1.18. The AtlasEngine<\/code> will also now be used to display the Appearance preview in the Windows Terminal Settings UIs for profiles which it is enabled.<\/p>\n
Portable Mode<\/h2>\n
As of stable channel version 1.17, Windows Terminal will support being deployed in “Portable mode”. Portable mode ensures that all data created and maintained by Windows Terminal is saved next to the application so that it can be more easily moved across different environments.<\/p>\n
Portable mode is supported by the unpackaged “ZIP” distribution. This is an officially-supported mode of execution where Windows Terminal stores its settings in a settings folder next to WindowsTerminal.exe<\/code>. Portable mode is not supported in the packaged or preinstallation kit distributions of Windows Terminal.<\/p>\n
The unpackaged and portable mode distributions of Windows Terminal allow you to use Terminal without installing it globally, e.g. on systems where you may not have permission to install MSIX packages or download software from the Microsoft Store. Portable mode allows you to carry around or archive a preconfigured installation of Windows Terminal and run it from a network share, cloud drive or USB flash drive. Any such installation is self-contained and will not interfere with other installed distributions of Windows Terminal.<\/p>\n
Portable mode needs to be enabled manually. After unzipping the Windows Terminal download, create a file named .portable<\/code> next to WindowsTerminal.exe<\/code>.
\nWindows Terminal will automatically create a directory named settings<\/code> after you launch WindowsTerminal.exe<\/code>. That settings<\/code> directory will store both settings and runtime state such as window layouts.<\/p>\n
Note that Windows Terminal will NOT automatically reload its settings and transform your terminal into portable mode right after you create the .portable<\/code> file.
\nThis change will only apply after you relaunch Terminal. You can verify if you are in portable mode, by selecting “About” in the dropdown menu.<\/p>\n
\"Windows<\/a><\/p>\n
From here, you can customize Windows Terminal to your liking and then copy that entire Windows Terminal folder to a USB flash drive or network share to use on the go or to share with others!<\/p>\n
For more information on the various distribution types that Windows Terminal offers, please see our distribution docs<\/a>!<\/p>\n
Usability Updates<\/h2>\n
\u26a1 Windows Terminal can now use Ctrl+Shift<\/kbd> to run terminal elevated from the context menu (thanks @jamespack<\/a>!)<\/p>\n
\u26a1 Users can now enable and disable read-only mode rather than toggling it with the enableReadOnly<\/code> and disableReadOnly<\/code> actions (thanks @Swinkid<\/a>!)<\/p>\n
\u26a1 We added “legacy” themes to our available default themes. Check them out in the Settings UI!<\/p>\n
\u26a1 We improved the preview text in the Settings UI and enabled the cursor<\/p>\n
\u26a1 Users can now customize cell sizes and line spacing<\/p>\n
\u26a1 A warning now appears when a proportional font is selected (thanks again @jamespack<\/a>!)<\/p>\n
\u26a1 We added an action to immediately restart a connection (restartConnection<\/code>). You also manually invoke this menu with a keyboard shortcut by binding a keybinding instead<\/p>\n
\u26a1 We added an action to manually invoke the control context menu<\/p>\n
\u26a1 Added jump list support for indirect icon references (thanks yet again @jamespack<\/a>!)<\/p>\n
\u26a1 $theme.tab.showCloseButton<\/code> now supports activeOnly<\/code>, to display the x only on the active tab (thanks @kovdu<\/a>!)<\/p>\n
\u26a1 Any WSL distribution named rancher-desktop<\/code> or rancher-desktop-data<\/code> will be ignored. Thanks for helping us with this, @jamespack<\/a>. For more information on this change, please see issue #12757 on GitHub<\/a>.<\/p>\n
Miscellaneous Improvements<\/h2>\n
\ud83d\udee0\ufe0f Added support for horizontal margin sequences (thanks @j4james<\/a>!)<\/p>\n
\ud83d\udee0\ufe0f Added support for bracketed paste mode in ConHost (thanks again @j4james<\/a>!)<\/p>\n
\ud83d\udee0\ufe0f Added support for CSI 18t (thanks @michalnpl<\/a>!)<\/p>\n
\ud83d\udee0\ufe0f Added subtext to why “Always show tabs” is not toggleable in the Settings UI (thanks @BenConstable9<\/a>!)<\/p>\n
\ud83d\udee0\ufe0f The reset button is now accessible with description in reset (thanks @michalnpl<\/a>!)<\/p>\n
\ud83d\udee0\ufe0f We refactored how connection restart is handled and added an action for restartConnection<\/code> for manually restarting a tab or pane<\/p>\n
\ud83d\udee0\ufe0f If you are using the FTCS “start of command”, “start of output” and “end of output” marks (OSC 133<\/code>), you can now use the selectCommand<\/code> and selectOutput<\/code> actions to select the command or output as demarcated by those sequences<\/p>\n
Bug Fixes<\/h2>\n
\ud83d\udc1b Active attributes are now preserved during Virtual Terminal (VT) resize operations (thanks @j4james<\/a>!)<\/p>\n
\ud83d\udc1b LineFeed<\/code> and PrintString<\/code> functionality is now merged into AdaptDispatch<\/code> (thanks again @j4james<\/a>!)<\/p>\n
\ud83d\udc1b ConHost now respects the codepage stored in .LNK<\/code> files (thanks @michalnpl<\/a>!)<\/p>\n
\ud83d\udc1b Windows Terminal will now focus on the shell instead of the titlebar when a profile is selected from a nested menu entry (thanks @kkostrzewa<\/a>!)<\/p>\n
\ud83d\udc1b We now manually pre-evaluate the starting directory when calling elevate-shim<\/code><\/p>\n
\ud83d\udc1b We now use a “virtual CWD” for each terminal window<\/p>\n
\ud83d\udc1b We fixed a bug in default terminal startup that should fix some apps that immediately print lots of text to the console<\/p>\n
\ud83d\udc1b We now use the persisted position with centerOnLaunch:true<\/code><\/p>\n
Top contributors<\/h2>\n
We love working with the community and recognizing those who made an impact for each release. Here are the community members who helped out for this one!<\/p>\n
Contributors who created the most merged pull requests<\/h3>\n
\ud83c\udfc6 j4james<\/a><\/p>\n
\ud83c\udfc6 jamespack<\/a><\/p>\n
\ud83c\udfc6 ianjoneill<\/a><\/p>\n
Contributors who opened the most non-duplicate issues<\/h3>\n
\ud83c\udfc6 j4james<\/a><\/p>\n
\ud83c\udfc6 Saiteja341<\/a><\/p>\n
\ud83c\udfc6 Vampire<\/a><\/p>\n
Contributors who provided the most comments on pull requests<\/h3>\n
\ud83c\udfc6 j4james<\/a><\/p>\n
\ud83c\udfc6 jamespack<\/a><\/p>\n
\ud83c\udfc6 ianjoneill<\/a><\/p>\n
I would also like to give additional recognition to @kovdu<\/a>, @Swinkid<\/a>, @Yovach<\/a>, and  MikuAuahDark <\/a> for their help on documentation, code health, grammar, spelling, workflow security and maintenance!<\/p>\n
Mahalo!<\/h2>\n
We hope you enjoy this latest release of Windows Terminal Preview! More information on these new features can be found on our docs site<\/a> and if you find any bugs or have feature requests, feel free to file them on GitHub<\/a>. If you have any questions you can reach out to Christopher Nguyen (@nguyen_dows<\/a>) on Twitter.<\/p>\n
Thank you!<\/p>\n
\"2023<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
Welcome back to another Windows Terminal release! This release updates Windows Terminal to version 1.17 and includes all of the features from this previous blog post. Additionally, Windows Terminal Preview is getting an update to version 1.18 and will include all the features detailed here, so let’s talk all about them! As always, you can […]<\/p>\n","protected":false},"author":101092,"featured_media":8622,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[10,1,2,1535,1728,6,782],"tags":[],"class_list":["post-8607","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-cmd","category-commandline","category-command-line","category-open-source","category-windows","category-windows-console","category-windows-terminal"],"acf":[],"blog_post_summary":"
Welcome back to another Windows Terminal release! This release updates Windows Terminal to version 1.17 and includes all of the features from this previous blog post. Additionally, Windows Terminal Preview is getting an update to version 1.18 and will include all the features detailed here, so let’s talk all about them! As always, you can […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/commandline\/wp-json\/wp\/v2\/posts\/8607","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\/101092"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/commandline\/wp-json\/wp\/v2\/comments?post=8607"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/commandline\/wp-json\/wp\/v2\/posts\/8607\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/commandline\/wp-json\/wp\/v2\/media\/8622"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/commandline\/wp-json\/wp\/v2\/media?parent=8607"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/commandline\/wp-json\/wp\/v2\/categories?post=8607"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/commandline\/wp-json\/wp\/v2\/tags?post=8607"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}