Bug with spaceship prompt theme.

[namirinz]

Discord username (optional)

No response

Describe the bug

It produce the prefix text from default spaceship-prompt theme

~
->

Screen.Recording.2565-10-18.at.15.19.19.mov

To Reproduce

1. Start the warp terminal
2. Bug appear

Expected behaviour

Test on default terminal app for Mac

Screenshots

No response

Operating System

MacOS

OS Version

12.6

Shell Version

zsh 5.8.1 (x86_64-apple-darwin21.0)

Warp Version

v0.2022.10.11.08.13.stable_01

Additional context

No response

Does this block you from using Warp daily?

Yes

Warp Internal (ignore): linear-label:b8107fdf-ba31-488d-b103-d271c89cac3e

No response

[dannyneira]

Hi @namirinz, Sorry to hear about this, although we generally support OMZ, we don't support multi or right-sided prompts at this time, which spaceship theme appears to have. Please see more here

Can you please confirm you're not using a multi/right-sided prompt if not, let us know your configuration so we can attempt to reproduce.

[danilopolani]

Same issue here. There's nothing special needed to reproduce it: just install Warp and the Spaceship theme for Oh My Zsh.
The only thing I can do right now is to disable Spaceship for Warp and use it in VSCode and somewhere else when needed:

if [[ $TERM_PROGRAM != "WarpTerminal" ]]; then
    ZSH_THEME="spaceship"
fi

[enavarrocu]

This was working in a previous version of spaceship I upgraded today to the version 4 of spaceship and started failing in warp.

Update: Looks like is a combination between spaceship and warp. If you set SPACESHIP_PROMPT_ASYNC=false it works fine.

[danilopolani]

This was working in a previous version of spaceship I upgraded today to the version 4 of spaceship and started failing in warp.

Update: Looks like is a combination between spaceship and warp. If you set SPACESHIP_PROMPT_ASYNC=false it works fine.

Can confirm that SPACESHIP_PROMPT_ASYNC=false works. Or, at least, it does not create a wrong output in the shell.
It still does not show the Spaceship data (e.g. current k8s environment), but that's okay I guess.

Standard terminal:

Warp:

[enavarrocu]

For me, it shows correctly. I'm not using k8s.

[danilopolani]

For me, it shows correctly. I'm not using k8s.

Oh right, I had to enable the Honor user's custom prompt (PS1) Feature flag, now it works perfectly, thank you!

[dannyneira]

@namirinz are you still seeing this issue after recent updates?

[bfaulk96]

@dannyneira I am seeing it with the most updated version

[dannyneira]

@namirinz @bfaulk96
Run echo "SPACESHIP_PROMPT_ASYNC=FALSE" >>! ~/.zshrc, then open a new Tab CMD-T and let us know if the issue persists.

[dannyneira]

Opened a bug report with the Spaceship team here to track this issue: spaceship-prompt/spaceship-prompt#1311

[bfaulk96]

@dannyneira that did indeed work, sorry for not reading the thread more completely before commenting!

[maurelian]

Same issue, but the suggested fix does not work.
i.e. After adding SPACESHIP_PROMPT_ASYNC=FALSE to my .zshrc file and opening a new tab (with "honor custom prompt" enabled), I have a blank prompt.

Manually running source .zshrc again properly activates my prompt, but I'd rather not have to do this everytime I open a new tabl.

[dannyneira]

@maurelian I wonder if there is anything else in your rc file causing this. Opening new tabs/windows/panes should automatically "source" the .zshrc file. Please see: https://docs.warp.dev/help/known-issues#configuring-and-debugging-your-rc-files