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

Pane operation demands #8164

Closed
8solo opened this issue Nov 5, 2020 · 2 comments
Closed

Pane operation demands #8164

8solo opened this issue Nov 5, 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

@8solo
Copy link

8solo commented Nov 5, 2020

Pane Split & Switch Mode

  1. Add pane split mode that made panes equal-width and equal-hight like iterm2
  2. Add key binding in switch pane that support switch pane with specific number, alt + direction is not such convinient

Proposed technical implementation details (optional)

  1. Split all pane in equal
  2. Switch pane using number key binding like ctrl + 1
@8solo 8solo added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Nov 5, 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 Nov 5, 2020
@zadjii-msft
Copy link
Member

Thanks for the suggestion! Please make sure to search for duplicates when filing new issues. These requests are already being tracked by another issue on our repo - please refer to #1000 for more discussion.

More specifically, see:

  1. Split panes equally in size #6002
  2. moveFocus to panel using number #5803

/dup #6002
/dup #5803

P.S. The word "demands" is a bit strong of a word to use when asking for new features - the word "request" might be more what you're looking for ☺️

@ghost
Copy link

ghost commented Nov 5, 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 Nov 5, 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 Nov 5, 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 @8solo