Does it make sense to switch to the new custom prompts feature if using flex-prompt already?

[narnaud]

I switched to clink because of the slowness of powershell (just start a shell, wait 2-3s).
One of the thing I like about Powershell was Oh-My-Posh, even if it slowed things quite a bit in git repository.

Then I discovered clink-flex-prompt, which is just perfect with the async updates of git status.

I'm a happy flex-prompt user, does it make sense for me to try and sswitch to the new custom prompts feature? Does it support async prompts?

Thanks.

[chrisant996]

Use whatever prompt you like best. 🙂

My personal favorites are flexprompt in Bubbles style, and the Headline prompt.

The new custom prompt stuff is designed to make it easy to change what prompt you're using, and to preview what other prompts will look like.

But which prompt you choose to use is a very subjective decision based on personal preference. I just wanted to make it easy to experiment and find that personal preference.

And yes, all of the prompts that come with Clink support async. (But other prompts might not; it's up to each prompt author.)

[chrisant996]

So, it's easy to preview and experiment, without actually changing your prompt.

clink config prompt show and then use completion to see what ones are available, and choose one and hit Enter to see a preview.

If you want to actually try one out, then
clink config prompt use ThePromptName

If you want to revert back, then
clink config prompt clear