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

DuplicateTab shortcut redo same splitedPane layout from previous tab. #4284

Closed
ucavalcante opened this issue Jan 17, 2020 · 2 comments
Closed

DuplicateTab shortcut redo same splitedPane layout from previous tab. #4284

ucavalcante opened this issue Jan 17, 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

@ucavalcante
Copy link

ucavalcante commented Jan 17, 2020 •
edited
Loading

When we using duplicate tab shortcut (default "ctrl+shift+d") if current Tab has splited panes replicate the same splited panes layout from current Tab in the next Tab.
image
@ucavalcante ucavalcante added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Jan 17, 2020
@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 Jan 17, 2020
@zadjii-msft
Copy link
Member

Thanks for the suggestion! This is actually a /dup of #1756.

@ghost
Copy link

ghost commented Jan 19, 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 Jan 19, 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 Jan 19, 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
@ucavalcante @zadjii-msft