dannyneira
commented
4 months ago There could be something in your rc file causing this issue and Warp cannot parse it.
We have a list of known incompatible tools here: https://docs.warp.dev/help/known-issues#list-of-incompatible-tools And more info on supported custom prompts here: https://docs.warp.dev/features/prompt
Please send us your logs and also 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# Fish
if test "$TERM_PROGRAM" != "WarpTerminal"
# > What you want to disable here <
end
Dupe Check
Describe the bug
Why does warp get stuck for a long time every time I exit with cmd + Q?
To reproduce
Why does warp get stuck for a long time every time I exit with cmd + Q?
Expected behavior
No response
Screenshots
No response
Operating system
MacOS
Operating system and version
14.5.0
Shell Version
No response
Current Warp version
v0.2024.06.11.08.02.stable_03
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?
No
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