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

When PS is installed on a system with Windows Terminal, please default to that console. #9220

Closed
sharpninja opened this issue Feb 19, 2021 · 3 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@sharpninja
Copy link

Description of the new feature/enhancement

From this discussion in PowerShell.

Please allow setting WindowsTerminal to the default conhost.

Proposed technical implementation details (optional)

Add setting to specify default conhost is WindowsTerminal.

@sharpninja sharpninja added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Feb 19, 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 Feb 19, 2021
@skyline75489
Copy link
Collaborator

See #492 #7414

@zadjii-msft
Copy link
Member

Yep, this is the whole point of #492.

/dup #492

@ghost
Copy link

ghost commented Feb 19, 2021

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed Feb 19, 2021
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed 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 Feb 19, 2021
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

3 participants