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.

Sign up for GitHub

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

Jump to bottom

Does not restart on correct monitor #12647

Closed
SteveALee opened this issue Mar 9, 2022 · 3 comments
Closed

Does not restart on correct monitor #12647

SteveALee opened this issue Mar 9, 2022 · 3 comments
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@SteveALee
Copy link

Windows Terminal version

1.11.3471.0

Windows build number

21H2 (there is no ver in WSL or cmd)

Other Software

Windows 11 - running terminal from a task bar icon but windows 11 seems to have removed ability to see what the properties are (yet another win 11 fail)

Steps to reproduce

  1. have multiple monitors attached to PC.
  2. open Terminal.
  3. move to another monitor rather than default
  4. close terminal
  5. open again

Expected Behavior

Opens on same monitor it was last on

Actual Behavior

Opens on default monitor
@SteveALee SteveALee added the Issue-Bug It either shouldn't be doing this or needs an investigation. label Mar 9, 2022
@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 9, 2022
@SteveALee SteveALee changed the title Does not restart on corrent monitor Does not restart on correct monitor Mar 9, 2022
@zadjii-msft
Copy link
Member

On Terminal Preview, there's a setting to enable restoring your open windows (including tabs and position) when you relaunch the Terminal: Behavior when starting a new terminal session

If you just want the ability to restore the window position, we're tracking that in /dup #12633

@ghost
Copy link

ghost commented Mar 9, 2022

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 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 9, 2022
@SteveALee
Copy link
Author

OK, sorry, I did search but a lot of irrelevant bugs.

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@SteveALee @zadjii-msft