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

Opening 'Quake mode' does not work until another instance of Windows Terminal is running #10920

Closed
NinovanderMark opened this issue Aug 11, 2021 · 2 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@NinovanderMark
Copy link

NinovanderMark commented Aug 11, 2021

Windows Terminal version (or Windows build number)

1.9.1942.0

Other Software

Powershell 7.1.3

Steps to reproduce

Pressing win + tilde after a clean reboot.

Entering 'exit' in the existing Windows Terminal that has been triggered by win + tilde then attempting to reopen it by using win + tilde

This is my settings.json:
settings.zip

Expected Behavior

I expected the Windows Terminal to be opened, regardless if another instance was running, or I had opened it prior.

Actual Behavior

Windows Terminal is not dropped down from the top, nothing else appears to happen.

@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 Aug 11, 2021
@zadjii-msft
Copy link
Member

Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #9996 for more discussion.

/dup #9996

@ghost
Copy link

ghost commented Aug 11, 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 Aug 11, 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 Aug 11, 2021
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