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

Split screen fails to resize #4597

Closed
TotallyInformation opened this issue Feb 15, 2020 · 2 comments
Closed

Split screen fails to resize #4597

TotallyInformation opened this issue Feb 15, 2020 · 2 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@TotallyInformation
Copy link

Environment

Platform ServicePack Version VersionString
Win32NT 10.0.18363.0 Microsoft Windows NT 10.0.18363.0

Microsoft Surface Book 2, i7, 16GB RAM.

Steps to reproduce

Open cmd.exe, issue wt -p "WSL (Home1 Remote)" ; split-pane -p "WSL (Home1 Remote)"

Where "WSL (Home1 Remote)" is a profile that opens WSL and issues an SSH connection to a remote Debian Buster server.

Or, open any other profile or simply wt ; split-pane which opens two PowerShell v6 panes.

It is not possible to drag the split left or right (nor up/down if starting 3 or more panes).

Expected behavior

Be able to resize the internal boundaries of the panes.

Actual behavior

The panes cannot be resized.

This generally makes the panes of little to no use since it is often the case that at least one of the panes is too narrow to be useful.

@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 Feb 15, 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 #992 for more discussion.

/dup #992

Right now, panes can't be resized with the mouse, however, you can resize them with keybindings. See #1207, and the default keybindings:

{ "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 Feb 18, 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 Feb 18, 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 Feb 18, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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