Jump to content
Microsoft Windows Bulletin Board

Windows Terminal Preview 1.13 Release


Recommended Posts

Guest Kayla Cinnamon
Posted

Welcome to the first Windows Terminal release of 2022! This release will add the new features below to Windows Terminal Preview 1.13 and migrate Windows Terminal to version 1.12, which includes all of the features from this previous blog post. The Windows Terminal 1.12 build will be released through the Windows Insider Program before being delivered to retail versions of Windows. As always, you can install Windows Terminal and Windows Terminal Preview from the Microsoft Store or from the GitHub repository.

 

2757.png.4b584b86735dbf79bfcb30ef5b6b3a75.pngThe minimum supported version of Windows 10 for Windows Terminal 1.13+ has been increased from 18362 (19H1) to 19041 (20H1).

 

[HEADING=1]Updated settings UI design[/HEADING]

 

We’ve updated our settings UI to align with the new Windows 11 style, using WinUI 2.6. Please file any bugs you may find on our repo with this new design as we’re still ironing out the kinks. 1f60a.png.4734d4c0739d71cd48d14ddfcfbfc467.png

 

terminal-win11-sui.thumb.png.562e6eb4a2666a99bb14fc7d76a0c8a9.png

 

[HEADING=1]Auto-elevate profiles[/HEADING]

 

A new profile setting has been added called [iCODE]elevate[/iCODE] that allows you to automatically launch a profile as elevated (as Administrator). When set to [iCODE]true[/iCODE] and you are using an unelevated window, opening this profile will open an elevated window containing that profile. Otherwise, when set to [iCODE]false[/iCODE], this profile will open in the current window regardless of elevation. You can also hold Ctrl and click a profile in your dropdown to open it as Administrator.

 

terminal-elevate.thumb.png.86602a2d89afc341854e6b95d99802e5.png

 

Additionally, we added the [iCODE]elevate[/iCODE] argument to the [iCODE]new-tab[/iCODE] and [iCODE]split-pane[/iCODE] actions, allowing you to launch a new profile as elevated using an action. Here are some examples you can use to enable this feature:

 

// Profile setting
"elevate": true

// New tab action
{ "command": { "action": "newTab", "elevate": true }, "keys": "ctrl+shift+1" }

// Split pane action
{ "command": { "action": "splitPane", "split": "auto", "elevate": true }, "keys": "alt+shift+e" }

[HEADING=1]New rendering engine[/HEADING]

 

We’ve added a new profile setting, [iCODE]experimental.useAtlasEngine[/iCODE], that when set to [iCODE]true[/iCODE] will enable a new text rendering engine. While the performance improvements aren’t generally noticeable, they can be seen in certain edge cases, most notably when presenting text with a large number of colors. In these cases, this new renderer will draw at the display refresh rate regardless of screen resolution. Please note that the engine is still a work in progress, it may be unstable, and some of your favorite features may still be missing. We look forward to improving this renderer over time and will hopefully replace the existing one by default once it meets feature parity.

 

terminal-atlas.thumb.png.5cd7e0588856f7b27cc62f71cd7171ef.png

 

We admit this feature began with a kerfuffle we caused in the summer of 2021. When confronted with being told our rendering pipeline had terrible performance, we turned inward. We relied on our existing experiences and we leaned heavily on our partner teams’ work to conclude the DirectWrite general purpose renderer was the best fit for our product. We were wrong. As such, we dedicate this experimental renderer to the community as an olive branch. We know we have so much more to learn, but we hope that you will accept our apology and understand we’re humans behind this product with a capability and willingness to learn from our past mistakes. Thank you for sticking with us. We strive to make this an experience we can all learn from to not only improve ourselves, but to improve our product and delight you all.

 

[HEADING=1]Customizable bell sound[/HEADING]

 

You can now customize your profile’s bell sound using the [iCODE]bellSound[/iCODE] setting. This setting accepts a file path as a string, or an array of file path strings. While using an array, the terminal will randomly select a bell sound to play.

 

 

Thanks House House for letting us honk! 1f9a4.png.c01e7cf9c46a5d8ddc6b4e5d9b3528e2.png1f52a.png.92f05bca6d54f9465080c70c0e17a6f1.png

 

[HEADING=1]New actions[/HEADING]

 

26a1.png.b89330ce654c4c45b588051439af5472.png You can now restore recently closed tabs or panes with the new [iCODE]restoreLastClosed[/iCODE] action (Thanks @Rosefield!). Note: this will restore the profile in the tab/pane, but not the buffer history nor running command line applications.

 

26a1.png.f8f435ad76016d6028cc2b38ddd0162e.png The new [iCODE]exportBuffer[/iCODE] action lets you export the text within the buffer into a text file.

 

26a1.png.6d56491193e5d3be60ce01a032b0c4ae.png The new [iCODE]adjustOpacity[/iCODE] action allows you to change the opacity of the terminal window at runtime.

 

[HEADING=1]Miscellaneous improvements[/HEADING]

 

1f6e0.png.ea5758952b37536540d6f4b8d3751a65.png The terminal now supports snap layouts in Windows 11!

 

1f6e0.png.8cdaf42e353ae4fdc20f461dd04d1ec4.png The system context menu now has an item to open settings (Thanks @serd2011!).

 

1f6e0.png.2dbfea220fc9112ef208db6588c14458.png The background image path is now displayed in the settings UI (Thanks @ianjoneill!).

 

[HEADING=1]Bug fixes[/HEADING]

 

1f41b.png.01b3e6bb2cfd6ea0d6bd5276bdcffa27.png [iCODE]//wsl$/[/iCODE] paths and [iCODE]~[/iCODE] should now work as the starting directory for WSL distros.

 

1f41b.png.9d3984ff234b4532b292e0c28cf1d79a.png The Azure Cloud Shell profile can now be duplicated using the settings UI.

 

1f41b.png.c3b79c4f9b5f621b2d8010132ed94112.png Adjusting transparency will no longer re-enable acrylic when disabled.

 

1f41b.png.96c204b53fca751aa1a0af7739eed0c3.png The AltGr + Space key combination should now work correctly.

 

1f41b.png.e2c49511fe42e7bcca06e2b348f6485c.png AltGr should now work properly in the settings UI.

 

[HEADING=1]Top contributors[/HEADING]

 

We always appreciate working with the community and receiving contributions. Here are the contributors who have especially made an impact on this release:

 

[HEADING=2]Contributors who opened the most non-duplicate issues[/HEADING]

 

1f3c6.png.a970e81377ab272e948469dae0921896.png j4james

 

1f3c6.png.b1ac57014e4bed7ba61a4d187eb2753a.png elsaco

 

1f3c6.png.ea17454601164d99d07039596bdc9e87.png vefatica

 

[HEADING=2]Contributors who created the most merged pull requests[/HEADING]

 

1f3c6.png.3d39e384ff195caca1a0a22fc462dc59.png j4james

 

1f3c6.png.ae7f3fade866efc866e59702d83b1a9e.png serd2011

 

1f3c6.png.6150881f44ce97d1d8bd86177f114a3f.png ianjoneill

 

[HEADING=2]Contributors who provided the most comments on pull requests[/HEADING]

 

1f3c6.png.571d14a83064ee966b000dc71e2bf479.png j4james

 

1f3c6.png.1a3c6d4064aba8839f98654906f9606f.png LuanVSO

 

1f3c6.png.54d7fe5ee7376d9c6de9213a38e16d9d.png Rosefield

 

[HEADING=1]Cheers![/HEADING]

 

If you want to learn more about these new features, feel free to check out our docs site. If you have any questions, you can reach out to Kayla (@cinnamon_msft) on Twitter. If you find any bugs or have feature requests, feel free to file an issue on GitHub. We hope you enjoy this latest release of Windows Terminal!

 

2-2022-terminal-signatures.thumb.png.647ba8e90840a42975c7b4f6cc0687e5.png

 

The post Windows Terminal Preview 1.13 Release appeared first on Windows Command Line.

 

Continue reading...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...