Open Ocayy opened 6 months ago
Hey @Ocayy Sorry to hear about this issue. Is it possible for you to try and run the upgrade script manually and see if the issue persists? cd ~/.oh-my-zsh/ ; ./tools/upgrade.sh
Please send a screenshot/video of the issue once you run the script.
Also, what version of ohmyzsh are you using currently?
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.
Same problem here:
Need to open iterm to update almost weekly ohmyzsh...
I've started using Warp recently and just faced that issue
On Linux happens too, every omz update stuck warp on startup. But I have a work arround for this issue.
Discord username (optional)
No response
Describe the bug
When starting Warp (or any other terminal) OMZ checks for updates and if there is one users get asked if they want to update it by simply selecting Y (yes) or N (no). However, on Warp, it is impossible to accept that update or even use the tab where it appeared after.
To reproduce
Just install older version of OMZ and wait for OMZ to check for updates.
Expected behavior
No response
Screenshots
No response
Operating system
MacOS
Operating system and version
14.2.1
Shell Version
No response
Current Warp version
v0.2024.01.02.08.02.stable_02
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