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

Bug Report: splitVertical should duplicate opened shell instead of defaul #2442

Closed
guibirow opened this issue Aug 15, 2019 · 1 comment
Closed
Labels
Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@guibirow
Copy link

This is related to the #1000 - Deliverable: Add support for panes

Currently, when a new pane is opened by splitting the window, the default shell is opened instead of an instance of same shell already open in the side pane.

I would expect the window to be split using the same shell, maybe have a separate command to split using the default shell.

Environment

Windows build number: Microsoft Windows [Version 10.0.18362.239]
Windows Terminal version (if applicable): 0.3.2171.0

Any other software?
WSL 1 (Ubuntu) (Default shell in Win Terminal)

Steps to reproduce

Open a non default shell (In my case CMD, because WSL is the default)
Press the shortcut for command splitVertical (ctrl+shift+\)
The pane will split and

Expected behavior

Open a new pane of same shell

Actual behavior

The default shell is opened in the new pane

@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 Aug 15, 2019
@zadjii-msft
Copy link
Member

Literally in #1000:

#1756 The user should be able to configure what profile is used for splitting a pane. Currently, the default profile is used, but it's possible a user might want to create a new pane with the parent pane's profile.

@zadjii-msft zadjii-msft added the Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. label Aug 15, 2019
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Aug 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting 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