Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The "Default Terminal" option is only available for Preview builds of the Terminal #11415

Closed
3 tasks
zadjii-msft opened this issue Oct 4, 2021 · 4 comments
Closed
3 tasks
Labels
Area-DefApp Needs-Tag-Fix Doesn't match tag requirements Product-Terminal The new Windows Terminal. Resolution-Answered Related to questions that have been answered
Milestone

Comments

@zadjii-msft
Copy link
Member

zadjii-msft commented Oct 4, 2021

Windows 11 is shipping a new OS feature we're calling "defterm" - the ability to set the default terminal application for console launches in Windows. This was originally tracked in #492, #5000. This feature initially shipped in Terminal Preview version https://github.com/microsoft/terminal/releases/tag/v1.9.1445.0.

As of writing, this feature is still only available with "Preview" versions of the Terminal. There are two different versions of the Terminal available:

Stable is usually one minor version behind the Preview version, +/- a couple features. If you're wondering why the Terminal doesn't appear in the dropdown, then this is why.

If you only have "Windows Terminal" (stable) installed, you will not see the Terminal in the Settings app for the Default Terminal setting.

There's a bit of work we want to get done in the 1.12 timeframe to move the defterm feature into the Stable branch:

Once that's fixed up, we'll be enabling the Default Terminal feature for Stable builds as well.

(Preview is also reasonably reliable if you're really enthusiastic about defterm, it is just a tad bit more "move fast and break things".)

@zadjii-msft zadjii-msft added Resolution-Answered Related to questions that have been answered Product-Terminal The new Windows Terminal. Area-DefApp labels Oct 4, 2021
@zadjii-msft zadjii-msft added this to the Terminal v2.0 milestone Oct 4, 2021
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Oct 4, 2021
@zadjii-msft zadjii-msft pinned this issue Oct 4, 2021
@DHowett DHowett removed the Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting label Oct 15, 2021
@jtnord
Copy link

jtnord commented Oct 18, 2021

As of writing, this feature is still only available with "Preview" versions of the Terminal.

yet the release notes for 1.10 specifically call out fixes for the "Default terminal" which may be causing some confusion as to why this is being reported?

@zadjii-msft
Copy link
Member Author

Thanks for pointing that out, I've added a note that might help clarify. I'm suspecting the real reason is the release of Windows 11 last week and a flux of new users to the Stable version, which doesn't yet support that feature.

@CDAGaming
Copy link

Just tested the new 1.11 stable release, Default Terminal so far working like a charm on 22000.282 Windows11

Thanks for the amazing service!

@zadjii-msft
Copy link
Member Author

I'm closing this, because with the release of 1.11 Stable, we added support for defterm. Thanks for the patience everyone!

@zadjii-msft zadjii-msft unpinned this issue Nov 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-DefApp Needs-Tag-Fix Doesn't match tag requirements Product-Terminal The new Windows Terminal. Resolution-Answered Related to questions that have been answered
Projects
None yet
Development

No branches or pull requests

4 participants