Windows 10: How to set New Windows Terminal as default console.

/u/datius · Dec 5, 2020

Anyone know how to set the new awesome Windows Terminal as default? If I go through the extension selector it doesn't find a program to be able to choose, it just directs me to the store, where I have already downloaded and ran WT.

submitted by /u/datius
[link] [comments]

:)

Brink · Dec 5, 2020

New Windows Terminal Preview v1.2.2022.0 update for Windows 10 July 22

Features

We're flighting very early support for a "command palette", which will provide quick access to every Terminal feature (#6635)

If you bind commandPalette (I recommend Ctrl+Shift+P), you can open a filterable list
of every action Terminal can perform.

This is a great way to find "focus mode" and "always on top" mode! (see below)

We've added two window management features, "focus mode" and "always on top" (#6804) (#6903)

Focus mode removes the tab bar and caption buttons, and always on top mode always-on-tops the window.

Right now, they're accessible via the toggleFocusMode and toggleAlwaysOnTop action bindings. They are not bound to keys by default.

Terminal has learned to pop up warning dialogs about clipboard content (thanks @greg904!) (#6631)

Pasting content over 5 KiB in length will result in a confirmation dialog.

This can be disabled with the global setting largePasteWarning (boolean, default true)

Pasting content that contains newline characters will result in a confirmation dialog.

This can be disabled with the global setting multiLinePasteWarning (boolean, default true)

There is a handful of new action bindings, none of which are bound by default:

renameTab (activates the tab title text field) (thanks @ggadget6) (#6557)

toggleRetroEffect (#6691)

setTabColor and openTabColorPicker (#6567)

This version of Windows Terminal ships with Cascadia Code 2007.15.

Changes

The rowsToScroll setting has been removed (#6891).

It was added to work around precision touchpad scrolling issues, which we fixed correctly before 1.0

Terminal will now follow the system's "lines to scroll" setting.

In addition, it will no longer scroll backwards when the system setting is set to "one page at a time"

The terminal will no longer jump to the bottom when you're scrolled up or when you have a selection (#6062)

Holding down Shift while clicking has always expanded your selection. Now, however, you can take it two or three steps further by holding down Shift and double- or triple-clicking (#6322)

You can now double-click a tab to rename it (thanks @greg904!) (#6628)

wt will now accept shorthand nt, sp, ft versions of new-tab, split-pane, and focus-tab on the commandline (#6576)

Our window borders will now always be unobtrusive, even when your system theme is light (thanks @greg904!) (#6624)

The Solarized color schemes have been updated to fix "bright black" and "normal black" having been swapped (thanks @M-Pixel!) (#6985).

PowerShell's PSReadline prefers bright black to render command parameters, which rendered (!) them totally unreadable on Solarized Dark

We can now hot reload a bunch of renderer settings like the experimental retro terminal effect and the software rendering flag (#6551)

UI

Thanks to @jtippet, Terminal's UI is now fives of times more accessible in high contrast mode (#6833) (#6910)

This includes beautiful new icons (

) (#6915)

Thanks again to @jtippet, our "new tab" button now looks much closer to the rest of the tab strip in shape and color (#6766) (#6812)

You can now start selections from the padding area (#6343)

Terminal Basics

Color representation has been significantly improved (thanks @j4james!)

In the old days (read: before 1.2), Terminal would try to map colors coming out of applications to their
nearest paletted color index. This was inherently lossy.

The pseudoconsole will now forward colors and styles emitted by applications with higher fidelity (#6506)

We've added heuristic detection for applications using the traditional Win32 console API to set "defaulted" background/foreground colors (#6698)

PowerShell in particular required additional workarounds (#6810) (PowerShell/PSReadline#1626)

This required us to break and then somewhat fix DECSCNM (full screen inversion) (#6809)

We can now render additional graphical attributes (thanks @j4james!)

SGR 4, "faint" (#6873)

Faint text will be rendered at roughly half intensity.

SGR 8, "concealed" (#6907)

Concealed text will not be visible, but it will be copyable to the clipboard and read out by screen readers.

SGR 53, "overline" (#6754)

It's like an underline, but not so much "under" as "over".

Care about SGRs a lot? Follow #6879 for yet more SGRs.

Commandline applications can now put text on the clipboard using OSC 52 (thanks @uzxmx!) (#5823)

Terminal (and conhost) will now be able to answer queries for further device attributes (DA2, DA3) (thanks @j4james!) (#6850)

Bug Fixes

You can now run wt as an Administrator from the Run dialog with Ctrl+Shift+Enter (#6860)

This is a workaround for MSFT:25907286.

This change also fixes the issue where running wt from powershell would render your existing session inoperable.

App execution aliases aren't real executables, so they've got all sorts of fun caveats!

Precision touchpads have been reined in and will no longer dispatch untold many VT mouse events on scroll (#6843)

The hard reset sequence will now properly result in the entire terminal being reset (thanks @j4james!) (#6763)

Terminal should no longer crash when you read its contents with Narrator's "scan mode" (#6447)

Performance

We've made a good number of behind-the-scenes performance improvements:

"Improved ATTR_ROW::ReplaceAttrs performance" (thanks @lhecker!) (#6573)

"Improve bitmap::_calculateArea performance" (thanks @lhecker!) (#6572)

"Recycle assorted rendering components to accelerate drawing" (#6483)

"Restore simple text runs, correct for crashes" (#6695)

"Avoid copying the bitmap on the way into the tracing function" (#6839)

"Cache VT buffer line string to avoid (de)alloc on every paint" (#6840)

"Cache the size viewport structure inside TextBuffer" (#6841)

"Cache the viewport to make invalidation faster" (#6918)

Click to expand...

Source:

https://github.com/microsoft/termina...ag/v1.2.2022.0

https://devblogs.microsoft.com/comma...w-1-2-release/

Microsoft Store: https://www.microsoft.com/en-us/p/wi...w/9n8g5rfz9xk3

See also: New Windows Terminal v1.1.2021.0 released for Windows 10 - July 22

Tweet

— Twitter API (@user) View on Twitter
Click to expand...

Brink · Dec 5, 2020

New Windows Terminal Preview v1.3.2382.0 update for Windows 10 Aug. 26

Features

We're trying out a new tab switching experience! (#6732), followups: (#7263) (#7280) (#7321)

The nextTab and prevTab bindings will now display an ephemeral UI that can be navigated with the mouse or keyboard

If you would like to fall back to the original tab-switching UI (or lack thereof), set new useTabSwitcher (global, boolean, default true) to false.

We'd love feedback on why the new tab switcher didn't work for you!

Building on the infrastructure from the tab switcher, we're also flighting support for a new tab search/jump experience

Bind the "tabSearch" action ({"command": "tabSearch", "keys": ...}) to open up a filterable list of open tabs!

The "command palette" introduced in 1.2 is now bound to Ctrl+Shift+P by default (#7384)

It has gained support for nested/repeated commands (#7299) (#6856) that can iterate over profiles and color schemes (#7329)

We've shipped a couple convenience commands, like "set color scheme to ..." and "open split pane with ... in direction ..." (#7348)

By starting your command with >, you can enter "commandline" mode and run any wt startup script, like > new-tab ; split-pane (#7293)

It now has support for command icons! (#7368)

We've added support for a new action, wt, that lets you run any WT commandline in your current session (#6537)

Example: { "command": { "action": "wt", "commandline": "split-pane -p Ubuntu; new-tab; split-pane" }, "keys": ... }

We've added a new action, sendInput, that can emit text directly into the terminal (thanks @lhecker!) (#7249)

Example: you can bind a so that it sends the VT sequence for "up arrow"

{ "command": { "action": "sendInput", "input": "\u001B[A" }, "keys": "a" }

You can now zoom one pane to temporarily take up the entire terminal with the togglePaneZoom action! (#6989) (#7273)

You can now override the active color of the terminal using the setColorScheme action (#6993)

A profile can now specify its default tabColor (profile setting, hex color, default unset) (#7162)

Two actions have been added, closeOtherTabs and closeTabsAfter, to facilitate better tab management (#7176)

The copyFormatting option and the copy.copyFormatting action argument have been taught finer-grained control
over the copied formats (#6004)

You can now specify an array of formats, [ "rtf", "html" ], a string "html", "all", or a boolean to indicate
which formats to copy. true maps to all and false maps to none.

Changes

Windows Terminal 1.3 ships with Cascadia Code v2008.25

The bindings keyword in settings has been replaced with actions in preparation for improvements to the action
binding experience (#7332)

All processes spawned under Terminal will be given a fresh new environment block (#7243)

⚠ WARNING This may break some workflows, as environment variables from without Terminal will no longer be
inherited. If you have a broken workflow, please reach out.

Terminal is now a little more strict about parsing your settings (#6590), but it will now actually tell you why
something couldn't be understood (#7241)

Key bindings can now use the app or menu key (thanks @MichelleTanPY!) (#7328)

UI

Clicking in the scrollbar track will now jump up/down by a whole screenful (#7385)

The color picker is now more visually consistent, having learned to round its buttons (thanks @MichelleTanPY!) (#7305)

Terminal Basics

We now have very basic support for DCS sequences (thanks @skyline75489!) (#6328)

Even if we can't support sixels, the least we could do is not dump their raw data to the screen!

If you really wanted their raw data dumped to the screen, why??

Underlines are now rendered consistent with the font's metrics (thanks @j4james!) (#7148)

We now have support for SGR 21, doubly-underlined (thanks @j4james!) (#7223)

We now have support for SGR 9, crossed out (thanks @j4james!) (#7143)

Our underline/strikethrough renderer has been refactored to be easier to work with (thanks @j4james!) (#7107)

Our VT parser has been refactored to be easier to work with (thanks @j4james!) (#7304)

Scroll locking should now work more reliably when the scrollback is at maximum length (#7247)

Bug Fixes

The command palette now has a gutter so that it stops overlapping the scrollbar (thanks @jtippet!) (#6965)

F7 will no longer not work after our "null scancode" change (whoops!) (#7298)

altGrAliasing: false will no longer actually break AltGr (thanks @lhecker!) (#7400)

Profiles whose indices are greater than 9 will now properly display their shortcuts in the menu (thanks
@MichelleTanPY!) (#7344)

Performance

Miscellaneous performance improvements for handling incoming data:

"Set memory order on slow atomics" (#6920)

"Commit attr runs less frequently by accumulating length of color run" (#6919)

"Skip DX invalidation if we've already scrolled an entire screen worth of height" (#6922)

Click to expand...

Source:

https://github.com/microsoft/termina...ag/v1.3.2382.0

https://devblogs.microsoft.com/comma...w-1-3-release/

See also: New Windows Terminal v1.2.2381.0 released for Windows 10 - Aug. 26

Tweet

— Twitter API (@user) View on Twitter
Click to expand...

Brink · Dec 5, 2020

New Experimental Console Features in Windows 10 build 18298

As of Windows 10 build 18298, when you open the properties page of any Console window, you’ll notice an additional “Terminal” tab. Click on this tab and you’ll see several new settings for some experimental features we’re working on for future OS releases:

Experimental settings in action
Important Note: These settings are "experimental", because in certain scenarios, it's possible that they might not behave like you would expect them to, may not make it into the next OS release, and may change completely before we ship! But have fun with them anyway and let us know how you get on – we’d love to hear your feedback.
Let’s outline each of the settings groups from the bottom up, ending with a more thorough discussion the Terminal Color settings:

Terminal Scrolling

Disable Scroll Forward:

When cleared (default state), the Console can to scroll anywhere within the Console’s buffer, even below the most recent row of text displayed
When checked, the Console will not allow scrolling below the last line output, similar to how most *NIX terminals work

Cursor Shape

Legacy Style: Thicker underscore by default, but controlled by the cursor size property in the "Options" page

Underscore: Thinner underscore

Vertical Bar: For all you crazy kids who like your cursors tall and skinny

Empty Box: The second-best cursor:

Solid Box: The one true cursor

Cursor Colors

Inverse Color: The current and default behavior where the cursor color is the calculated inverse of the background color … which results in, for example, this adorable fetching pink against the bright green background of my first computer – the Dragon 32

Use Color: Draw the cursor in a specific RGB color, like this fetching green against dark gray background:

Terminal Colors

The Terminal Colors fields allow you to specify specific RGB color values for the default foreground and/or background colors. These colors are independent of the color palette and are not affected by changes you make to your color palette! But before we discuss the inherent implications here, we need to consider how these new settings fit into the color changes we’ve been making over the last several Windows 10 releases:

Karma Karma Karma Karma Console Chameleon

Over the last couple of years, during “The Grand Overhaul” of Windows Console, we’ve made some significant improvements to Console’s parsing and handling of ANSI/VT sequences, and how the Console stores and renders colored text.

This all started with a rewrite of the Console’s VT parser. Prior to the (then new) team’s efforts, Windows Console barely supported any VT sequences at all. But with the steady growth in adoption of *NIX-first open-source tools, many of which emit VT sequences to color and draw text-based UI’s, it was increasingly imperative that the Windows Console be able to support VT sequences.

Before (XP) and after (Win10) VT support added to Console

This was made even more important and urgent due to the arrival of Windows Subsystem for Linux which allowed unmodified Linux binaries to run natively on Windows, allowing Windows users to easily run most of the *NIX tools they’d previously had to fire-up in a separate VM.

The first significant version of the Console’s new VT engine shipped in Windows 10 1609 (Anniversary Update), and was quickly followed in the 1703 (Creators Update) release which contained much richer support for a wider range of VT sequences. This allowed Console to render many of even the most complex text-based UI’s generated by tools like Tmux (a great tutorial here for the uninitiated) and Midnight Commander … or even vim, bash, Midnight Commander and htop running simultaneously in separate Tmux panes:

TMux hosting vim, bash, Midnight Commander, and htop

Also in Creators Update, the Console shipped its massively improved color support, increasing its color support from a mere 8-bit/16-colors (a single 8-bit value held both the foreground and background color 0-7 in the low and high nybble respectively), to full 24-bit/16M-colors!

But we weren’t yet done! In the Fall Creators Update (Oct 2017), we updated the Console’s default color palette for the first time … ever! After working with Microsoft’s usability and accessibility teams, and following recommended color selection guidelines, we arrived at a new color palette that is FAR better suited to modern high-contrast displays.

In addition, we also shipped an open-source ColorTool which you can use to apply different color palette’s to your Console windows if you wish.

So, we’re done with color support in the Console, right?

Nope!

Looking Back, Moving Forward

The Console now lives in two worlds:

1. Windows – Console supports traditional/legacy command-line Windows apps that call the Win32 Console APIs to color/manipulate text displayed on the Console

ANSI/VT – Console also now supports apps that color/manipulate the text that they display by embedding VT sequences within the text that they emit

Because of #2 above, Console has to support some of the different ways in which VT compatible terminals think about the world.

A key difference between Windows Console and *NIX-based VT Terminals is that *NIX Terminals have a notion of default foreground and background colors, which are independent from the Terminal’s color palette. The Windows Console does not … at least not quite the same!

Windows Console refers the “Screen Text” and “Screen Background” colors to the colors defined in the Console’s palette:

Console color settings

But Console has no notion of “default” foreground or background color to the command-line apps that draw on the screen. At best, there’s an assumption that color #0 is often the background color, and that #7 is the foreground, but this is an often-incorrect assumption, not a widely-understood rule. In fact, Windows command-line apps have no way of determining the default foreground and background colors!!

For a good example of this, let’s explore Windows PowerShell: The Windows PowerShell team wanted to differentiate PowerShell Consoles from Cmd Consoles by changing the PowerShell Console’s default background color.

They specifically modified the PowerShell shortcuts’ settings:

Re-defined color #5 as a specific shade of blue: RGB(1,36,86)

Re-defined color #6 as a specific shade of gray: RGB(238,237,240)

However, they also decided to modify the shortcut’s background and foreground color indexes to

Color #5 as the background color (instead of the generally assumed color #0)

Color #6 as the foreground color (instead of the generally assumed color #7)

Sometimes, PowerShell wants to, for example, “render this text in <color> on whatever the default background color is”.

Alas, because Windows Console has no API to discover what the “default background color” is, PowerShell assumes that the background is the color defined by color #0 … which usually IS the background color … except in PowerShell which uses color #5

Thus, if you’ve ever mis-typed a command in Windows PowerShell, you’ve likely seen something like this:

PowerShell assumes the background color is #0

Moving Forward

Alas, the changes we’re working on (and exposing via the experimental Terminal settings page) won’t fix this specific issue for Windows PowerShell ☹

Existing/legacy applications that specifically say “draw this text in <some-foreground-color> on color #0” will still draw text in some-foreground-color, on a (usually black/dark) background, even if the Console’s default background color is bright green! In some ways this is good;there will be no behavioral change for existing/legacy apps. But the downside is that such apps will continue to render less than optimal output (like in the PowerShell example above.

However, making Console aware of the notion of “default independent foreground and background colors” will enable Console to more accurately render VT enriched text-UI, and will give Console users more control over the customizability of their Command-Line environment.

Call To Action!

This issue further amplifies the recommendation to start writing (or update existing) Command-Line apps to emit VT enriched text, rather than calling Win32 Console APIs to control/format Console output: VT-enabled apps will not only benefit from rendering improvements like those described above (with more on the way), but they’ll also enjoy richer features available via VT-sequences, like 24-bit color support, and default foreground/background color support.

We look forward to hearing how you get-on with these experimental changes. If you find issues with the color support, please find/file issues on our GitHub issues repo, reach out and let @richturn_ms know on Twitter, and/or submit feedback via the Feedback Hub.
Click to expand...

Source: New Experimental Console Features Windows Command Line Tools For Developers

Windows 10: How to set New Windows Terminal as default console.

How to set New Windows Terminal as default console.

How to set New Windows Terminal as default console.

How to set New Windows Terminal as default console.

How to set New Windows Terminal as default console. - Similar Threads - set Terminal default

With Default Terminal set to Windows Terminal - Use start-process to launch PWSH in the...

With Default Terminal set to Windows Terminal - Use start-process to launch PWSH in the...

Windows 11 not detecting Windows Terminal as default terminal application

Windows 11 not detecting Windows Terminal as default terminal application

How to set Windows Terminal as the default terminal application in Windows 11

Can't set Windows Terminal as default because it is not detected in the list of terminals.

Can't set Windows Terminal as default because it is not detected in the list of terminals.

How to Change Default JSON Editor in Windows Terminal Settings?

Change Terminal Colors of Console Window in Windows 10