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

Quake mode from the launch #12928

Closed
NSurtsev opened this issue Apr 18, 2022 · 6 comments
Closed

Quake mode from the launch #12928

NSurtsev opened this issue Apr 18, 2022 · 6 comments
Labels
Area-Windowing Window frame, quake mode, tearout Issue-Question For questions or discussion Resolution-Answered Related to questions that have been answered Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@NSurtsev
Copy link

NSurtsev commented Apr 18, 2022

Windows Terminal version

1.12.10732.0

Windows build number

19044.1645

Other Software

No response

Steps to reproduce

Launch Terminal

Expected Behavior

When we have "Quake mode" ability, I expect to have option to have Quake window when I launch Terminal or at least autoreplace the default window If I use Win+~

Actual Behavior

I launch Terminal, get default Terminal window and I have to press Win+` to get Quake ( window #2), then to system tray and close default Terminal window #1.
And only then it becomes as it should be (but still, name #2 remains for Quake for whatever reason).

@NSurtsev NSurtsev added the Issue-Bug It either shouldn't be doing this or needs an investigation. label Apr 18, 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 Apr 18, 2022
@zadjii-msft
Copy link
Member

This sounds like you're looking for #9996.

You can immediately launch the quake window with wt -w _quake. Or, you should be able to convert an existing window to be the quake window by renaming the window to _quake (with the "Rename window" action in the Command Palette). That of course assumes there isn't an already running quake window, of course.

Does that make sense?

@zadjii-msft zadjii-msft added Issue-Question For questions or discussion Resolution-Answered Related to questions that have been answered Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something Area-Windowing Window frame, quake mode, tearout and removed Issue-Bug It either shouldn't be doing this or needs an investigation. labels Apr 18, 2022
@NSurtsev
Copy link
Author

This sounds like you're looking for #9996.

You can immediately launch the quake window with wt -w _quake. Or, you should be able to convert an existing window to be the quake window by renaming the window to _quake (with the "Rename window" action in the Command Palette). That of course assumes there isn't an already running quake window, of course.

Does that make sense?

Ok, these options are interesting, but that doesn't actually solve the main issue.
Why should I right commands or doing renames when I should launch Terminal and Quake window should meet me immediately?
(Btw, there should be option in settings to make Quake mode default for launching)
And even if I do not check this potential future option and there is default window opened, I should just press Win+` and this window should become Quake, because I checked "make new instance add to existing window" option in settings (if you do not check it, then it should create separate Quake window like it already does now)

@ghost ghost 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 Apr 18, 2022
@markusdd
Copy link

I wish to second that.

We simply need an option to launch in quake mode as default (as there are options for maximized etc.).

Also, quake mode should NOT launch in Focus mode by default, that does not make sense. (at least it should be configurable).

Currently I always need 4 steps to get my windows terminal:

  • launch it from taskbar
  • then launch quake mode
  • close the other window
  • take quake window out of focus mode

This is annoying xD

@zadjii-msft
Copy link
Member

Okay yea, between the two of you, it sounds like you're looking for

/dup #9996
/dup #9992

FYI you don't need to use the quakeMode action to summon the window - you could always just rebind win+` to a plain old globalSummon action. Then you'd summon whatever terminal window you were already using, without the focus mode baggage attached. You can even use globalSummon with a dropdownDuration if that's really important (though, you can't currently dock the window to the top of the monitor outside the _quake window).

@ghost
Copy link

ghost commented Apr 20, 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 Needs-Attention The core contributors need to come back around and look at this ASAP. labels Apr 20, 2022
@markusdd
Copy link

markusdd commented Apr 20, 2022

Sorry, I do not seem to understand this. I have now put this globalSummon stuff in my JSON settings, still I have to perform the same steps to get my quake window, also the focus mode is still on on first launch.

I just want this terminal to launch in quake mode without focus mode, why is that so difficult? xD

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Windowing Window frame, quake mode, tearout Issue-Question For questions or discussion Resolution-Answered Related to questions that have been answered 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