warpdotdev / warpdotdev/warp

linux: fish fzf shortcut keys are not triggered

Open
#4,125 7 comments 7 reactions 1 assignee View on GitHub

@acarl005 is already working on this.

Since Aug 26, 2026.

area:settings-keybindings bug factory:wilson ready-to-implement triaged
Dominant language
Rust
Stars
65.1k
Forks
5.6k
PR merge metrics
PR metrics pending

Description

Discord username (optional)

No response

Describe the bug

While using fzf.fish. all the triggered shortcut are not appearing

To reproduce
  1. Use fish shell
  2. install fish plugin https://github.com/PatrickF1/fzf.fish
  3. press ctrl+alt+f for displaying file completion
Expected behavior

file should appear like in other terminal

Screenshots

example of same command running on other terminal
image

Operating system

Linux

Operating system and version

39.0.0

Shell Version

fish 3.7.0

Current Warp version

v0.2024.01.30.16.52.stable_00

Regression

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

Recent working Warp date

No response

Additional context

executing this on warp, give this message

16:10:00 [INFO] dispatching typed action: UnhandledModifierKey("ctrl-alt-f")
16:10:00 [INFO] dispatching typed action: UnhandledModifierKey("ctrl-alt-f")
16:10:01 [INFO] dispatching typed action: UnhandledModifierKey("ctrl-alt-f")
16:10:01 [INFO] dispatching typed action: UnhandledModifierKey("ctrl-alt-f")

I'm using completion alot.

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.

Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e

None

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.