starship/docs/faq
Jan Katins 17e8115f16
docs: Improvements in docs for custom modules (#1615)
* docs: Clarify that commands will be passed in on stdin

* docs: Clearer instruction how to include individual custom modules

* docs: Include link to #1252 in docs for custom modules

That issue is used to share custom modules.

* docs: Remove reference to prompt_order

Co-authored-by: Thomas O'Donnell <andytom@users.noreply.github.com>

Co-authored-by: Thomas O'Donnell <andytom@users.noreply.github.com>
2020-09-01 19:07:12 +02:00
..
README.md docs: Improvements in docs for custom modules (#1615) 2020-09-01 19:07:12 +02:00

FAQ

What is the configuration used in the demo GIF?

Do top level format and <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 top level format
  • 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 glibc:

curl -fsSL https://starship.rs/install.sh | bash -s -- --platform unknown-linux-musl

Why don't I see a glyph symbol in my prompt?

The most common cause of this is system misconfiguration. Some Linux distros in particular do not come with font support out-of-the-box. You need to ensure that:

  • Your locale is set to a UTF-8 value, like de_DE.UTF-8 or ja_JP.UTF-8. If LC_ALL is not a UTF-8 value, you will need to change it.
  • You have an emoji font installed. Most systems come with an emoji font by default, but some (notably Arch Linux) do not. You can usually install one through your system's package manager--noto emoji is a popular choice.
  • You are using a Nerd Font.

To test your system, run the following commands in a terminal:

echo -e "\xf0\x9f\x90\x8d"
echo -e "\xee\x82\xa0"

The first line should produce a snake emoji, while the second should produce a powerline branch symbol (e0a0).

If either symbol fails to display correctly, your system is still misconfigured. Unfortunately, getting font configuration correct is sometimes difficult. Users on the Discord may be able to help. If both symbols display correctly, but you still don't see them in starship, file a bug report!

How do I uninstall Starship?

Starship is just as easy to uninstall as it is to install in the first place.

  1. Remove any lines in your shell config (e.g. ~/.bashrc) used to initialize Starship.
  2. Delete the Starship binary.

If Starship was installed using a package manager, please refer to their docs for uninstallation instructions.

If Starship was installed using the curl | bash script, the following command will delete the binary:

# Locate and delete the starship binary
rm "$(which starship)"