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

Feature Request - Hide borders #2939

Closed
fpqc opened this issue Sep 27, 2019 · 3 comments
Closed

Feature Request - Hide borders #2939

fpqc opened this issue Sep 27, 2019 · 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

@fpqc
Copy link

fpqc commented Sep 27, 2019 •
edited
Loading

Okay, first, I want to say, I'm not sure if this is equivalent to

#872

But it would be nice to be able to completely hide the window border that looks like

image

What wasn't mentioned in the other topic was that even if we turn off ShowTabsInTitlebar, we still have a small border (which I'm still not a fan of):

image

The issue I cited was closed without a clear (to me) resolution, and it's not clear if this feature might be implemented in a future version of Windows or if it's been completely abandoned, so if this is a duplicate, before closing it, could one of the devs clarify the situation?

What would be nice is maybe a hotkey to just hide the entire non-client area. Support for this would also move toward quake-terminal support (which I guess isn't planned for 1.0).
@fpqc fpqc added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Sep 27, 2019
@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 Sep 27, 2019
@DHowett-MSFT
Copy link
Contributor

This is a dupe of (i-want-my-terminal-to-be-a-floating-box-i-cannot-interact-with), I just don't know the number right now.

@DHowett-MSFT
Copy link
Contributor

/dup #2238

Thanks @zadjii-msft

@ghost
Copy link

ghost commented Sep 30, 2019

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 Sep 30, 2019
@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 Sep 30, 2019
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
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
Milestone
No milestone
Development

No branches or pull requests
2 participants
@fpqc @DHowett-MSFT