Please add support closePaneRight/Left/Up/Down #6904

Closed
opened 2026-01-31 00:50:04 +00:00 by claunia · 5 comments
Owner

Originally created by @kgfly on GitHub (Mar 16, 2020).

Description of the new feature/enhancement

I want to look for a way to close eg right pane and bind it to a hot key.
Currently, to close eg right pane, I need move focus to right pane first. Then close it.

Proposed technical implementation details (optional)

Please add support closePaneRight/Left/Up/Down.
Then people can bind it to a hot key

Thanks.

Originally created by @kgfly on GitHub (Mar 16, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> # Description of the new feature/enhancement I want to look for a way to close eg right pane and bind it to a hot key. Currently, to close eg right pane, I need move focus to right pane first. Then close it. <!-- A clear and concise description of what the problem is that the new feature would solve. Describe why and how a user would use this new functionality (if applicable). --> # Proposed technical implementation details (optional) Please add support closePaneRight/Left/Up/Down. Then people can bind it to a hot key Thanks. <!-- A clear and concise description of what you want to happen. -->
Author
Owner

@zadjii-msft commented on GitHub (Mar 16, 2020):

Okay I like the idea, but what happens when someone's got something like the following:

[ A | B | C ]

What happens when they closeRight from pane A? Or the even more complicated [ A | B | C | D ]? What happens when the nesting gets ridiculous like
image

@zadjii-msft commented on GitHub (Mar 16, 2020): Okay I like the idea, but what happens when someone's got something like the following: ``` [ A | B | C ] ``` What happens when they `closeRight` from pane A? Or the even more complicated `[ A | B | C | D ]`? What happens when the nesting gets ridiculous like ![image](https://user-images.githubusercontent.com/18356694/76797567-d509c300-679b-11ea-91e2-abe49b577995.png)
Author
Owner

@kgfly commented on GitHub (Mar 16, 2020):

In this case, [ A | B | C ]. What happens when they closeRight from pane A?
I suggest close B only.

I found, multi command binding, eg
{ "command": "moveFocusRight","command": "closePane", "keys": ["alt+l"] }
does not work.

That's why I propose.

Other software, such vim, supports above multi command binding easily.

Thanks.

@kgfly commented on GitHub (Mar 16, 2020): In this case, [ A | B | C ]. What happens when they closeRight from pane A? I suggest close B only. I found, multi command binding, eg { "command": "moveFocusRight","command": "closePane", "keys": ["alt+l"] } does not work. That's why I propose. Other software, such vim, supports above multi command binding easily. Thanks.
Author
Owner

@kgfly commented on GitHub (Mar 16, 2020):

If "multi command binding" is supported, that would be even better.

@kgfly commented on GitHub (Mar 16, 2020): If "multi command binding" is supported, that would be even better.
Author
Owner

@zadjii-msft commented on GitHub (Mar 16, 2020):

Ah okay. What you really want is tracked over here, in #3992. Thanks for helping clarify!

/dup #3992

@zadjii-msft commented on GitHub (Mar 16, 2020): Ah okay. What you _really_ want is tracked over here, in #3992. Thanks for helping clarify! /dup #3992
Author
Owner

@ghost commented on GitHub (Mar 16, 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 commented on GitHub (Mar 16, 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!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#6904