# What is the configuration used in the demo GIF?
- Terminal Emulator: iTerm2
- Shell: Fish Shell
<module>.disabled do the same thing?
Yes, they can both be used to disable modules in the prompt. If all you plan to do is disable modules,
<module>.disabled is the preferred way to do so for these reasons:
- Disabling modules is more explicit than omitting them from the prompt_order
- Newly created modules will be added to the prompt as Starship is updated
# The docs say Starship is cross-shell, but it doesn't support X shell. Why?
The way Starship is built, it should be possible to add support for virtually any shell. The starship binary is stateless and shell agnostic, so as long as your shell supports prompt customization and shell expansion, Starship can be used.
Here's a small example getting Starship working with bash:
# Get the status code from the last command executed STATUS=$? # Get the number of jobs running. NUM_JOBS=$(jobs -p | wc -l) # Set the prompt to the output of `starship prompt` PS1="$(starship prompt --status=$STATUS --jobs=$NUM_JOBS)"
The Bash implementation built into Starship is slightly more complex to allow for advanced features like the Command Duration module and to ensure that Starship is compatible with pre-installed Bash configurations.
For a list of all flags accepted by
starship prompt, use the following command:
starship prompt --help
The prompt will use as much context as is provided, but no flags are "required".
# How do I run Starship on Linux distributions with older versions of glibc?
If you get an error like "version 'GLIBC_2.18' not found (required by starship)" when using the prebuilt binary (for example, on CentOS 6 or 7), you can use a binary compiled with
musl instead of
curl -fsSL https://starship.rs/install.sh | bash -s -- --platform unknown-linux-musl