Discussion: Installation process about starship HOT 6 CLOSED

@matchai I’d prefer for the second option (where we can install via package managers), as users are most familiar with the method and it’s the easiest to install (I like to have everything installed via a package manager ... not having to run scripts)

from starship.

Oops, I thought I had responded earlier. We could do both!

Let's say binary is installed, people can either add it themselves or do starship launch to launch with autopilot, we detect what shell is being used and the user and automatically do it, and switch straight into starship. 😊

Maybe even add a quick, cute ASCII animation that shows what's happening.
3... 2... 1... ☁️🚀

Proposed Steps

1. Do brew install starship or apt install starship.
2. Do starship launch.
3. ☄️

from starship.

@matchai Weirdly, I actually like the first option the most.
A single simple line to add to your config it just works! ✨🚀

It would feel just... wrong for it to be shipped in omf/fisher/Antigen/Zgen etc. considering it's a system-wide prompt that's globally cross-compatible with any of the three popular shells.

What if I use both Bash, Fish and Zsh and want to have Starship for all three? Or just two of them (Zsh & Fish) to use Starship? What if I install Starship with both omf, fisher and antigen? What happens? D:

This gets incredibly complicated with the other two options but stays super simple with number 1.

from starship.

For the v1.0.0 release, I definitely think the first option is the way to go.
It'd be quick to implement and easy to document. The last two options would be more of a v2.0.0 task if we decided to proceed with them.

@Snuggle would you prefer it if we automatically added it to their config files, or asked them to do it themselves after the binary installation?

from starship.

Sounds like a good way to get started 👍

Maybe even add a quick, cute ASCII animation that shows what's happening.
3... 2... 1... ☁️🚀

Yesss! 😍

from starship.

After a good amount of testing in basic-init branch, it looks like we can't get enough context from environment variables alone to identify the shell. Fish is able to be reliably identified with $SHELL, but it appears zsh and bash don't export the environment variables that would make them identifiable ($BASH or $SHELL).

Though it's a little more inelegant, my next thought is to do the following:

eval $(SHELL=zsh starship init)

# or 

export STARSHIP_SHELL=zsh
eval $(starship init)

Does anyone have other ideas? 🤔

from starship.