Global Hotkey Window "Active Screen" Option Doesn't Work With Multiple Screens

Open
#3,490 13 comments 23 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
Clearly specified
Activity status
Stale
Tech stack
macos
Domain
desktop

Research direction

Start in Settings → Features → Global hotkey and reproduce the Dedicated hotkey window behavior with Active Screen selected while focus is on a non-main display. Confirm that the window opens on the focused screen rather than the main screen, and verify the behavior on macOS with multiple screens.

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

The "Active Screen" settings option under the Global hotkey window does NOT open the hotkey window in the currently active (focused) window but in the main screen.

Unfortunately, this bug is why I'm avoiding switching to Warp entirely.

To reproduce

Go to settings -> features -> Global hotkey.
Choose "Dedicated hotkey window", define a keyboard binding, and set "Active Screen".
Focus on a screen other than the main one, and press the hotkey keyboard sequence defined above.
The hotkey window still opens on the main screen.

Expected behavior

The hotkey window should be open in the currently active/focused screnn.screen

Operating system

MacOS

Operating system and version

macOS 13.5

Shell Version

zsh 5.9

Current Warp version

v0.2023.08.01.08.05.stable_03

Regression

No, this bug or issue has existed throughout my experience using Warp

Does this block you from using Warp daily?

Yes, this issue prevents me from using Warp daily.

Is this a Warp specific issue? (i.e. does it happen in Terminal, iTerm, Kitty, etc.)

Yes, this I confirmed this only happens in Warp, not other terminals.

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.