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: Active Pane Maxmise / Minimise hotkey #6944

Closed
lgisler opened this issue Jul 16, 2020 · 2 comments
Closed

Feature Request: Active Pane Maxmise / Minimise hotkey #6944

lgisler opened this issue Jul 16, 2020 · 2 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

@lgisler
Copy link

lgisler commented Jul 16, 2020

Description of the new feature/enhancement

I have looked in the Issues, and in the default.json settings file under //Pane Management and have been unable to find this feature.

I have just recently moved from developing in Linux to Windows. I have really enjoyed the Linux application Byobu to manage my terminal experience. One feature that I used extensively was "zoom into a split, zoom out of a split". In Microsoft Terminal language that might be "zoom into a pane, zoom out of a pane".

I would be happy to implement this feature if it is deemed useful, but I have not contributed to this project before so some guidance to point me in the right direction would be greatly appreciated.

Proposed technical implementation details (optional)
@lgisler lgisler added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Jul 16, 2020
@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 Jul 16, 2020
@zadjii-msft
Copy link
Member

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

/dup #996

@ghost
Copy link

ghost commented Jul 16, 2020

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 Jul 16, 2020
@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 Jul 16, 2020
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
@zadjii-msft @lgisler