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

Adjustable split area sizes #13993

Closed
Richard7129 opened this issue Sep 14, 2022 · 3 comments
Closed

Adjustable split area sizes #13993

Richard7129 opened this issue Sep 14, 2022 · 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

@Richard7129
Copy link

Description of the new feature/enhancement

As a user that creates mutiple splits on a tab I want to be able to adjust the split size so that I can have the optimum amount of screen area for the tasks that I am performing in each split area.

Proposed technical implementation details (optional)

  • After selecting "split tab", I would like to be able to adjust the size of the area
  • I would like to be able to resize those areas by using either the mouse or keyboard shortcut(s).
  • For vertical splits, I want to be able to move the plit bar to the left or right
  • For horizontal splits, I want to be able to move the split bar up or down
@Richard7129 Richard7129 added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Sep 14, 2022
@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 Sep 14, 2022
@Richard7129
Copy link
Author

Sorry, I've just found that it already can do this, and I didn't know.

@zadjii-msft
Copy link
Member

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

/dup #992

See also:

{ "command": { "action": "resizePane", "direction": "down" }, "keys": "alt+shift+down" },
{ "command": { "action": "resizePane", "direction": "left" }, "keys": "alt+shift+left" },
{ "command": { "action": "resizePane", "direction": "right" }, "keys": "alt+shift+right" },
{ "command": { "action": "resizePane", "direction": "up" }, "keys": "alt+shift+up" },

@ghost
Copy link

ghost commented Sep 14, 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 labels Sep 14, 2022
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

2 participants