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

Command line focus-pane to split #5811

Closed
chechorincon opened this issue May 8, 2020 · 2 comments
Closed

Command line focus-pane to split #5811

chechorincon opened this issue May 8, 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

@chechorincon
Copy link

chechorincon commented May 8, 2020

It would be great to have a focus-pane option from the command line, so you can start wt with some layouts that currently are almost impossible (2x2 splitted, 3x3, and so on) and be able to pass parameters to a specific pane (not tab)

Right now, (as far as I´ve found and searched) there is a way to start wt from the command line and split the pane (H or V), but when you append a new split-pane, it splits the last (Current) pane. So if you want to split, from the command line, the tab to have a layout of 2x2 panes or 3x3 panes, its not possible. With a focus-pane option, each pane should have an ID, so at the command line you can tell to what paneID you want to split.

Proposed technical implementation details (optional)

@chechorincon chechorincon added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label May 8, 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 May 8, 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 #5464 for more discussion.

/dup #5464

@ghost
Copy link

ghost commented May 8, 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 May 8, 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 May 8, 2020
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

2 participants