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

wt opens a new windows with the default profile instead of the current profile #4793

Closed
ranyitz opened this issue Mar 3, 2020 · 2 comments
Closed
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@ranyitz
Copy link

ranyitz commented Mar 3, 2020

Environment

Windows build number: Microsoft Windows [Version 10.0.18362.657]
Windows Terminal version (if applicable): Version: 0.9.433.0

Steps to reproduce

Choose a profile which is not the default profile
Run wt

Expected behavior

Open a new window with the same profile as the currently used profile

Actual behavior

Open a new window with the default profile

Context

It makes sense to have the best defaults as possible. If I ran a command from a certain profile (for example PowerShell) I would like to continue and use the same profile.

@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 Mar 3, 2020
@DHowett-MSFT
Copy link
Contributor

This is just a different variation of /dup #445 for new window instead of new tab. Also, right now, there's no communication between wt instances.

@ghost
Copy link

ghost commented Mar 3, 2020

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 Mar 3, 2020
@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 Mar 3, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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

2 participants