{"id":6501,"date":"2021-03-01T10:00:47","date_gmt":"2021-03-01T18:00:47","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/commandline\/?p=6501"},"modified":"2021-03-01T10:00:47","modified_gmt":"2021-03-01T18:00:47","slug":"windows-terminal-preview-1-7-release","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/commandline\/windows-terminal-preview-1-7-release\/","title":{"rendered":"Windows Terminal Preview 1.7 Release"},"content":{"rendered":"

Welcome back to another release of Windows Terminal! This release migrates Windows Terminal<\/a> to version 1.6, which includes all of the features from this previous blog post<\/a> except for the settings UI. Windows Terminal Preview<\/a> will move to version 1.7, which includes all of the features described below. You can install both Windows Terminal and Windows Terminal Preview from the Microsoft Store or from the GitHub releases page<\/a>. Let’s check out what’s new!<\/p>\n

JSON fragment extensions<\/h2>\n

Windows Terminal now supports JSON fragment extensions. This means that snippets of JSON can be downloaded as extensions that can modify a user’s settings. You can create a folder that includes the JSON snippet file as well as other assets such as background images to include in your extension. This is especially useful for applications who want a specific color scheme to go with their executable or for a community member to share their Windows Terminal configuration with just a simple download. Full documentation on how to create a JSON fragment extension can be found on our docs site<\/a>.<\/p>\n

Windowing improvements<\/h2>\n

You can now set new terminal windows to launch in an already existing terminal instance! This can be done in a few different ways:<\/p>\n

A new global setting has been added called windowingBehavior<\/code>, which allows you to set where new instances of Windows Terminal launch. Options include a new window (\"useNew\"<\/code>), an already existing window (\"useAnyExisting\"<\/code>), and an already existing window on this desktop (\"useExisting\"<\/code>). This setting can be found on the Startup page of the settings UI.<\/p>\n

\"windowingBehavior\": \"useNew\"\n<\/code><\/pre>\n
\"Image<\/a><\/p>\n
We have a new action called newWindow<\/code>, which allows you to open a new window with the command palette and\/or your keyboard.<\/p>\n
{ \"command\": \"newWindow\", \"keys\": \"ctrl+shift+n\" }\n<\/code><\/pre>\n
There’s a new command line argument for running commands in specific windows as well. You can use --window,-w <window-id><\/code> with wt.exe<\/code> to specify which terminal window you’d like to interact with.<\/p>\n
\/\/ Open a new tab with the default profile in the current window\nwt -w 0 new-tab\n\n\/\/ Open a new tab with the default profile in the third-created terminal window\nwt -w 3 new-tab\n\n\/\/ Open a new tab with the default profile in a new window\nwt -w -1 new-tab\n<\/code><\/pre>\n
\"Image<\/a><\/p>\n
Read-only panes<\/h2>\n
Windows Terminal now supports read-only panes (Thanks @Don-Vito<\/a>!). This allows you to prevent input into a pane, which could be useful if you have a build or process running that you don’t want to interrupt. If you attempt to close or input text into a read-only pane, the terminal will display a popup warning instead. You can toggle read-only mode on a pane with the toggleReadOnlyMode<\/code> action.<\/p>\n
{ \"command\": \"toggleReadOnlyMode\" },\n<\/code><\/pre>\n
\ud83d\udc49 Note:<\/strong> This action is bound by default in the command palette, however it does not have keys attached to it.<\/p>\n
\"Image<\/a><\/p>\n
Automatically focus on mouse hover<\/h2>\n
A new setting has been added where you can automatically focus a pane when it’s hovered with the mouse (Thanks @Don-Vito<\/a>!). This new global setting can be found on the Interaction page of the settings UI or can be set in your settings.json with focusFollowMouse<\/code>.<\/p>\n
\"focusFollowMouse\": true\n<\/code><\/pre>\n
\ud83d\udc49 Note:<\/strong> This setting is set to false<\/code> by default.<\/p>\n
\"Image<\/a><\/p>\n
Settings UI updates<\/h2>\n
We are still actively working on improving the settings UI experience. Here are some updates with this release:<\/p>\n
Settings UI is now default<\/h3>\n
The settings UI is now attached to the Settings button in the dropdown menu, making it the default experience for those using Windows Terminal Preview. If you’d like to use the keyboard to access your settings, here are the shortcuts that come with the terminal by default:<\/p>\n