You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @kirs112 thanks for letting us know. I'm noticing similar behavior in other terminals, it appears since your passed an invalid command into exec the terminal hands-off to nothing instead of printing the "command not found" error. As a workaround, I recommend passing only known installed binaries to exec. You can find if the binary is installed in the system by running which <app_name> to confirm it's in the system PATH.
I'll let the team know and we'll post updates on this thread.
To anyone else facing this issue, please add a 👍 to the original post at the top or comment with your details, and subscribe if you'd like to be notified.
Dupe Check
Describe the bug
macos executes commands via exec and the program just exits.
To reproduce
exec Terminal
Expected behavior
No response
Screenshots
2024-06-30.01-16-54.mp4
Operating system
MacOS
Operating system and version
Mac os sonoma 14.5
Shell Version
No response
Current Warp version
v0.2024.06.25.08.02.stable_01
Regression
Yes, this bug started recently or with an X Warp version
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
The text was updated successfully, but these errors were encountered: