Skip to content

Preserve Last Known Window Position When Showing/Hiding Terminal #18876

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

Open
arhe1on opened this issue May 5, 2025 · 2 comments
Open

Preserve Last Known Window Position When Showing/Hiding Terminal #18876

arhe1on opened this issue May 5, 2025 · 2 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Needs-Attention The core contributors need to come back around and look at this ASAP. Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting

Comments

@arhe1on
Copy link

arhe1on commented May 5, 2025

Description of the new feature

I would like to suggest adding the ability to preserve the window position of the terminal before it is closed or hidden, so that when reopened using hotkeys, it appears in exactly the same screen location where it was previously opened. Currently, upon re-opening with a hotkey, the terminal window automatically displays on the monitor which currently has input focus, making it inconvenient while working with applications that heavily rely on console output for debugging or monitoring processes.

An ideal solution would be an option allowing users to choose whether the terminal should remain at its original position or switch between monitors based on current input focus.

Proposed technical implementation details

No response

@arhe1on arhe1on added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label May 5, 2025
@microsoft-github-policy-service microsoft-github-policy-service bot 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 May 5, 2025
@DHowett
Copy link
Member

DHowett commented May 7, 2025

Oh hey! If you're using the globalSummon action, you can configure whence the window is summoned using a couple of the additional knobs we expose. Does that help/?

One of the examples in there is...

// Summon the MRU window to the current desktop, leaving the position of the window untouched.
{ "command": { "action": "globalSummon", "monitor": "any" }, "id": "User.MyGlobalSummonAnyMonitor" },

@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something label May 7, 2025
@arhe1on
Copy link
Author

arhe1on commented May 9, 2025

Yes, it helped.Thank you very much!

@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Attention The core contributors need to come back around and look at this ASAP. and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels May 9, 2025
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. Needs-Attention The core contributors need to come back around and look at this ASAP. Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting
Projects
None yet
Development

No branches or pull requests

2 participants