Option+left/right arrow bound to switch pane left/right does nothing

Open
#2,163 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
rust
Domain
desktop

Research direction

Start in the preferences window's Shortcuts search for “switch pane” and reproduce the Option+Left/Right mappings on macOS. Trace the switch-pane shortcut handling from those bindings and compare it with Option+Home/End or Option+Up/Down. Done means the mapped left/right shortcuts navigate between split panes while the existing working mappings remain functional.

Written by the indexing model from the issue text.

Description

area:window-tabs-panes bug needs-info ready-to-implement triaged
Discord username (optional)

No response

Describe the bug

If I map:

  • Option + Left Arrow to switch pane left
  • Option + Right Arrow to switch pane tight

Hitting those shortcuts does work are promised: nothing happens.

Note that resetting to default or choosing other keys (eg. Option+Home & Option+End) works. Also mapping Option+up/down works too.

To Reproduce

Option the preferences window
Go to shortcuts
Search "switch pane"
Map Switch pane right to Option+Right Arrow
Map Switch pane left to Option+Left Arrow
Close the preferences
create a new pane (Split pane right)
Try to navigate between the two panes with Option+Left/Right

Expected behaviour

You can navigate between the two panes with Option+Left/Right

Screenshots

No response

Operating System

MacOS

OS Version

12.6

Shell Version

fish, version 3.3.1

Warp Version

v0.2022.11.14.14.55.stable_01

Additional context

No response

Does this block you from using Warp daily?

Yes

Warp Internal (ignore): linear-label:b8107fdf-ba31-488d-b103-d271c89cac3e

No response

Dominant language
Rust
Stars
65.1k
Forks
5.6k
PR merge metrics
PR metrics pending

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from warpdotdev/warp

All issues in warpdotdev/warp

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.