Input Editor: Prompt: Support a fully customizable prompt (and/or honor PS1)

[zachlloyd]

Right now we make our best guess at a useful default prompt, but don't support any customization.

The likely path forward is for us to put a nicer UI on prompt customizability and support generally useful prompt features like git status.

Another option would be to fall-back to PS1 for prompt rendering, but that would mean we'd need to support a full terminal grid in the prompt section of the input. I think we would probably only do this as a fallback, not the primary customization method.

[m50]

It looks like you use starship for the prompt? Could be wrong on this.

If so, utilize the starship configuration (~/.config/starship.toml) when rendering starship, because that's an easy win for prompt customization, easier than supporting a full custom PS1.

[zachlloyd]

We don't use starship, but using the configuration (or at least being compatible with it) is an interesting idea. Thank you for suggesting it!

…

On Wed, Aug 25, 2021 at 9:19 AM Marisa ***@***.***> wrote: It looks like you use starship for the prompt? Could be wrong on this. If so, utilize the starship configuration (~/.config/starship.toml) when rendering starship, because that's an easy win for prompt customization, easier than supporting a full custom PS1. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#96 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACCSUZN3Z7PVSSUH5ZDAKOLT6TUW5ANCNFSM5BRR7BDA> .

[TreTuna]

Custom prompt is something that I'm definitely missing a lot with Warp right now. The primary ones I've been using as of late have been Powerlevel10k and Starship (which has been taking over my prompts on most machines as of late). I would agree with @m50 here that just having Starship and using the customization from that would be amazing.

[lrvdijk]

Another point: I often use Conda (python) environments, and when you activate one, it often updates the prompt to show that it's active. Currently there's no indication of any active conda environment after conda activate your-env.

[anicholson-sq]

Yeah, not seeing the PROMPT I was expecting (also Starship) was rather jarring. It made me wonder what else from my .zshrc was being ignored/overridden.

[kaihoffman]

I also would absolutely need things from my bash PS1 to show to feel I could use Warp fully, namely my git branch and current Kubernetes context. These are currently set by scripts that show as part of the bash PS1

[zachlloyd]

@gagata is starting to explore solutions here. Would love all of your input as we spec things out.

[lak]

I'm also finding it jarring not to have my prompt. There's a lot of info in my prompt that isn't in this one.

It's especially useless because I don't even know what's in this prompt. Do the colors mean anything? I don't know. What systems are supported and which aren't? I don't know. The only real mention of the prompt in the docs is that you don't support PROMPT_COMMAND, and there's no mention of PS1.

[elviskahoro]

Hopefully this quarter!