Hotkey window always not work

Open
#2,401 22 comments 7 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
macos, zsh
Domain
desktop

Research direction

No source files or tests are named. Start by reproducing the hotkey-window keybinding failure on macOS 13.1 with the reported Warp version and zsh, then verify that the configured shortcut continues to trigger after switching to a browser tab.

Written by the indexing model from the issue text.

Description

area:settings-keybindings area:window-tabs-panes bug ready-to-implement triaged
Describe the bug

Hi, I have not been able to successfully trigger the hotkey window on either of my M1 MacBooks over several months, and have been updated to the latest version during that time, I'm not sure what this is about, and would appreciate some ideas on how to resolve it, and I can provide additional information if needed.

I have tried reinstalling the warp application (but not removing the user configuration), turning off system accessibility permissions several times, restarting the system, etc., which occasionally triggered successfully a few times, but once I did something else (such as opening a new browser tab) it would not trigger again.

The shortcut keys have been tried in many combinations, and I can be sure that there is no conflict among them, including CMD + CTRL + , etc.

To Reproduce
image But the keybinding not work
Expected behaviour

No response

Screenshots

No response

Operating System

None

OS Version

13.1

Shell Version

zsh 5.8.1

Warp Version

v0.2022.12.13.08.04.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

None

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.