-
Notifications
You must be signed in to change notification settings - Fork 384
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tmux and Vim OPT keys no longer work #5666
Comments
Same issue on MACOS, option key with neovim doesn't work after the last update. |
same issue here |
Downgrading to the last version before 2025 that worked for me. https://stackoverflow.com/questions/58373704/how-do-you-specify-a-version-using-brew-cask |
Thanks @TimAnthonyAlexander Working with the previous version |
Downgrading warp in macos that worked for me: Here's the link: |
I'm also experiencing this issue on Macos, also could not find any settings that would alter the behaviour. |
Hey all, sorry about this - we're working on a fix that we'll release today. |
Hey all, this issue should be fixed in the newest release ( |
@lucieleblanc works for me now, thank you kindly for the quick fix 👍 |
Dupe Check
Describe the bug
Since the latest update, when in a tmux session or vim, the option key no longer does what it should. I can no longer type symbols like |\€, which I need.
To reproduce
Go into a tmux session (or nvim for that matter) and try to type chars that are typed with OPT.
Expected behavior
Like last versions. Should type the character
Screenshots
No response
Operating system
MacOS
Operating system and version
macOS 15.2
Shell Version
zsh 5.9 (arm64-apple-darwin24.0)
Current Warp version
v0.2025.01.08.08.02.stable_03
Regression
Yes, this bug started recently or with an X Warp version
Recent working Warp date
The last version before that. The changelog mentions something along the lines of meta key for option.
Additional context
No response
Does this block you from using Warp daily?
Yes, this issue prevents me from using Warp daily.
Is this an issue only in Warp?
Yes, I confirmed that this only happens in Warp, not other terminals.
Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e
None
The text was updated successfully, but these errors were encountered: