Open popfido opened 6 months ago
I also experienced almost the same thing, the command execution did not start immediately when I pressed enter, I had to press the enter key several times.
I also experienced almost the same thing, the command execution did not start immediately when I pressed enter, I had to press the enter key several times.
For me the problem is even more severe that I, not only need to press the enter key several times, but also not sure how long is the response time after I pressed and whether the command truly effects. Currently I don't have an accurate way to stably reproduce this bug but it just keep emerging.
Hey folks, my guess is that you normally have a custom prompt, theme, or bash/zsh/fish plugin and Warp is unable to parse it.
You can check whether it’s something in your dotfiles by setting up clean configs:
Run echo 'ZDOTDIR=/' > ~/.zshenv
This forces Zsh to run with zero configs.
We have a list of incompatible tools here: https://docs.warp.dev/help/known-issues#list-of-incompatible-tools You can disable parts of your dotfiles just for Warp by using this conditional statement:
# Bash and Zsh
if [[ $TERM_PROGRAM != "WarpTerminal" ]]; then
# > What you want to disable here <
fi
If commenting out the rc files doesn't help with the slow issues please let us know and provide copy of the logs. https://docs.warp.dev/help/sending-us-feedback
Dupe Check
Describe the bug
The reacting time of each operation becomes quite long and can't quite Warp Terminal through ordinary way. I can just close Warp from Activity Monitor with force quit.
To reproduce
Expected behavior
terminal react at a very quick speed and can exit.
Screenshots
Operating system
MacOS
Operating system and version
14.5 (23F79)
Shell Version
zsh 5.9 (x86_64-apple-darwin23.0)
Current Warp version
v0.2024.05.07.08.02.stable_02
Regression
Yes, this bug started recently or with an X Warp version
Recent working Warp date
2 months earlier
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