Open mike-taylorprops opened 6 months ago
bean5
commented
3 months ago I am also experiencing issues with Warp. I think the faded hints are effectively part of the buffer and autokey is typing in so fast that they sometimes clash.
My version is v0.2024.06.04.08.02.stable_04
bean5
commented
1 month ago Still buggy as of v0.2024.07.23.08.02.stable_01. It actually seems worse now.
I just used an expansion on this version. The expansion typed out so fast, but some characters were in different places. I canceled the command and started typing it manually. But now the terminal is ignoring keystrokes. My keyboard is fine. Warp somehow got stuck in a strange state. I actually think that this means that if a malicious actor injected keys into warp fast enough it would end up broken like this and the user would be confused.
I'm not sure how big the vulnerability would be, but maybe this could be leveraged down the road. Who knows. Maybe @dannyneira
Discord username (optional)
No response
Describe the bug
Using Autokey in Warp does not work. It works in every other terminal I've used so it seems this is a Warp specific issue.
To reproduce
When attempting to enter a password with a keyboard shortcut all special characters are converted to numbers. For instance test!@#$ shows as test1234
Expected behavior
No response
Screenshots
No response
Operating system
Linux
Operating system and version
Pop!_OS 22.04 LTS
Shell Version
zsh 5.8.1 (x86_64-ubuntu-linux-gnu)
Current Warp version
No response
Regression
No, this bug or issue has existed throughout my experience using Warp
Recent working Warp date
No response
Additional context
No response
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