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

Always-on-top quake mode window #10372

Closed
cerebrate opened this issue Jun 8, 2021 · 3 comments
Closed

Always-on-top quake mode window #10372

cerebrate opened this issue Jun 8, 2021 · 3 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@cerebrate
Copy link

Description of the new feature/enhancement

The way I use the _quake window (for a one-off command or series of commands), it usually has my attention for as long as it's up, but on the occasions where I turn away to do other things, it can easily get lost in the mess and/or confused with one of my regular terminal windows. Having it always-on-top such that it is either dropped-down on-top or not makes this less likely to happen in my workflow.

Proposed technical implementation details (optional)

While just making the _quake window always-on-top by default would fit the letter of the request, I'd much rather have always-on-topness added as a parameter that can be used with quakeMode and globalSummon to influence the parameters of windows they create. It would also be useful to have it as a command-line option for use with -w -- I currently use a _C:\Users\avatar\AppData\Local\Microsoft\WindowsApps\wt.exe -w _quake to automatically open the _quake window when I log on, and while I can toggle on always-on-topness after opening it, I would prefer to be able to have that in the shortcut.

@cerebrate cerebrate added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Jun 8, 2021
@ghost ghost added 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 labels Jun 8, 2021
@WSLUser
Copy link
Contributor

WSLUser commented Jun 9, 2021

If you have the "AlwaysOnTop" enabled in your settings.json, does launching via quake mode ignore this? Regardless, because you have multiple windows you have open but want the quake mode window to be "Always on Top", I'd call it dupe #9992

@zadjii-msft
Copy link
Member

Yea, this is gonna fall under /dup #9992

@ghost
Copy link

ghost commented Jun 9, 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 Jun 9, 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 Jun 9, 2021
This issue was closed.
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. 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