chore(release): v0.51.0

Bumps [serde](https://github.com/serde-rs/serde) from 1.0.124 to 1.0.125.
- [Release notes](https://github.com/serde-rs/serde/releases)
- [Commits](https://github.com/serde-rs/serde/compare/v1.0.124...v1.0.125)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

.cargo/audit.toml

@@ -0,0 +1,2 @@
+[advisories]
+ignore = ["RUSTSEC-2020-0100"]

.github/ISSUE_TEMPLATE/config.yml

@@ -1,5 +1,5 @@
 blank_issues_enabled: false
 contact_links:
   - name:  🙏 Ask a question
-    url: https://github.com/starship/starship/discussions/new?category_id=65593
+    url: https://github.com/starship/starship/discussions/new?category=q-a
     about: Ask the community for help

.github/workflows/deploy.yml

@@ -33,35 +33,73 @@ jobs:
         env:
           COMMITTER_TOKEN: ${{ secrets.HOMEBREW_GITHUB_API_TOKEN }}
 
+  publish_docs:
+    name: Publish docs to Netlify
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Setup | Checkout
+        uses: actions/checkout@master
+
+      - name: Publish
+        uses: netlify/actions/build@master
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          NETLIFY_SITE_ID: ${{ secrets.NETLIFY_SITE_ID }}
+
   # Build sources for every OS
   github_build:
     name: Build release binaries
     strategy:
       fail-fast: false
       matrix:
-        target:
-          - x86_64-unknown-linux-gnu
-          - x86_64-unknown-linux-musl
-          - i686-unknown-linux-musl
-          - x86_64-apple-darwin
-          - x86_64-pc-windows-msvc
         include:
           - target: x86_64-unknown-linux-gnu
             os: ubuntu-latest
             name: starship-x86_64-unknown-linux-gnu.tar.gz
+
           - target: x86_64-unknown-linux-musl
             os: ubuntu-latest
             name: starship-x86_64-unknown-linux-musl.tar.gz
+
           - target: i686-unknown-linux-musl
             os: ubuntu-latest
             name: starship-i686-unknown-linux-musl.tar.gz
+
+          - target: aarch64-unknown-linux-musl
+            os: ubuntu-latest
+            name: starship-aarch64-unknown-linux-musl.tar.gz
+
+          - target: arm-unknown-linux-musleabihf
+            os: ubuntu-latest
+            name: starship-arm-unknown-linux-musleabihf.tar.gz
+
           - target: x86_64-apple-darwin
             os: macOS-latest
             name: starship-x86_64-apple-darwin.tar.gz
+
+          - target: aarch64-apple-darwin
+            os: macOS-latest
+            name: starship-aarch64-apple-darwin.tar.gz
+
           - target: x86_64-pc-windows-msvc
             os: windows-latest
             name: starship-x86_64-pc-windows-msvc.zip
+
+          - target: i686-pc-windows-msvc
+            os: windows-latest
+            name: starship-i686-pc-windows-msvc.zip
+
+          - target: aarch64-pc-windows-msvc
+            os: windows-latest
+            name: starship-aarch64-pc-windows-msvc.zip
+
+          - target: x86_64-unknown-freebsd
+            os: ubuntu-latest
+            name: starship-x86_64-unknown-freebsd.tar.gz
+
     runs-on: ${{ matrix.os }}
+    continue-on-error: true
     steps:
       - name: Setup | Checkout
         uses: actions/checkout@v2
@@ -83,27 +121,17 @@ jobs:
           profile: minimal
           target: ${{ matrix.target }}
 
-      - name: Setup | musl tools
-        if: contains(matrix.target, 'musl')
-        run: sudo apt install -y musl-tools
-
       - name: Build | Build
-        if: "! contains(matrix.target, 'musl')"
-        uses: actions-rs/cargo@v1
-        with:
-          command: build
-          args: --release --target ${{ matrix.target }}
-          use-cross: true
-
-      - name: Build | Build [musl]
-        if: contains(matrix.target, 'musl')
         uses: actions-rs/cargo@v1
+        # TODO: Remove this once it's the default
+        env:
+          SDKROOT: /Library/Developer/CommandLineTools/SDKs/MacOSX11.1.sdk
         with:
           command: build
           args: --release --features tls-vendored --target ${{ matrix.target }}
-          use-cross: true
+          use-cross: ${{ matrix.os == 'ubuntu-latest' }}
 
-      - name: Post Setup | Prepare artifacts [Windows]
+      - name: Post Build | Prepare artifacts [Windows]
         if: matrix.os == 'windows-latest'
         run: |
           cd target/${{ matrix.target }}/release
@@ -111,15 +139,16 @@ jobs:
           7z a ../../../${{ matrix.name }} starship.exe
           cd -
 
-      - name: Post Setup | Prepare artifacts [-nix]
+      - name: Post Build | Prepare artifacts [-nix]
         if: matrix.os != 'windows-latest'
         run: |
           cd target/${{ matrix.target }}/release
-          strip starship
+          # TODO: investigate better cross platform stripping
+          strip starship || true
           tar czvf ../../../${{ matrix.name }} starship
           cd -
 
-      - name: Post Setup | Upload artifacts
+      - name: Deploy | Upload artifacts
         uses: actions/upload-artifact@v2
         with:
           name: ${{ matrix.name }}
@@ -139,7 +168,7 @@ jobs:
       - name: Setup | Go
         uses: actions/setup-go@v2
         with:
-          go-version: "^1.13.1"
+          go-version: "^1.15.7"
 
       - name: Setup | Artifacts
         uses: actions/download-artifact@v2
@@ -149,7 +178,7 @@ jobs:
 
       - name: Setup | Release notes
         run: |
-          go get -u github.com/git-chglog/git-chglog/cmd/git-chglog
+          GO111MODULE=on go get github.com/git-chglog/git-chglog/cmd/git-chglog@0.9.1
           git-chglog -c .github/chglog/release.yml $(git describe --tags) > RELEASE.md
 
       - name: Build | Publish
@@ -159,22 +188,3 @@ jobs:
           body_path: RELEASE.md
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-  aur_release:
-    runs-on: ubuntu-latest
-    name: Create AUR release
-    needs: github_release # The -bin version downloads and shasums it
-    steps:
-      - name: Build | Publish AUR package
-        uses: ATiltedTree/create-aur-release@v1
-        with:
-          package_name: starship
-          commit_username: "Starship Bot"
-          commit_email: starship.bot.noreply@gmail.com
-          ssh_private_key: ${{ secrets.AUR_SSH_PRIVATE_KEY }}
-      - name: Build | Publish AUR package (-bin version)
-        uses: ATiltedTree/create-aur-release@v1
-        with:
-          package_name: starship-bin
-          commit_username: "Starship Bot"
-          commit_email: starship.bot.noreply@gmail.com
-          ssh_private_key: ${{ secrets.AUR_SSH_PRIVATE_KEY }}

.github/workflows/workflow.yml

@@ -140,7 +140,7 @@ jobs:
       # Install Mercurial (pre-installed on Linux and windows)
       - name: Setup | Mercurial (macos)
         if: matrix.os == 'macOS-latest'
-        run: pip3 install mercurial
+        run: brew install mercurial
 
       # Run the ignored tests that expect the above setup
       - name: Build | Test

CONTRIBUTING.md

@@ -37,7 +37,6 @@ use super::{Context, Module, RootModuleConfig};
 
 use crate::configs::php::PhpConfig;
 use crate::formatter::StringFormatter;
-use crate::utils;
 
 
 pub fn module<'a>(context: &'a Context) -> Option<Module<'a>> {
@@ -51,20 +50,19 @@ pub fn module<'a>(context: &'a Context) -> Option<Module<'a>> {
 
 ## External commands
 
-To run a external command (e.g. to get the version of a tool) and to allow for mocking use the `utils::exec_cmd` function. Here's a quick example:
+To run a external command (e.g. to get the version of a tool) and to allow for mocking use the `context.exec_cmd` function. Here's a quick example:
 
 ```rust
 use super::{Context, Module, RootModuleConfig};
 
 use crate::configs::php::PhpConfig;
 use crate::formatter::StringFormatter;
-use crate::utils;
 
 
 pub fn module<'a>(context: &'a Context) -> Option<Module<'a>> {
-   // Here `my_env_var` will be either the stdout of the called command or the function
+   // Here `output` will be either the stdout of the called command or the function
    // will exit if the called program was not installed or could not be run.
-   let output = utils::exec_cmd("my_command", &["first_arg", "second_arg"])?.stdout;
+   let output = context.exec_cmd("my_command", &["first_arg", "second_arg"])?.stdout;
 
    // Then you can happily use the output
 }

Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "starship"
-version = "0.48.0"
+version = "0.51.0"
 edition = "2018"
 authors = ["Matan Kushner <hello@matchai.me>"]
 homepage = "https://starship.rs"
@@ -10,6 +10,7 @@ readme = "README.md"
 license = "ISC"
 keywords = ["prompt", "shell", "bash", "fish", "zsh"]
 categories = ["command-line-utilities"]
+build = "build.rs"
 description = """
 The minimal, blazing-fast, and infinitely customizable prompt for any shell! ☄🌌️
 """
@@ -31,42 +32,45 @@ tls-vendored = ["native-tls/vendored"]
 clap = "2.33.3"
 ansi_term = "0.12.1"
 dirs-next = "2.0.0"
-git2 = { version = "0.13.15", default-features = false }
+git2 = { version = "0.13.17", default-features = false }
 toml = { version = "0.5.8", features = ["preserve_order"] }
-rust-ini = "0.16.0"
-serde_json = "1.0.61"
+rust-ini = "0.16.1"
+serde_json = "1.0.64"
 rayon = "1.5.0"
-log = { version = "0.4.11", features = ["std"] }
+log = { version = "0.4.14", features = ["std"] }
 # battery is optional (on by default) because the crate doesn't currently build for Termux
 # see: https://github.com/svartalf/rust-battery/issues/33
 battery = { version = "0.7.8", optional = true }
-path-slash = "0.1.3"
+path-slash = "0.1.4"
 unicode-segmentation = "1.7.1"
 gethostname = "0.2.1"
-once_cell = "1.5.2"
+once_cell = "1.7.2"
 chrono = "0.4.19"
-sys-info = "0.7.0"
-byte-unit = "4.0.9"
+sys-info = "0.8.0"
+byte-unit = "4.0.10"
 starship_module_config_derive = { version = "0.1.2", path = "starship_module_config_derive" }
-yaml-rust = "0.4.4"
+yaml-rust = "0.4.5"
 pest = "2.1.3"
 pest_derive = "2.1.0"
-regex = "1.4.2"
+regex = "1.4.5"
 os_info = "3.0.1"
 urlencoding = "1.1.1"
-open = "1.4.0"
+open = "1.6.0"
 unicode-width = "0.1.8"
 term_size = "0.3.2"
-quick-xml = "0.20.0"
-rand = "0.8.0"
-serde = { version = "1.0.118", features = ["derive"] }
-indexmap = "1.6.1"
-notify-rust = { version = "4.0.0", optional = true }
+quick-xml = "0.22.0"
+rand = "0.8.3"
+serde = { version = "1.0.125", features = ["derive"] }
+indexmap = "1.6.2"
+notify-rust = { version = "4.3.0", optional = true }
 semver = "0.11.0"
 which = "4.0.2"
+shadow-rs = "0.5.24"
+
+process_control = { version = "3.0.1", features = ["crossbeam-channel"] }
 
 # Optional/http:
-attohttpc = { version = "0.16.0", optional = true, default-features = false, features = ["tls", "form"] }
+attohttpc = { version = "0.16.3", optional = true, default-features = false, features = ["tls", "form"] }
 native-tls = { version = "0.2.7", optional = true }
 shell-words = "1.0.0"
 
@@ -80,10 +84,13 @@ winapi = { version = "0.3.9", features = [
 ] }
 
 [target.'cfg(not(windows))'.dependencies]
-nix = "0.19.1"
+nix = "0.20.0"
+
+[build-dependencies]
+shadow-rs = "0.5.24"
 
 [dev-dependencies]
-tempfile = "3.1.0"
+tempfile = "3.2.0"
 
 [profile.release]
 codegen-units = 1

Cross.toml

@@ -0,0 +1,2 @@
+[target.x86_64-unknown-freebsd]
+image = "docker.io/rustembedded/cross:x86_64-unknown-freebsd"

LICENSE

@@ -1,6 +1,6 @@
 ISC License
 
-Copyright (c) 2019-2020, Starship Contributors
+Copyright (c) 2019-2021, Starship Contributors
 
 Permission to use, copy, modify, and/or distribute this software for any
 purpose with or without fee is hereby granted, provided that the above

README.md

@@ -22,7 +22,7 @@
       src="https://img.shields.io/repology/repositories/starship?label=in%20repositories&style=flat-square"
       alt="Packaging status"/></a
   ><br />
-  <a href="https://discord.gg/8Jzqu3T"
+  <a href="https://discord.gg/starship"
     ><img
       src="https://img.shields.io/discord/567163873606500352?label=discord&logoColor=white&style=flat-square"
       alt="Chat on Discord"
@@ -105,6 +105,14 @@
       src="https://raw.githubusercontent.com/starship/starship/master/media/flag-fr.png"
       alt="Français"
   /></a>
+  &nbsp;
+  <a 
+    href="https://github.com/starship/starship/blob/master/docs/vi-VN/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-vn.png"
+      alt="Tiếng Việt"
+  /></a>
 </p>
 
 <h1></h1>
@@ -139,6 +147,9 @@
 
 ### Getting Started
 
+**Note**: due to the proliferation of different platforms, only a subset of supported platforms are
+shown below. Can't see yours? Have a look at the [extra platform instructions](https://starship.rs/installing/).
+
 1. Install the **starship** binary:
 
    #### Install Latest Version
@@ -149,15 +160,9 @@
    curl -fsSL https://starship.rs/install.sh | bash
    ```
 
-   ##### From source on [crates.io](https://crates.io/):
-
-   ```sh
-   cargo install starship
-   ```
-
    #### Install via Package Manager
 
-   ##### With [Homebrew](https://brew.sh/):
+   ##### Example: [Homebrew](https://brew.sh/):
 
    ```sh
    brew install starship
@@ -169,7 +174,7 @@
    scoop install starship
    ```
 
-1. Add the init script to your shell's config file:
+2. Add the init script to your shell's config file:
 
    #### Bash
 
@@ -205,7 +210,7 @@
 
    Add the following to the end of `Microsoft.PowerShell_profile.ps1`. You can check the location of this file by querying the `$PROFILE` variable in PowerShell. Typically the path is `~\Documents\PowerShell\Microsoft.PowerShell_profile.ps1` or `~/.config/powershell/Microsoft.PowerShell_profile.ps1` on -Nix.
 
-   ```sh
+   ```powershell
    Invoke-Expression (&starship init powershell)
    ```
 
@@ -219,6 +224,27 @@
    eval $(starship init ion)
    ```
 
+   #### Elvish
+
+   **Warning** Only elvish v0.15 or higher is supported.
+   Add the following to the end of `~/.elvish/rc.elv`:
+
+   ```sh
+   # ~/.elvish/rc.elv
+
+   eval (starship init elvish)
+   ```
+
+   #### Tcsh
+
+   Add the following to the end of `~/.tcshrc`:
+
+   ```sh
+   # ~/.tcshrc
+
+   eval `starship init tcsh`
+   ```
+
 ## 🤝 Contributing
 
 We are always looking for contributors of **all skill levels**! If you're looking to ease your way into the project, try out a [good first issue](https://github.com/starship/starship/labels/🌱%20good%20first%20issue).

build.rs

@@ -0,0 +1,3 @@
+fn main() -> shadow_rs::SdResult<()> {
+    shadow_rs::new()
+}

crowdin.yml

@@ -1,3 +1,4 @@
+pull_request_title: 'docs(i18n): new Crowdin updates'
 files:
   - source: /docs/**/*.md
     ignore:

docs/.vuepress/config.js

@@ -39,6 +39,11 @@ module.exports = {
       lang: "zh-TW",
       title: "Starship",
       description: "The minimal, blazing-fast, and infinitely customizable prompt for any shell!"
+    },
+    "/vi-VN/": {
+      lang: "vi-VN",
+      title: "Starship",
+      description: "Nhỏ gọn, cực nhanh, và khả năng tuỳ chỉnh vô hạn prompt cho bất kì shell nào!"
     }
   },
   // prettier-ignore
@@ -71,11 +76,6 @@ module.exports = {
       apiKey: "107bdc34b894d5d1dd0824b420184c2d",
       indexName: "starship"
     },
-    postcss: {
-      plugins: [
-        require('css-prefers-color-scheme/postcss'),
-      ]
-    },
     locales: {
       "/": {
         // text for the language dropdown
@@ -90,6 +90,7 @@ module.exports = {
         sidebar: [
           "/",
           ["/guide/", "Guide"],
+          ["/installing/", "Advanced Installation"],
           ["/config/", "Configuration"],
           ["/advanced-config/", "Advanced Configuration"],
           ["/faq/", "Frequently Asked Questions"],
@@ -228,6 +229,25 @@ module.exports = {
           ["/zh-CN/faq/", "常见问题"],
           ["/zh-CN/presets/", "社区配置分享"]
         ]
+      },
+      "/vi-VN/": {
+        // text for the language dropdown
+        selectText: "Ngôn ngữ",
+        // label for this locale in the language dropdown
+        label: "Tiếng Việt",
+        // Custom text for edit link. Defaults to "Edit this page"
+        editLinkText: "Chỉnh sửa trang này trên GitHub",
+        // Custom navbar values
+        nav: [{ text: "Cấu hình", link: "/vi-VN/config/" }],
+        // Custom sidebar values
+        sidebar: [
+          "/vi-VN/",
+          ["/vi-VN/guide/", "Hướng dẫn"],
+          ["/vi-VN/config/", "Cấu hình"],
+          ["/vi-VN/advanced-config/", "Cấu hình nâng cao"],
+          ["/vi-VN/faq/", "Các hỏi thường gặp"],
+          ["/vi-VN/presets/", "Mẫu thiết lập"]
+        ]
       }
     }
   },

docs/README.md

@@ -101,3 +101,27 @@ description: Starship is the minimal, blazing fast, and extremely customizable p
 
    eval $(starship init ion)
    ```
+   #### Elvish
+
+   ::: warning
+   Only elvish v0.15 or higher is supported.
+   :::
+
+   Add the following to the end of `~/.elvish/rc.elv`:
+
+   ```sh
+   # ~/.elvish/rc.elv
+
+   eval (starship init elvish)
+   ```
+
+   #### Tcsh
+
+   Add the following to the end of `~/.tcshrc`:
+
+   ```sh
+   # ~/.tcshrc
+
+   eval `starship init tcsh`
+   ```
+

docs/ar-SA/README.md

@@ -0,0 +1,136 @@
+---
+home: true
+heroImage: /logo.svg
+heroText:
+tagline: The minimal, blazing-fast, and infinitely customizable prompt for any shell!
+actionText: Get Started →
+actionLink: ./guide/
+features:
+  - 
+    title: Compatibility First
+    details: Works on the most common shells on the most common operating systems. Use it everywhere!
+  - 
+    title: Rust-Powered
+    details: Brings the best-in-class speed and safety of Rust, to make your prompt as quick and reliable as possible.
+  - 
+    title: Customizable
+    details: Every little detail is customizable to your liking, to make this prompt as minimal or feature-rich as you'd like it to be.
+footer: ISC Licensed | Copyright © 2019-present Starship Contributors
+#Used for the description meta tag, for SEO
+metaTitle: "Starship: Cross-Shell Prompt"
+description: Starship is the minimal, blazing fast, and extremely customizable prompt for any shell! Shows the information you need, while staying sleek and minimal. Quick installation available for Bash, Fish, ZSH, Ion, and PowerShell.
+---
+
+<div class="center">
+  <video class="demo-video" muted autoplay loop playsinline>
+    <source src="/demo.webm" type="video/webm">
+    <source src="/demo.mp4" type="video/mp4">
+  </video>
+</div>
+
+### Quick Install
+
+1. Install the **starship** binary:
+
+
+   #### Install Latest Version
+
+   With Shell:
+
+   ```sh
+   curl -fsSL https://starship.rs/install.sh | bash
+   ```
+
+
+   #### Install via Package Manager
+
+   With [Homebrew](https://brew.sh/):
+
+   ```sh
+   brew install starship
+   ```
+
+   With [Scoop](https://scoop.sh):
+
+   ```powershell
+   scoop install starship
+   ```
+
+1. Add the init script to your shell's config file:
+
+
+   #### Bash
+
+   Add the following to the end of `~/.bashrc`:
+
+   ```sh
+   # ~/.bashrc
+
+   eval "$(starship init bash)"
+   ```
+
+
+   #### Fish
+
+   Add the following to the end of `~/.config/fish/config.fish`:
+
+   ```sh
+   # ~/.config/fish/config.fish
+
+   starship init fish | source
+   ```
+
+
+   #### Zsh
+
+   Add the following to the end of `~/.zshrc`:
+
+   ```sh
+   # ~/.zshrc
+
+   eval "$(starship init zsh)"
+   ```
+
+
+   #### Powershell
+
+   Add the following to the end of `Microsoft.PowerShell_profile.ps1`. You can check the location of this file by querying the `$PROFILE` variable in PowerShell. Typically the path is `~\Documents\PowerShell\Microsoft.PowerShell_profile.ps1` or `~/.config/powershell/Microsoft.PowerShell_profile.ps1` on -Nix.
+
+   ```sh
+   Invoke-Expression (&starship init powershell)
+   ```
+
+
+   #### Ion
+
+   Add the following to the end of `~/.config/ion/initrc`:
+
+   ```sh
+   # ~/.config/ion/initrc
+
+   eval $(starship init ion)
+   ```
+
+   #### Elvish
+
+   ::: warning Only elvish v0.15 or higher is supported. :::
+
+   Add the following to the end of `~/.elvish/rc.elv`:
+
+   ```sh
+   # ~/.elvish/rc.elv
+
+   eval (starship init elvish)
+   ```
+
+
+   #### Tcsh
+
+   Add the following to the end of `~/.tcshrc`:
+
+   ```sh
+   # ~/.tcshrc
+
+   eval `starship init tcsh`
+   ```
+

docs/ar-SA/advanced-config/README.md

@@ -0,0 +1,93 @@
+# Advanced Configuration
+
+While Starship is a versatile shell, sometimes you need to do more than edit `starship.toml` to get it to do certain things. This page details some of the more advanced configuration techniques used in starship.
+
+::: warning
+
+The configurations in this section are subject to change in future releases of Starship.
+
+:::
+
+## Custom pre-prompt and pre-execution Commands in Bash
+
+Bash does not have a formal preexec/precmd framework like most other shells. Because of this, it is difficult to provide fully customizable hooks in `bash`. However, Starship does give you limited ability to insert your own functions into the prompt-rendering procedure:
+
+- To run a custom function right before the prompt is drawn, define a new function and then assign its name to `starship_precmd_user_func`. For example, to draw a rocket before the prompt, you would do
+
+```bash
+function blastoff(){
+    echo "🚀"
+}
+starship_precmd_user_func="blastoff"
+```
+
+- To run a custom function right before a command runs, you can use the [`DEBUG` trap mechanism](https://jichu4n.com/posts/debug-trap-and-prompt_command-in-bash/). However, you **must** trap the DEBUG signal *before* initializing Starship! Starship can preserve the value of the DEBUG trap, but if the trap is overwritten after starship starts up, some functionality will break.
+
+```bash
+function blastoff(){
+    echo "🚀"
+}
+trap blastoff DEBUG     # Trap DEBUG *before* running starship
+eval $(starship init bash)
+```
+
+## Change Window Title
+
+Some shell prompts will automatically change the window title for you (e.g. to reflect your working directory). Fish even does it by default. Starship does not do this, but it's fairly straightforward to add this functionality to `bash` or `zsh`.
+
+First, define a window title change function (identical in bash and zsh):
+
+```bash
+function set_win_title(){
+    echo -ne "\033]0; YOUR_WINDOW_TITLE_HERE \007"
+}
+```
+
+You can use variables to customize this title (`$USER`, `$HOSTNAME`, and `$PWD` are popular choices).
+
+In `bash`, set this function to be the precmd starship function:
+
+```bash
+starship_precmd_user_func="set_win_title"
+```
+
+In `zsh`, add this to the `precmd_functions` array:
+
+```bash
+precmd_functions+=(set_win_title)
+```
+
+If you like the result, add these lines to your shell configuration file (`~/.bashrc` or `~/.zshrc`) to make it permanent.
+
+For example, if you want to display your current directory in your terminal tab title, add the following snippet to your `~/.bashrc` or `~/.zshrc`:
+
+```bash
+function set_win_title(){
+    echo -ne "\033]0; $(basename $PWD) \007"
+}
+starship_precmd_user_func="set_win_title"
+```
+
+## Style Strings
+
+Style strings are a list of words, separated by whitespace. The words are not case sensitive (i.e. `bold` and `BoLd` are considered the same string). Each word can be one of the following:
+
+  - `bold`
+  - `underline`
+  - `dimmed`
+  - `bg:<color>`
+  - `fg:<color>`
+  - `<color>`
+  - `none`
+
+where `<color>` is a color specifier (discussed below). `fg:<color>` and `<color>` currently do the same thing , though this may change in the future. The order of words in the string does not matter.
+
+The `none` token overrides all other tokens in a string if it is not part of a `bg:` specifier, so that e.g. `fg:red none fg:blue` will still create a string with no styling. `bg:none`  sets the background to the default color so `fg:red bg:none` is equivalent to `red` or `fg:red` and `bg:green fg:red bg:none` is also equivalent to `fg:red` or `red`. It may become an error to use `none` in conjunction with other tokens in the future.
+
+A color specifier can be one of the following:
+
+ - One of the standard terminal colors: `black`, `red`, `green`, `blue`, `yellow`, `purple`, `cyan`, `white`. You can optionally prefix these with `bright-` to get the bright version (e.g. `bright-white`).
+ - A `#` followed by a six-digit hexadecimal number. This specifies an [RGB color hex code](https://www.w3schools.com/colors/colors_hexadecimal.asp).
+ - A number between 0-255. This specifies an [8-bit ANSI Color Code](https://i.stack.imgur.com/KTSQa.png).
+
+If multiple colors are specified for foreground/background, the last one in the string will take priority.

docs/ar-SA/faq/README.md

@@ -0,0 +1,96 @@
+# FAQ
+
+## What is the configuration used in the demo GIF?
+
+- **Terminal Emulator**: [iTerm2](https://iterm2.com/)
+  - **Theme**: Minimal
+  - **Color Scheme**: [Snazzy](https://github.com/sindresorhus/iterm2-snazzy)
+  - **Font**: [FiraCode Nerd Font](https://www.nerdfonts.com/font-downloads)
+- **Shell**: [Fish Shell](https://fishshell.com/)
+  - **Configuration**: [matchai's Dotfiles](https://github.com/matchai/dotfiles/blob/b6c6a701d0af8d145a8370288c00bb9f0648b5c2/.config/fish/config.fish)
+  - **Prompt**: [Starship](https://starship.rs/)
+
+## How do I get command completion as shown in the demo GIF?
+
+Completion support, or autocomplete, is provided by your shell of choice. In the case of the demo, the demo was done with [Fish Shell](https://fishshell.com/), which provides completions by default. If you use Z Shell (zsh), I'd suggest taking a look at [zsh-autosuggestions](https://github.com/zsh-users/zsh-autosuggestions).
+
+## 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. Why isn't my preferred shell supported?
+
+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:
+
+```sh
+# 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](https://github.com/starship/starship/blob/master/src/init/starship.bash) built into Starship is slightly more complex to allow for advanced features like the [Command Duration module](https://starship.rs/config/#command-duration) 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:
+
+```sh
+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`:
+
+```sh
+curl -fsSL https://starship.rs/install.sh | bash -s -- --platform unknown-linux-musl
+```
+
+## I see symbols I don't understand or expect, what do they mean?
+
+If you see symbols that you don't recognise you can use `starship explain` to explain the currently showing modules.
+
+## 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](https://www.tecmint.com/set-system-locales-in-linux/).
+- 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](https://www.google.com/get/noto/help/emoji/) is a popular choice.
+- You are using a [Nerd Font](https://www.nerdfonts.com/).
+
+To test your system, run the following commands in a terminal:
+
+```sh
+echo -e "\xf0\x9f\x90\x8d"
+echo -e "\xee\x82\xa0"
+```
+
+The first line should produce a [snake emoji](https://emojipedia.org/snake/), while the second should produce a [powerline branch symbol (e0a0)](https://github.com/ryanoasis/powerline-extra-symbols#glyphs).
+
+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!](https://github.com/starship/starship/issues/new/choose)
+
+## 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.
+1. 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:
+
+```sh
+# Locate and delete the starship binary
+rm "$(which starship)"
+```

docs/ar-SA/guide/README.md

@@ -0,0 +1,311 @@
+<p align="center">
+  <img
+    width="400"
+    src="https://raw.githubusercontent.com/starship/starship/master/media/logo.png"
+    alt="Starship – Cross-shell prompt"
+ />
+</p>
+
+<p align="center">
+  <a href="https://github.com/starship/starship/actions"
+    ><img
+      src="https://img.shields.io/github/workflow/status/starship/starship/Main workflow/master?label=workflow&style=flat-square"
+      alt="GitHub Actions workflow status"
+ /></a>
+  <a href="https://crates.io/crates/starship"
+    ><img
+      src="https://img.shields.io/crates/v/starship?style=flat-square"
+      alt="Crates.io version"
+ /></a>
+  <a href="https://repology.org/project/starship/versions"
+    ><img
+      src="https://img.shields.io/repology/repositories/starship?label=in%20repositories&style=flat-square"
+      alt="Packaging status" /></a
+><br />
+  <a href="https://discord.gg/starship"
+    ><img
+      src="https://img.shields.io/discord/567163873606500352?label=discord&logoColor=white&style=flat-square"
+      alt="Chat on Discord"
+ /></a>
+  <a href="https://twitter.com/StarshipPrompt"
+    ><img
+      src="https://img.shields.io/badge/twitter-@StarshipPrompt-1DA1F3?style=flat-square"
+      alt="Follow @StarshipPrompt on Twitter"
+ /></a>
+</p>
+
+<p align="center">
+  <a href="https://starship.rs">Website</a>
+  ·
+  <a href="#🚀-installation">Installation</a>
+  ·
+  <a href="https://starship.rs/config/">Configuration</a>
+</p>
+
+<p align="center">
+  <a href="https://github.com/starship/starship/blob/master/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-us.png"
+      alt="English"
+ /></a>
+  &nbsp;
+  <a
+    href="https://github.com/starship/starship/blob/master/docs/ja-JP/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-jp.png"
+      alt="日本語"
+ /></a>
+  &nbsp;
+  <a
+    href="https://github.com/starship/starship/blob/master/docs/zh-TW/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-tw.png"
+      alt="繁體中文"
+ /></a>
+  &nbsp;
+  <a
+    href="https://github.com/starship/starship/blob/master/docs/ru-RU/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-ru.png"
+      alt="Русский"
+ /></a>
+  &nbsp;
+  <a
+    href="https://github.com/starship/starship/blob/master/docs/de-DE/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-de.png"
+      alt="Deutsch"
+ /></a>
+  &nbsp;
+  <a
+    href="https://github.com/starship/starship/blob/master/docs/zh-CN/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-cn.png"
+      alt="简体中文"
+ /></a>
+  &nbsp;
+  <a 
+    href="https://github.com/starship/starship/blob/master/docs/es-ES/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-es.png"
+      alt="Español"
+ /></a>
+  &nbsp;
+  <a 
+    href="https://github.com/starship/starship/blob/master/docs/fr-FR/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-fr.png"
+      alt="Français"
+ /></a>
+  &nbsp;
+  <a 
+    href="https://github.com/starship/starship/blob/master/docs/vi-VN/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-vn.png"
+      alt="Tiếng Việt"
+ /></a>
+</p>
+
+<h1></h1>
+
+<img
+  src="https://raw.githubusercontent.com/starship/starship/master/media/demo.gif"
+  alt="Starship with iTerm2 and the Snazzy theme"
+  width="50%"
+  align="right"
+ />
+
+**The minimal, blazing-fast, and infinitely customizable prompt for any shell!**
+
+- **Fast:** it's fast – _really really_ fast! 🚀
+- **Customizable:** configure every aspect of your prompt.
+- **Universal:** works on any shell, on any operating system.
+- **Intelligent:** shows relevant information at a glance.
+- **Feature rich:** support for all your favorite tools.
+- **Easy:** quick to install – start using it in minutes.
+
+<p align="center">
+<a href="https://starship.rs/config/"><strong>Explore the Starship docs&nbsp;&nbsp;▶</strong></a>
+</p>
+
+<a name="🚀-installation"></a>
+
+## 🚀 Installation
+
+### Prerequisites
+
+- A [Nerd Font](https://www.nerdfonts.com/) installed and enabled in your terminal (for example, try the [Fira Code Nerd Font](https://www.nerdfonts.com/font-downloads)).
+
+### Getting Started
+
+**Note**: due to the proliferation of different platforms, only a subset of supported platforms are shown below. Can't see yours? Have a look at the [extra platform instructions](https://starship.rs/installing/).
+
+1. Install the **starship** binary:
+
+
+   #### Install Latest Version
+
+
+   ##### From prebuilt binary, with Shell:
+
+   ```sh
+   curl -fsSL https://starship.rs/install.sh | bash
+   ```
+
+
+   #### Install via Package Manager
+
+
+   ##### Example: [Homebrew](https://brew.sh/):
+
+   ```sh
+   brew install starship
+   ```
+
+
+   ##### With [Scoop](https://scoop.sh):
+
+   ```powershell
+   scoop install starship
+   ```
+
+2. Add the init script to your shell's config file:
+
+
+   #### Bash
+
+   Add the following to the end of `~/.bashrc`:
+
+   ```sh
+   # ~/.bashrc
+
+   eval "$(starship init bash)"
+   ```
+
+
+   #### Fish
+
+   Add the following to the end of `~/.config/fish/config.fish`:
+
+   ```sh
+   # ~/.config/fish/config.fish
+
+   starship init fish | source
+   ```
+
+
+   #### Zsh
+
+   Add the following to the end of `~/.zshrc`:
+
+   ```sh
+   # ~/.zshrc
+
+   eval "$(starship init zsh)"
+   ```
+
+
+   #### PowerShell
+
+   Add the following to the end of `Microsoft.PowerShell_profile.ps1`. You can check the location of this file by querying the `$PROFILE` variable in PowerShell. Typically the path is `~\Documents\PowerShell\Microsoft.PowerShell_profile.ps1` or `~/.config/powershell/Microsoft.PowerShell_profile.ps1` on -Nix.
+
+   ```powershell
+   Invoke-Expression (&starship init powershell)
+   ```
+
+
+   #### Ion
+
+   Add the following to the end of `~/.config/ion/initrc`:
+
+   ```sh
+   # ~/.config/ion/initrc
+
+   eval $(starship init ion)
+   ```
+
+
+   #### Elvish
+
+   **Warning** Only elvish v0.15 or higher is supported. Add the following to the end of `~/.elvish/rc.elv`:
+
+   ```sh
+   # ~/.elvish/rc.elv
+
+   eval (starship init elvish)
+   ```
+
+
+   #### Tcsh
+
+   Add the following to the end of `~/.tcshrc`:
+
+   ```sh
+   # ~/.tcshrc
+
+   eval `starship init tcsh`
+   ```
+
+## 🤝 Contributing
+
+We are always looking for contributors of **all skill levels**! If you're looking to ease your way into the project, try out a [good first issue](https://github.com/starship/starship/labels/🌱%20good%20first%20issue).
+
+If you are fluent in a non-English language, we greatly appreciate any help keeping our docs translated and up-to-date in other languages. If you would like to help, translations can be contributed on the [Starship Crowdin](https://translate.starship.rs/).
+
+If you are interested in helping contribute to starship, please take a look at our [Contributing Guide](https://github.com/starship/starship/blob/master/CONTRIBUTING.md). Also, feel free to drop into our [Discord server](https://discord.gg/8Jzqu3T) and say hi. 👋
+
+### Code Contributors
+
+This project exists thanks to all the people who contribute. [[Contribute](https://github.com/starship/starship/blob/master/CONTRIBUTING.md)].
+<a href="https://github.com/starship/starship/graphs/contributors"><img src="https://opencollective.com/starship/contributors.svg?width=890&button=false" /></a>
+
+### Financial Contributors
+
+Become a financial contributor and help us sustain our community. [[Contribute](https://opencollective.com/starship/contribute)]
+
+#### Individuals
+
+<a href="https://opencollective.com/starship"><img src="https://opencollective.com/starship/individuals.svg?width=890"></a>
+
+#### Organizations
+
+Support this project with your organization. Your logo will show up here with a link to your website. [[Contribute](https://opencollective.com/starship/contribute)]
+
+<a href="https://opencollective.com/starship/organization/0/website"><img src="https://opencollective.com/starship/organization/0/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/1/website"><img src="https://opencollective.com/starship/organization/1/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/2/website"><img src="https://opencollective.com/starship/organization/2/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/3/website"><img src="https://opencollective.com/starship/organization/3/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/4/website"><img src="https://opencollective.com/starship/organization/4/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/5/website"><img src="https://opencollective.com/starship/organization/5/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/6/website"><img src="https://opencollective.com/starship/organization/6/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/7/website"><img src="https://opencollective.com/starship/organization/7/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/8/website"><img src="https://opencollective.com/starship/organization/8/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/9/website"><img src="https://opencollective.com/starship/organization/9/avatar.svg"></a>
+
+## 💭 Inspired By
+
+Please check out these previous works that helped inspire the creation of starship. 🙏
+
+- **[denysdovhan/spaceship-prompt](https://github.com/denysdovhan/spaceship-prompt)** - A ZSH prompt for astronauts.
+
+- **[denysdovhan/robbyrussell-node](https://github.com/denysdovhan/robbyrussell-node)** - Cross-shell robbyrussell theme written in JavaScript.
+
+- **[reujab/silver](https://github.com/reujab/silver)** - A cross-shell customizable powerline-like prompt with icons.
+
+<p align="center">
+    <br>
+    <img width="100" src="https://raw.githubusercontent.com/starship/starship/master/media/icon.png" alt="Starship rocket icon">
+</p>
+
+## 📝 License
+
+Copyright © 2019-present, [Starship Contributors](https://github.com/starship/starship/graphs/contributors).<br /> This project is [ISC](https://github.com/starship/starship/blob/master/LICENSE) licensed.

docs/ar-SA/installing/README.md

@@ -0,0 +1,84 @@
+# 🚀 Advanced Installation
+
+To install starship, you need to do two things:
+
+1. Get the **starship** binary onto your computer
+1. Tell your shell to use the starship binary as its prompt by modifying its init scripts
+
+For most users, the instructions on [the main page](/guide/#🚀-installation) will work great. However, for some more specialized platforms, different instructions are needed.
+
+There are so many platforms out there that they didn't fit into the main README.md file, so here are some installation instructions for other platforms from the community. Is yours not here? Please do add it here if you figure it out!
+
+## [Chocolatey](https://chocolatey.org)
+
+### Prerequisites
+
+Head over to the [Chocolatey installation page](https://chocolatey.org/install) and follow the instructions to install Chocolatey.
+
+### Installation
+
+```powershell
+choco install starship
+```
+
+## [termux](https://termux.com)
+
+### Prerequisites
+
+```sh
+pkg install getconf
+```
+
+### Installation
+
+```sh
+curl -fsSL https://starship.rs/install.sh | bash -s -- -b /data/data/com.termux/files/usr/bin
+```
+
+## [Nix](https://nixos.wiki/wiki/Nix)
+
+### Getting the Binary
+
+#### Imperatively
+
+```sh
+nix-env -iA nixos.starship
+```
+
+#### Declarative, single user, via [home-manager](home-manager)
+
+Enable the `programs.starship` module in your `home.nix` file, and add your settings
+
+```nix
+{
+  programs.starship = {
+    enable = true;
+    enableZshIntegration = true;
+    # Configuration written to ~/.config/starship.toml
+    settings = {
+      # add_newline = false;
+
+      # character = {
+      #   success_symbol = "[➜](bold green)";
+      #   error_symbol = "[➜](bold red)";
+      # };
+
+      # package.disabled = true;
+    };
+  };
+}
+```
+
+then run
+
+```sh
+home-manager switch
+```
+
+#### Declarative, system-wide, with NixOS
+
+Add `pkgs.starship` to `environment.systemPackages` in your `configuration.nix`, then run
+
+```sh
+sudo nixos-rebuild switch
+```

docs/ar-SA/migrating-to-0.45.0/README.md

@@ -0,0 +1,267 @@
+# Migrating to v0.45.0
+
+Starship v0.45.0 is a release containing breaking changes, in preparation for the big v1.0.0. We have made some major changes around how configuration is done on the prompt, to allow for a greater degree of customization.
+
+This guide is intended to walk you through the breaking changes.
+
+## `prompt_order` has been replaced by a root-level `format`
+
+Previously to v0.45.0, `prompt_order` would accept an array of module names in the order which they should be rendered by Starship.
+
+Starship v0.45.0 instead accepts a `format` value, allowing for customization of the prompt outside of the modules themselves.
+
+**Example pre-v0.45.0 configuration**
+
+```toml
+prompt_order = [
+  "username",
+  "hostname",
+  "directory",
+  "git_branch",
+  "git_commit",
+  "git_state",
+  "git_status",
+  "cmd_duration",
+  "custom",
+  "line_break",
+  "jobs",
+  "battery",
+  "time",
+  "character",
+]
+```
+
+**Example v0.45.0 configuration**
+
+```toml
+format = """\
+  $username\
+  $hostname\
+  $directory\
+  $git_branch\
+  $git_commit\
+  $git_state\
+  $git_status\
+  $cmd_duration\
+  $custom\
+  $line_break\
+  $jobs\
+  $battery\
+  $time\
+  $character\
+  """
+```
+
+## Module `prefix` and `suffix` have been replaced by `format`
+
+Previously to v0.45.0, some modules would accept `prefix` and/or `suffix` in order to stylize the way that modules are rendered.
+
+Starship v0.45.0 instead accepts a `format` value, allowing for further customization of how modules are rendered. Instead of defining a prefix and suffix for the context-based variables, the variables can now be substituted from within a format string, which represents the module's output.
+
+**Example pre-v0.45.0 configuration**
+
+```toml
+[cmd_duration]
+prefix = "took "
+```
+
+**Example v0.45.0 configuration**
+
+```toml
+[cmd_duration]
+# $duration – The command duration (e.g. "15s")
+# $style    – The default style of the module (e.g. "bold yellow")
+format = "took [$duration]($style) "
+```
+
+### Affected Modules
+
+#### Character
+
+| Removed Property        | Replacement      |
+| ----------------------- | ---------------- |
+| `symbol`                | `success_symbol` |
+| `use_symbol_for_status` | `error_symbol`   |
+| `style_success`         | `success_symbol` |
+| `style_failure`         | `error_symbol`   |
+
+**Changes to the Default Configuration**
+
+```diff
+[character]
+-- symbol = "❯"
+-- error_symbol = "✖"
+-- use_symbol_for_status = true
+-- vicmd_symbol = "❮"
+++ success_symbol = "[❯](bold green)"
+++ error_symbol = "[❯](bold red)"
+++ vicmd_symbol = "[❮](bold green)"
+```
+
+Previously, the `use_symbol_for_status` property was used to configure the prompt to show the `error_symbol` when the last command resulted in a non-zero status code.
+
+With the release of v0.45.0, we now always use `error_symbol` after non-zero status codes, unifying `use_symbol_for_status` and `error_symbol` properties.
+
+To configure the prompt to use the older `use_symbol_for_status = true` configuration, add the following to your config file:
+
+```toml
+[character]
+error_symbol = "[✖](bold red)"
+```
+
+*Note:* The `character` element automatically adds a space after, so unlike the other `format` strings, we specifically do not add one in the above examples.
+
+#### Command Duration
+
+| Removed Property | Replacement |
+| ---------------- | ----------- |
+| `prefix`         | `format`    |
+
+**Changes to the Default Configuration**
+
+```diff
+[cmd_duration]
+-- prefix = "took "
+++ format = "took [$duration]($style) "
+```
+
+#### Directory
+
+| Removed Property | Replacement |
+| ---------------- | ----------- |
+| `prefix`         | `format`    |
+
+**Changes to the Default Configuration**
+
+```diff
+[directory]
+-- prefix = "in "
+++ format = "[$path]($style)[$read_only]($read_only_style) "
+```
+
+#### Environment Variable
+
+| Removed Property | Replacement |
+| ---------------- | ----------- |
+| `prefix`         | `format`    |
+| `suffix`         | `format`    |
+
+**Changes to the Default Configuration**
+
+```diff
+[env_var]
+-- prefix = ""
+-- suffix = ""
+++ format = "with [$env_value]($style) "
+```
+
+#### Git Commit
+
+| Removed Property | Replacement |
+| ---------------- | ----------- |
+| `prefix`         | `format`    |
+| `suffix`         | `format`    |
+
+**Changes to the Default Configuration**
+
+```diff
+[git_commit]
+-- prefix = "("
+-- suffix = ")"
+++ format = '[\($hash\)]($style) '
+```
+
+#### Git Status
+
+| Removed Property  | Replacement |
+| ----------------- | ----------- |
+| `prefix`          | `format`    |
+| `suffix`          | `format`    |
+| `show_sync_count` | `format`    |
+
+**Changes to the Default Configuration**
+
+```diff
+[git_status]
+-- prefix = "["
+-- suffix = "]"
+-- show_sync_count = false
+++ format = '([\[$all_status$ahead_behind\]]($style) )'
+```
+
+Previously, the `show_sync_count` property was used to configure the prompt to show the number of commits the branch was ahead or behind the remote branch.
+
+With the release of v0.45.0, this has been replaced with three separate properties, `ahead`, `behind`, and `diverged`.
+
+To configure the prompt to use the older `show_sync_count = true` configuration, set the following to your config file:
+
+```toml
+[git_status]
+ahead = "⇡${count}"
+diverged = "⇕⇡${ahead_count}⇣${behind_count}"
+behind = "⇣${count}"
+```
+
+#### Hostname
+
+| Removed Property | Replacement |
+| ---------------- | ----------- |
+| `prefix`         | `format`    |
+| `suffix`         | `format`    |
+
+**Changes to the Default Configuration**
+
+```diff
+[hostname]
+-- prefix = ""
+-- suffix = ""
+++ format = "[$hostname]($style) in "
+```
+
+#### Singularity
+
+| Removed Property | Replacement |
+| ---------------- | ----------- |
+| `label`          | `format`    |
+| `prefix`         | `format`    |
+| `suffix`         | `format`    |
+
+**Changes to the Default Configuration**
+
+```diff
+[singularity]
+-- prefix = ""
+-- suffix = ""
+++ format = '[$symbol\[$env\]]($style) '
+```
+
+#### Time
+
+| Removed Property | Replacement   |
+| ---------------- | ------------- |
+| `format`         | `time_format` |
+
+**Changes to the Default Configuration**
+
+```diff
+[time]
+-- format = "🕙[ %T ]"
+++ time_format = "%T"
+++ format = "at 🕙[$time]($style) "
+```
+
+#### Custom Commands
+
+| Removed Property | Replacement |
+| ---------------- | ----------- |
+| `prefix`         | `format`    |
+| `suffix`         | `format`    |
+
+**Changes to the Default Configuration**
+
+```diff
+[custom.example]
+-- prefix = ""
+-- suffix = ""
+++ format = "[$symbol$output]($style) "
+```

docs/ar-SA/presets/README.md

@@ -0,0 +1,92 @@
+# Presets
+
+Here is a collection of community-submitted configuration presets for Starship. If you have a preset to share, please [submit a PR](https://github.com/starship/starship/edit/master/docs/presets/README.md) updating this file! 😊
+
+## Nerd Font Symbols
+
+This preset doesn't change anything except for the symbols used for each module. If emojis aren't your thing, this might catch your eye!
+
+![Screenshot of Nerd Font Symbols preset](/presets/nerd-font-symbols.png)
+
+### Prerequisites
+
+- A [Nerd Font](https://www.nerdfonts.com/) installed and enabled in your terminal (the example uses Fira Code Nerd Font)
+
+### Configuration
+
+```toml
+[aws]
+symbol = "  "
+
+[conda]
+symbol = " "
+
+[dart]
+symbol = " "
+
+[directory]
+read_only = " "
+
+[docker]
+symbol = " "
+
+[elixir]
+symbol = " "
+
+[elm]
+symbol = " "
+
+[git_branch]
+symbol = " "
+
+[golang]
+symbol = " "
+
+[haskell]
+symbol = " "
+
+[hg_branch]
+symbol = " "
+
+[java]
+symbol = " "
+
+[julia]
+symbol = " "
+
+[memory_usage]
+symbol = " "
+
+[nim]
+symbol = " "
+
+[nix_shell]
+symbol = " "
+
+[nodejs]
+symbol = " "
+
+[package]
+symbol = " "
+
+[perl]
+symbol = " "
+
+[php]
+symbol = " "
+
+[python]
+symbol = " "
+
+[ruby]
+symbol = " "
+
+[rust]
+symbol = " "
+
+[scala]
+symbol = " "
+
+[swift]
+symbol = "ﯣ "
+```

docs/ckb-IR/README.md

@@ -0,0 +1,136 @@
+---
+home: true
+heroImage: /logo.svg
+heroText:
+tagline: The minimal, blazing-fast, and infinitely customizable prompt for any shell!
+actionText: Get Started →
+actionLink: ./guide/
+features:
+  - 
+    title: Compatibility First
+    details: Works on the most common shells on the most common operating systems. Use it everywhere!
+  - 
+    title: Rust-Powered
+    details: Brings the best-in-class speed and safety of Rust, to make your prompt as quick and reliable as possible.
+  - 
+    title: Customizable
+    details: Every little detail is customizable to your liking, to make this prompt as minimal or feature-rich as you'd like it to be.
+footer: ISC Licensed | Copyright © 2019-present Starship Contributors
+#Used for the description meta tag, for SEO
+metaTitle: "Starship: Cross-Shell Prompt"
+description: Starship is the minimal, blazing fast, and extremely customizable prompt for any shell! Shows the information you need, while staying sleek and minimal. Quick installation available for Bash, Fish, ZSH, Ion, and PowerShell.
+---
+
+<div class="center">
+  <video class="demo-video" muted autoplay loop playsinline>
+    <source src="/demo.webm" type="video/webm">
+    <source src="/demo.mp4" type="video/mp4">
+  </video>
+</div>
+
+### Quick Install
+
+1. Install the **starship** binary:
+
+
+   #### Install Latest Version
+
+   With Shell:
+
+   ```sh
+   curl -fsSL https://starship.rs/install.sh | bash
+   ```
+
+
+   #### Install via Package Manager
+
+   With [Homebrew](https://brew.sh/):
+
+   ```sh
+   brew install starship
+   ```
+
+   With [Scoop](https://scoop.sh):
+
+   ```powershell
+   scoop install starship
+   ```
+
+1. Add the init script to your shell's config file:
+
+
+   #### Bash
+
+   Add the following to the end of `~/.bashrc`:
+
+   ```sh
+   # ~/.bashrc
+
+   eval "$(starship init bash)"
+   ```
+
+
+   #### Fish
+
+   Add the following to the end of `~/.config/fish/config.fish`:
+
+   ```sh
+   # ~/.config/fish/config.fish
+
+   starship init fish | source
+   ```
+
+
+   #### Zsh
+
+   Add the following to the end of `~/.zshrc`:
+
+   ```sh
+   # ~/.zshrc
+
+   eval "$(starship init zsh)"
+   ```
+
+
+   #### Powershell
+
+   Add the following to the end of `Microsoft.PowerShell_profile.ps1`. You can check the location of this file by querying the `$PROFILE` variable in PowerShell. Typically the path is `~\Documents\PowerShell\Microsoft.PowerShell_profile.ps1` or `~/.config/powershell/Microsoft.PowerShell_profile.ps1` on -Nix.
+
+   ```sh
+   Invoke-Expression (&starship init powershell)
+   ```
+
+
+   #### Ion
+
+   Add the following to the end of `~/.config/ion/initrc`:
+
+   ```sh
+   # ~/.config/ion/initrc
+
+   eval $(starship init ion)
+   ```
+
+   #### Elvish
+
+   ::: warning Only elvish v0.15 or higher is supported. :::
+
+   Add the following to the end of `~/.elvish/rc.elv`:
+
+   ```sh
+   # ~/.elvish/rc.elv
+
+   eval (starship init elvish)
+   ```
+
+
+   #### Tcsh
+
+   Add the following to the end of `~/.tcshrc`:
+
+   ```sh
+   # ~/.tcshrc
+
+   eval `starship init tcsh`
+   ```
+

docs/ckb-IR/advanced-config/README.md

@@ -0,0 +1,93 @@
+# Advanced Configuration
+
+While Starship is a versatile shell, sometimes you need to do more than edit `starship.toml` to get it to do certain things. This page details some of the more advanced configuration techniques used in starship.
+
+::: warning
+
+The configurations in this section are subject to change in future releases of Starship.
+
+:::
+
+## Custom pre-prompt and pre-execution Commands in Bash
+
+Bash does not have a formal preexec/precmd framework like most other shells. Because of this, it is difficult to provide fully customizable hooks in `bash`. However, Starship does give you limited ability to insert your own functions into the prompt-rendering procedure:
+
+- To run a custom function right before the prompt is drawn, define a new function and then assign its name to `starship_precmd_user_func`. For example, to draw a rocket before the prompt, you would do
+
+```bash
+function blastoff(){
+    echo "🚀"
+}
+starship_precmd_user_func="blastoff"
+```
+
+- To run a custom function right before a command runs, you can use the [`DEBUG` trap mechanism](https://jichu4n.com/posts/debug-trap-and-prompt_command-in-bash/). However, you **must** trap the DEBUG signal *before* initializing Starship! Starship can preserve the value of the DEBUG trap, but if the trap is overwritten after starship starts up, some functionality will break.
+
+```bash
+function blastoff(){
+    echo "🚀"
+}
+trap blastoff DEBUG     # Trap DEBUG *before* running starship
+eval $(starship init bash)
+```
+
+## Change Window Title
+
+Some shell prompts will automatically change the window title for you (e.g. to reflect your working directory). Fish even does it by default. Starship does not do this, but it's fairly straightforward to add this functionality to `bash` or `zsh`.
+
+First, define a window title change function (identical in bash and zsh):
+
+```bash
+function set_win_title(){
+    echo -ne "\033]0; YOUR_WINDOW_TITLE_HERE \007"
+}
+```
+
+You can use variables to customize this title (`$USER`, `$HOSTNAME`, and `$PWD` are popular choices).
+
+In `bash`, set this function to be the precmd starship function:
+
+```bash
+starship_precmd_user_func="set_win_title"
+```
+
+In `zsh`, add this to the `precmd_functions` array:
+
+```bash
+precmd_functions+=(set_win_title)
+```
+
+If you like the result, add these lines to your shell configuration file (`~/.bashrc` or `~/.zshrc`) to make it permanent.
+
+For example, if you want to display your current directory in your terminal tab title, add the following snippet to your `~/.bashrc` or `~/.zshrc`:
+
+```bash
+function set_win_title(){
+    echo -ne "\033]0; $(basename $PWD) \007"
+}
+starship_precmd_user_func="set_win_title"
+```
+
+## Style Strings
+
+Style strings are a list of words, separated by whitespace. The words are not case sensitive (i.e. `bold` and `BoLd` are considered the same string). Each word can be one of the following:
+
+  - `bold`
+  - `underline`
+  - `dimmed`
+  - `bg:<color>`
+  - `fg:<color>`
+  - `<color>`
+  - `none`
+
+where `<color>` is a color specifier (discussed below). `fg:<color>` and `<color>` currently do the same thing , though this may change in the future. The order of words in the string does not matter.
+
+The `none` token overrides all other tokens in a string if it is not part of a `bg:` specifier, so that e.g. `fg:red none fg:blue` will still create a string with no styling. `bg:none`  sets the background to the default color so `fg:red bg:none` is equivalent to `red` or `fg:red` and `bg:green fg:red bg:none` is also equivalent to `fg:red` or `red`. It may become an error to use `none` in conjunction with other tokens in the future.
+
+A color specifier can be one of the following:
+
+ - One of the standard terminal colors: `black`, `red`, `green`, `blue`, `yellow`, `purple`, `cyan`, `white`. You can optionally prefix these with `bright-` to get the bright version (e.g. `bright-white`).
+ - A `#` followed by a six-digit hexadecimal number. This specifies an [RGB color hex code](https://www.w3schools.com/colors/colors_hexadecimal.asp).
+ - A number between 0-255. This specifies an [8-bit ANSI Color Code](https://i.stack.imgur.com/KTSQa.png).
+
+If multiple colors are specified for foreground/background, the last one in the string will take priority.

docs/ckb-IR/faq/README.md

@@ -0,0 +1,96 @@
+# FAQ
+
+## What is the configuration used in the demo GIF?
+
+- **Terminal Emulator**: [iTerm2](https://iterm2.com/)
+  - **Theme**: Minimal
+  - **Color Scheme**: [Snazzy](https://github.com/sindresorhus/iterm2-snazzy)
+  - **Font**: [FiraCode Nerd Font](https://www.nerdfonts.com/font-downloads)
+- **Shell**: [Fish Shell](https://fishshell.com/)
+  - **Configuration**: [matchai's Dotfiles](https://github.com/matchai/dotfiles/blob/b6c6a701d0af8d145a8370288c00bb9f0648b5c2/.config/fish/config.fish)
+  - **Prompt**: [Starship](https://starship.rs/)
+
+## How do I get command completion as shown in the demo GIF?
+
+Completion support, or autocomplete, is provided by your shell of choice. In the case of the demo, the demo was done with [Fish Shell](https://fishshell.com/), which provides completions by default. If you use Z Shell (zsh), I'd suggest taking a look at [zsh-autosuggestions](https://github.com/zsh-users/zsh-autosuggestions).
+
+## 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. Why isn't my preferred shell supported?
+
+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:
+
+```sh
+# 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](https://github.com/starship/starship/blob/master/src/init/starship.bash) built into Starship is slightly more complex to allow for advanced features like the [Command Duration module](https://starship.rs/config/#command-duration) 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:
+
+```sh
+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`:
+
+```sh
+curl -fsSL https://starship.rs/install.sh | bash -s -- --platform unknown-linux-musl
+```
+
+## I see symbols I don't understand or expect, what do they mean?
+
+If you see symbols that you don't recognise you can use `starship explain` to explain the currently showing modules.
+
+## 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](https://www.tecmint.com/set-system-locales-in-linux/).
+- 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](https://www.google.com/get/noto/help/emoji/) is a popular choice.
+- You are using a [Nerd Font](https://www.nerdfonts.com/).
+
+To test your system, run the following commands in a terminal:
+
+```sh
+echo -e "\xf0\x9f\x90\x8d"
+echo -e "\xee\x82\xa0"
+```
+
+The first line should produce a [snake emoji](https://emojipedia.org/snake/), while the second should produce a [powerline branch symbol (e0a0)](https://github.com/ryanoasis/powerline-extra-symbols#glyphs).
+
+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!](https://github.com/starship/starship/issues/new/choose)
+
+## 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.
+1. 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:
+
+```sh
+# Locate and delete the starship binary
+rm "$(which starship)"
+```

docs/ckb-IR/guide/README.md

@@ -0,0 +1,311 @@
+<p align="center">
+  <img
+    width="400"
+    src="https://raw.githubusercontent.com/starship/starship/master/media/logo.png"
+    alt="Starship – Cross-shell prompt"
+ />
+</p>
+
+<p align="center">
+  <a href="https://github.com/starship/starship/actions"
+    ><img
+      src="https://img.shields.io/github/workflow/status/starship/starship/Main workflow/master?label=workflow&style=flat-square"
+      alt="GitHub Actions workflow status"
+ /></a>
+  <a href="https://crates.io/crates/starship"
+    ><img
+      src="https://img.shields.io/crates/v/starship?style=flat-square"
+      alt="Crates.io version"
+ /></a>
+  <a href="https://repology.org/project/starship/versions"
+    ><img
+      src="https://img.shields.io/repology/repositories/starship?label=in%20repositories&style=flat-square"
+      alt="Packaging status" /></a
+><br />
+  <a href="https://discord.gg/starship"
+    ><img
+      src="https://img.shields.io/discord/567163873606500352?label=discord&logoColor=white&style=flat-square"
+      alt="Chat on Discord"
+ /></a>
+  <a href="https://twitter.com/StarshipPrompt"
+    ><img
+      src="https://img.shields.io/badge/twitter-@StarshipPrompt-1DA1F3?style=flat-square"
+      alt="Follow @StarshipPrompt on Twitter"
+ /></a>
+</p>
+
+<p align="center">
+  <a href="https://starship.rs">Website</a>
+  ·
+  <a href="#🚀-installation">Installation</a>
+  ·
+  <a href="https://starship.rs/config/">Configuration</a>
+</p>
+
+<p align="center">
+  <a href="https://github.com/starship/starship/blob/master/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-us.png"
+      alt="English"
+ /></a>
+  &nbsp;
+  <a
+    href="https://github.com/starship/starship/blob/master/docs/ja-JP/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-jp.png"
+      alt="日本語"
+ /></a>
+  &nbsp;
+  <a
+    href="https://github.com/starship/starship/blob/master/docs/zh-TW/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-tw.png"
+      alt="繁體中文"
+ /></a>
+  &nbsp;
+  <a
+    href="https://github.com/starship/starship/blob/master/docs/ru-RU/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-ru.png"
+      alt="Русский"
+ /></a>
+  &nbsp;
+  <a
+    href="https://github.com/starship/starship/blob/master/docs/de-DE/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-de.png"
+      alt="Deutsch"
+ /></a>
+  &nbsp;
+  <a
+    href="https://github.com/starship/starship/blob/master/docs/zh-CN/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-cn.png"
+      alt="简体中文"
+ /></a>
+  &nbsp;
+  <a 
+    href="https://github.com/starship/starship/blob/master/docs/es-ES/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-es.png"
+      alt="Español"
+ /></a>
+  &nbsp;
+  <a 
+    href="https://github.com/starship/starship/blob/master/docs/fr-FR/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-fr.png"
+      alt="Français"
+ /></a>
+  &nbsp;
+  <a 
+    href="https://github.com/starship/starship/blob/master/docs/vi-VN/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-vn.png"
+      alt="Tiếng Việt"
+ /></a>
+</p>
+
+<h1></h1>
+
+<img
+  src="https://raw.githubusercontent.com/starship/starship/master/media/demo.gif"
+  alt="Starship with iTerm2 and the Snazzy theme"
+  width="50%"
+  align="right"
+ />
+
+**The minimal, blazing-fast, and infinitely customizable prompt for any shell!**
+
+- **Fast:** it's fast – _really really_ fast! 🚀
+- **Customizable:** configure every aspect of your prompt.
+- **Universal:** works on any shell, on any operating system.
+- **Intelligent:** shows relevant information at a glance.
+- **Feature rich:** support for all your favorite tools.
+- **Easy:** quick to install – start using it in minutes.
+
+<p align="center">
+<a href="https://starship.rs/config/"><strong>Explore the Starship docs&nbsp;&nbsp;▶</strong></a>
+</p>
+
+<a name="🚀-installation"></a>
+
+## 🚀 Installation
+
+### Prerequisites
+
+- A [Nerd Font](https://www.nerdfonts.com/) installed and enabled in your terminal (for example, try the [Fira Code Nerd Font](https://www.nerdfonts.com/font-downloads)).
+
+### Getting Started
+
+**Note**: due to the proliferation of different platforms, only a subset of supported platforms are shown below. Can't see yours? Have a look at the [extra platform instructions](https://starship.rs/installing/).
+
+1. Install the **starship** binary:
+
+
+   #### Install Latest Version
+
+
+   ##### From prebuilt binary, with Shell:
+
+   ```sh
+   curl -fsSL https://starship.rs/install.sh | bash
+   ```
+
+
+   #### Install via Package Manager
+
+
+   ##### Example: [Homebrew](https://brew.sh/):
+
+   ```sh
+   brew install starship
+   ```
+
+
+   ##### With [Scoop](https://scoop.sh):
+
+   ```powershell
+   scoop install starship
+   ```
+
+2. Add the init script to your shell's config file:
+
+
+   #### Bash
+
+   Add the following to the end of `~/.bashrc`:
+
+   ```sh
+   # ~/.bashrc
+
+   eval "$(starship init bash)"
+   ```
+
+
+   #### Fish
+
+   Add the following to the end of `~/.config/fish/config.fish`:
+
+   ```sh
+   # ~/.config/fish/config.fish
+
+   starship init fish | source
+   ```
+
+
+   #### Zsh
+
+   Add the following to the end of `~/.zshrc`:
+
+   ```sh
+   # ~/.zshrc
+
+   eval "$(starship init zsh)"
+   ```
+
+
+   #### PowerShell
+
+   Add the following to the end of `Microsoft.PowerShell_profile.ps1`. You can check the location of this file by querying the `$PROFILE` variable in PowerShell. Typically the path is `~\Documents\PowerShell\Microsoft.PowerShell_profile.ps1` or `~/.config/powershell/Microsoft.PowerShell_profile.ps1` on -Nix.
+
+   ```powershell
+   Invoke-Expression (&starship init powershell)
+   ```
+
+
+   #### Ion
+
+   Add the following to the end of `~/.config/ion/initrc`:
+
+   ```sh
+   # ~/.config/ion/initrc
+
+   eval $(starship init ion)
+   ```
+
+
+   #### Elvish
+
+   **Warning** Only elvish v0.15 or higher is supported. Add the following to the end of `~/.elvish/rc.elv`:
+
+   ```sh
+   # ~/.elvish/rc.elv
+
+   eval (starship init elvish)
+   ```
+
+
+   #### Tcsh
+
+   Add the following to the end of `~/.tcshrc`:
+
+   ```sh
+   # ~/.tcshrc
+
+   eval `starship init tcsh`
+   ```
+
+## 🤝 Contributing
+
+We are always looking for contributors of **all skill levels**! If you're looking to ease your way into the project, try out a [good first issue](https://github.com/starship/starship/labels/🌱%20good%20first%20issue).
+
+If you are fluent in a non-English language, we greatly appreciate any help keeping our docs translated and up-to-date in other languages. If you would like to help, translations can be contributed on the [Starship Crowdin](https://translate.starship.rs/).
+
+If you are interested in helping contribute to starship, please take a look at our [Contributing Guide](https://github.com/starship/starship/blob/master/CONTRIBUTING.md). Also, feel free to drop into our [Discord server](https://discord.gg/8Jzqu3T) and say hi. 👋
+
+### Code Contributors
+
+This project exists thanks to all the people who contribute. [[Contribute](https://github.com/starship/starship/blob/master/CONTRIBUTING.md)].
+<a href="https://github.com/starship/starship/graphs/contributors"><img src="https://opencollective.com/starship/contributors.svg?width=890&button=false" /></a>
+
+### Financial Contributors
+
+Become a financial contributor and help us sustain our community. [[Contribute](https://opencollective.com/starship/contribute)]
+
+#### Individuals
+
+<a href="https://opencollective.com/starship"><img src="https://opencollective.com/starship/individuals.svg?width=890"></a>
+
+#### Organizations
+
+Support this project with your organization. Your logo will show up here with a link to your website. [[Contribute](https://opencollective.com/starship/contribute)]
+
+<a href="https://opencollective.com/starship/organization/0/website"><img src="https://opencollective.com/starship/organization/0/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/1/website"><img src="https://opencollective.com/starship/organization/1/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/2/website"><img src="https://opencollective.com/starship/organization/2/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/3/website"><img src="https://opencollective.com/starship/organization/3/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/4/website"><img src="https://opencollective.com/starship/organization/4/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/5/website"><img src="https://opencollective.com/starship/organization/5/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/6/website"><img src="https://opencollective.com/starship/organization/6/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/7/website"><img src="https://opencollective.com/starship/organization/7/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/8/website"><img src="https://opencollective.com/starship/organization/8/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/9/website"><img src="https://opencollective.com/starship/organization/9/avatar.svg"></a>
+
+## 💭 Inspired By
+
+Please check out these previous works that helped inspire the creation of starship. 🙏
+
+- **[denysdovhan/spaceship-prompt](https://github.com/denysdovhan/spaceship-prompt)** - A ZSH prompt for astronauts.
+
+- **[denysdovhan/robbyrussell-node](https://github.com/denysdovhan/robbyrussell-node)** - Cross-shell robbyrussell theme written in JavaScript.
+
+- **[reujab/silver](https://github.com/reujab/silver)** - A cross-shell customizable powerline-like prompt with icons.
+
+<p align="center">
+    <br>
+    <img width="100" src="https://raw.githubusercontent.com/starship/starship/master/media/icon.png" alt="Starship rocket icon">
+</p>
+
+## 📝 License
+
+Copyright © 2019-present, [Starship Contributors](https://github.com/starship/starship/graphs/contributors).<br /> This project is [ISC](https://github.com/starship/starship/blob/master/LICENSE) licensed.

docs/ckb-IR/installing/README.md

@@ -0,0 +1,84 @@
+# 🚀 Advanced Installation
+
+To install starship, you need to do two things:
+
+1. Get the **starship** binary onto your computer
+1. Tell your shell to use the starship binary as its prompt by modifying its init scripts
+
+For most users, the instructions on [the main page](/guide/#🚀-installation) will work great. However, for some more specialized platforms, different instructions are needed.
+
+There are so many platforms out there that they didn't fit into the main README.md file, so here are some installation instructions for other platforms from the community. Is yours not here? Please do add it here if you figure it out!
+
+## [Chocolatey](https://chocolatey.org)
+
+### Prerequisites
+
+Head over to the [Chocolatey installation page](https://chocolatey.org/install) and follow the instructions to install Chocolatey.
+
+### Installation
+
+```powershell
+choco install starship
+```
+
+## [termux](https://termux.com)
+
+### Prerequisites
+
+```sh
+pkg install getconf
+```
+
+### Installation
+
+```sh
+curl -fsSL https://starship.rs/install.sh | bash -s -- -b /data/data/com.termux/files/usr/bin
+```
+
+## [Nix](https://nixos.wiki/wiki/Nix)
+
+### Getting the Binary
+
+#### Imperatively
+
+```sh
+nix-env -iA nixos.starship
+```
+
+#### Declarative, single user, via [home-manager](home-manager)
+
+Enable the `programs.starship` module in your `home.nix` file, and add your settings
+
+```nix
+{
+  programs.starship = {
+    enable = true;
+    enableZshIntegration = true;
+    # Configuration written to ~/.config/starship.toml
+    settings = {
+      # add_newline = false;
+
+      # character = {
+      #   success_symbol = "[➜](bold green)";
+      #   error_symbol = "[➜](bold red)";
+      # };
+
+      # package.disabled = true;
+    };
+  };
+}
+```
+
+then run
+
+```sh
+home-manager switch
+```
+
+#### Declarative, system-wide, with NixOS
+
+Add `pkgs.starship` to `environment.systemPackages` in your `configuration.nix`, then run
+
+```sh
+sudo nixos-rebuild switch
+```

docs/ckb-IR/migrating-to-0.45.0/README.md

@@ -0,0 +1,267 @@
+# Migrating to v0.45.0
+
+Starship v0.45.0 is a release containing breaking changes, in preparation for the big v1.0.0. We have made some major changes around how configuration is done on the prompt, to allow for a greater degree of customization.
+
+This guide is intended to walk you through the breaking changes.
+
+## `prompt_order` has been replaced by a root-level `format`
+
+Previously to v0.45.0, `prompt_order` would accept an array of module names in the order which they should be rendered by Starship.
+
+Starship v0.45.0 instead accepts a `format` value, allowing for customization of the prompt outside of the modules themselves.
+
+**Example pre-v0.45.0 configuration**
+
+```toml
+prompt_order = [
+  "username",
+  "hostname",
+  "directory",
+  "git_branch",
+  "git_commit",
+  "git_state",
+  "git_status",
+  "cmd_duration",
+  "custom",
+  "line_break",
+  "jobs",
+  "battery",
+  "time",
+  "character",
+]
+```
+
+**Example v0.45.0 configuration**
+
+```toml
+format = """\
+  $username\
+  $hostname\
+  $directory\
+  $git_branch\
+  $git_commit\
+  $git_state\
+  $git_status\
+  $cmd_duration\
+  $custom\
+  $line_break\
+  $jobs\
+  $battery\
+  $time\
+  $character\
+  """
+```
+
+## Module `prefix` and `suffix` have been replaced by `format`
+
+Previously to v0.45.0, some modules would accept `prefix` and/or `suffix` in order to stylize the way that modules are rendered.
+
+Starship v0.45.0 instead accepts a `format` value, allowing for further customization of how modules are rendered. Instead of defining a prefix and suffix for the context-based variables, the variables can now be substituted from within a format string, which represents the module's output.
+
+**Example pre-v0.45.0 configuration**
+
+```toml
+[cmd_duration]
+prefix = "took "
+```
+
+**Example v0.45.0 configuration**
+
+```toml
+[cmd_duration]
+# $duration – The command duration (e.g. "15s")
+# $style    – The default style of the module (e.g. "bold yellow")
+format = "took [$duration]($style) "
+```
+
+### Affected Modules
+
+#### Character
+
+| Removed Property        | Replacement      |
+| ----------------------- | ---------------- |
+| `symbol`                | `success_symbol` |
+| `use_symbol_for_status` | `error_symbol`   |
+| `style_success`         | `success_symbol` |
+| `style_failure`         | `error_symbol`   |
+
+**Changes to the Default Configuration**
+
+```diff
+[character]
+-- symbol = "❯"
+-- error_symbol = "✖"
+-- use_symbol_for_status = true
+-- vicmd_symbol = "❮"
+++ success_symbol = "[❯](bold green)"
+++ error_symbol = "[❯](bold red)"
+++ vicmd_symbol = "[❮](bold green)"
+```
+
+Previously, the `use_symbol_for_status` property was used to configure the prompt to show the `error_symbol` when the last command resulted in a non-zero status code.
+
+With the release of v0.45.0, we now always use `error_symbol` after non-zero status codes, unifying `use_symbol_for_status` and `error_symbol` properties.
+
+To configure the prompt to use the older `use_symbol_for_status = true` configuration, add the following to your config file:
+
+```toml
+[character]
+error_symbol = "[✖](bold red)"
+```
+
+*Note:* The `character` element automatically adds a space after, so unlike the other `format` strings, we specifically do not add one in the above examples.
+
+#### Command Duration
+
+| Removed Property | Replacement |
+| ---------------- | ----------- |
+| `prefix`         | `format`    |
+
+**Changes to the Default Configuration**
+
+```diff
+[cmd_duration]
+-- prefix = "took "
+++ format = "took [$duration]($style) "
+```
+
+#### Directory
+
+| Removed Property | Replacement |
+| ---------------- | ----------- |
+| `prefix`         | `format`    |
+
+**Changes to the Default Configuration**
+
+```diff
+[directory]
+-- prefix = "in "
+++ format = "[$path]($style)[$read_only]($read_only_style) "
+```
+
+#### Environment Variable
+
+| Removed Property | Replacement |
+| ---------------- | ----------- |
+| `prefix`         | `format`    |
+| `suffix`         | `format`    |
+
+**Changes to the Default Configuration**
+
+```diff
+[env_var]
+-- prefix = ""
+-- suffix = ""
+++ format = "with [$env_value]($style) "
+```
+
+#### Git Commit
+
+| Removed Property | Replacement |
+| ---------------- | ----------- |
+| `prefix`         | `format`    |
+| `suffix`         | `format`    |
+
+**Changes to the Default Configuration**
+
+```diff
+[git_commit]
+-- prefix = "("
+-- suffix = ")"
+++ format = '[\($hash\)]($style) '
+```
+
+#### Git Status
+
+| Removed Property  | Replacement |
+| ----------------- | ----------- |
+| `prefix`          | `format`    |
+| `suffix`          | `format`    |
+| `show_sync_count` | `format`    |
+
+**Changes to the Default Configuration**
+
+```diff
+[git_status]
+-- prefix = "["
+-- suffix = "]"
+-- show_sync_count = false
+++ format = '([\[$all_status$ahead_behind\]]($style) )'
+```
+
+Previously, the `show_sync_count` property was used to configure the prompt to show the number of commits the branch was ahead or behind the remote branch.
+
+With the release of v0.45.0, this has been replaced with three separate properties, `ahead`, `behind`, and `diverged`.
+
+To configure the prompt to use the older `show_sync_count = true` configuration, set the following to your config file:
+
+```toml
+[git_status]
+ahead = "⇡${count}"
+diverged = "⇕⇡${ahead_count}⇣${behind_count}"
+behind = "⇣${count}"
+```
+
+#### Hostname
+
+| Removed Property | Replacement |
+| ---------------- | ----------- |
+| `prefix`         | `format`    |
+| `suffix`         | `format`    |
+
+**Changes to the Default Configuration**
+
+```diff
+[hostname]
+-- prefix = ""
+-- suffix = ""
+++ format = "[$hostname]($style) in "
+```
+
+#### Singularity
+
+| Removed Property | Replacement |
+| ---------------- | ----------- |
+| `label`          | `format`    |
+| `prefix`         | `format`    |
+| `suffix`         | `format`    |
+
+**Changes to the Default Configuration**
+
+```diff
+[singularity]
+-- prefix = ""
+-- suffix = ""
+++ format = '[$symbol\[$env\]]($style) '
+```
+
+#### Time
+
+| Removed Property | Replacement   |
+| ---------------- | ------------- |
+| `format`         | `time_format` |
+
+**Changes to the Default Configuration**
+
+```diff
+[time]
+-- format = "🕙[ %T ]"
+++ time_format = "%T"
+++ format = "at 🕙[$time]($style) "
+```
+
+#### Custom Commands
+
+| Removed Property | Replacement |
+| ---------------- | ----------- |
+| `prefix`         | `format`    |
+| `suffix`         | `format`    |
+
+**Changes to the Default Configuration**
+
+```diff
+[custom.example]
+-- prefix = ""
+-- suffix = ""
+++ format = "[$symbol$output]($style) "
+```

docs/ckb-IR/presets/README.md

@@ -0,0 +1,92 @@
+# Presets
+
+Here is a collection of community-submitted configuration presets for Starship. If you have a preset to share, please [submit a PR](https://github.com/starship/starship/edit/master/docs/presets/README.md) updating this file! 😊
+
+## Nerd Font Symbols
+
+This preset doesn't change anything except for the symbols used for each module. If emojis aren't your thing, this might catch your eye!
+
+![Screenshot of Nerd Font Symbols preset](/presets/nerd-font-symbols.png)
+
+### Prerequisites
+
+- A [Nerd Font](https://www.nerdfonts.com/) installed and enabled in your terminal (the example uses Fira Code Nerd Font)
+
+### Configuration
+
+```toml
+[aws]
+symbol = "  "
+
+[conda]
+symbol = " "
+
+[dart]
+symbol = " "
+
+[directory]
+read_only = " "
+
+[docker]
+symbol = " "
+
+[elixir]
+symbol = " "
+
+[elm]
+symbol = " "
+
+[git_branch]
+symbol = " "
+
+[golang]
+symbol = " "
+
+[haskell]
+symbol = " "
+
+[hg_branch]
+symbol = " "
+
+[java]
+symbol = " "
+
+[julia]
+symbol = " "
+
+[memory_usage]
+symbol = " "
+
+[nim]
+symbol = " "
+
+[nix_shell]
+symbol = " "
+
+[nodejs]
+symbol = " "
+
+[package]
+symbol = " "
+
+[perl]
+symbol = " "
+
+[php]
+symbol = " "
+
+[python]
+symbol = " "
+
+[ruby]
+symbol = " "
+
+[rust]
+symbol = " "
+
+[scala]
+symbol = " "
+
+[swift]
+symbol = "ﯣ "
+```

docs/config/README.md

@@ -9,8 +9,8 @@ mkdir -p ~/.config && touch ~/.config/starship.toml
 All configuration for starship is done in this [TOML](https://github.com/toml-lang/toml) file:
 
 ```toml
-# Don't print a new line at the start of the prompt
-add_newline = false
+# Inserts a blank line between shell prompts
+add_newline = true
 
 # Replace the "❯" symbol in the prompt with "➜"
 [character]                            # The name of the module we are configuring is "character"
@@ -21,16 +21,16 @@ success_symbol = "[➜](bold green)"     # The "success_symbol" segment is being
 disabled = true
 ```
 
-You can change default `starship.toml` file location with `STARSHIP_CONFIG` environment variable:
+You can change default configuration file location with `STARSHIP_CONFIG` environment variable:
 
 ```sh
-export STARSHIP_CONFIG=~/.starship
+export STARSHIP_CONFIG=~/.starship/config.toml
 ```
 
 Equivalently in PowerShell (Windows) would be adding this line to your `$PROFILE`:
 
-```ps1
-$ENV:STARSHIP_CONFIG = "$HOME\.starship"
+```powershell
+$ENV:STARSHIP_CONFIG = "$HOME\.starship\config.toml"
 ```
 
 ### Logging
@@ -44,7 +44,7 @@ export STARSHIP_CACHE=~/.starship/cache
 
 Equivalently in PowerShell (Windows) would be adding this line to your `$PROFILE`:
 
-```ps1
+```powershell
 $ENV:STARSHIP_CACHE = "$HOME\AppData\Local\Temp"
 ```
 
@@ -85,7 +85,7 @@ In the second part, which is enclosed in a `()`, is a [style string](#style-stri
 For example:
 
 - `[on](red bold)` will print a string `on` with bold text colored red.
-- `[⬢ $version](bold green)` will print a symbol `⬢ ` followed by the content of variable `version`, with bold text colored green.
+- `[⌘ $version](bold green)` will print a symbol `⌘ ` followed by the content of variable `version`, with bold text colored green.
 - `[a [b](red) c](green)` will print `a b c` with `b` red, and `a` and `c` green.
 
 #### Style Strings
@@ -155,7 +155,7 @@ This is the list of prompt-wide configuration options.
 | -------------- | ------------------------------ | ----------------------------------------------------- |
 | `format`       | [link](#default-prompt-format) | Configure the format of the prompt.                   |
 | `scan_timeout` | `30`                           | Timeout for starship to scan files (in milliseconds). |
-| `add_newline`  | `true`                         | Add a new line before the start of the prompt.        |
+| `add_newline`  | `true`                         | Inserts blank line between shell prompts.               |
 
 ### Example
 
@@ -171,7 +171,7 @@ format = """
 # Wait 10 milliseconds for starship to check files under the current directory.
 scan_timeout = 10
 
-# Disable the newline at the start of the prompt
+# Disable the blank line at the start of the prompt
 add_newline = false
 ```
 
@@ -216,8 +216,10 @@ $purescript\
 $python\
 $ruby\
 $rust\
+$scala\
 $swift\
 $terraform\
+$vagrant\
 $zig\
 $nix_shell\
 $conda\
@@ -235,6 +237,7 @@ $jobs\
 $battery\
 $time\
 $status\
+$shell\
 $character"""
 ```
 
@@ -247,11 +250,14 @@ The `aws` module shows the current AWS region and profile. This is based on
 When using [aws-vault](https://github.com/99designs/aws-vault) the profile
 is read from the `AWS_VAULT` env var.
 
+When using [awsu](https://github.com/kreuzwerker/awsu) the profile
+is read from the `AWSU_PROFILE` env var.
+
 ### Options
 
 | Option           | Default                                        | Description                                                     |
 | ---------------- | ---------------------------------------------- | --------------------------------------------------------------- |
-| `format`         | `'on [$symbol$profile(\($region\))]($style) '` | The format for the module.                                      |
+| `format`         | `'on [$symbol($profile )(\($region\) )]($style)'` | The format for the module.                                      |
 | `symbol`         | `"☁️ "`                                        | The symbol used before displaying the current AWS profile.      |
 | `region_aliases` |                                                | Table of region aliases to display in addition to the AWS name. |
 | `style`          | `"bold yellow"`                                | The style for the module.                                       |
@@ -276,7 +282,7 @@ is read from the `AWS_VAULT` env var.
 # ~/.config/starship.toml
 
 [aws]
-format = 'on [$symbol$profile(\($region\))]($style) '
+format = 'on [$symbol($profile )(\($region\) )]($style)'
 style = "bold blue"
 symbol = "🅰 "
 [aws.region_aliases]
@@ -388,6 +394,10 @@ can do this in two ways:
 By default it only changes color. If you also want to change it's shape take a
 look at [this example](#with-custom-error-shape).
 
+::: warning
+`error_symbol` is not supported on elvish shell.
+:::
+
 ### Options
 
 | Option           | Default             | Description                                                                      |
@@ -437,7 +447,8 @@ vicmd_symbol = "[V](bold green) "
 
 ## CMake
 
-The `cmake` module shows the currently installed version of CMake if any of the following conditions are met:
+The `cmake` module shows the currently installed version of CMake. By default
+the module will be activated if any of the following conditions are met:
 
 - The current directory contains a `CMakeLists.txt` file
 - The current directory contains a `CMakeCache.txt` file
@@ -445,9 +456,12 @@ The `cmake` module shows the currently installed version of CMake if any of the
 ### Options
 
 | Option              | Default                                | Description                                  |
-| ---------- | ---------------------------------- | -------------------------------------------- |
-| `format`   | `"via [$symbol$version]($style) "` | The format for the module.                   |
-| `symbol`   | `"喝 "`                             | The symbol used before the version of cmake. |
+| ------------------- | -------------------------------------- | -------------------------------------------- |
+| `format`            | `"via [$symbol($version )]($style)"`   | The format for the module.                   |
+| `symbol`            | `"△ "`                                | The symbol used before the version of cmake. |
+| `detect_extensions` | `[]`                                   | Which extensions should trigger this moudle  |
+| `detect_files`      | `["CMakeLists.txt", "CMakeCache.txt"]` | Which filenames should trigger this module   |
+| `detect_folders`    | `[]`                                   | Which folders should trigger this module     |
 | `style`             | `"bold blue"`                          | The style for the module.                    |
 | `disabled`          | `false`                                | Disables the `cmake` module.                 |
 
@@ -560,7 +574,7 @@ format = "[$symbol$environment](dimmed green) "
 ## Crystal
 
 The `crystal` module shows the currently installed version of Crystal.
-The module will be shown if any of the following conditions are met:
+By default the module will be shown if any of the following conditions are met:
 
 - The current directory contains a `shard.yml` file
 - The current directory contains a `.cr` file
@@ -568,10 +582,13 @@ The module will be shown if any of the following conditions are met:
 ### Options
 
 | Option              | Default                              | Description                                               |
-| ---------- | ---------------------------------- | --------------------------------------------------------- |
+| ------------------- | ------------------------------------ | --------------------------------------------------------- |
 | `symbol`            | `"🔮 "`                              | The symbol used before displaying the version of crystal. |
 | `style`             | `"bold red"`                         | The style for the module.                                 |
-| `format`   | `"via [$symbol$version]($style) "` | The format for the module.                                |
+| `detect_extensions` | `["cr"]`                             | Which extensions should trigger this module.              |
+| `detect_files`      | `["shard.yml"]`                      | Which filenames should trigger this module.               |
+| `detect_folders`    | `[]`                                 | Which folders should trigger this module.                 |
+| `format`            | `"via [$symbol($version )]($style)"` | The format for the module.                                |
 | `disabled`          | `false`                              | Disables the `crystal` module.                            |
 
 ### Variables
@@ -596,18 +613,21 @@ format = "via [✨ $version](bold blue) "
 ## Dart
 
 The `dart` module shows the currently installed version of Dart.
-The module will be shown if any of the following conditions are met:
+By default the module will be shown if any of the following conditions are met:
 
 - The current directory contains a file with `.dart` extension
 - The current directory contains a `.dart_tool` directory
-- The current directory contains a `pubspec.yaml` or `pubspec.lock` file
+- The current directory contains a `pubspec.yaml`, `pubspec.yml` or `pubspec.lock` file
 
 ### Options
 
 | Option              | Default                                           | Description                                     |
-| ---------- | ---------------------------------- | ----------------------------------------------- |
-| `format`   | `"via [$symbol$version]($style) "` | The format for the module.                      |
+| ------------------- | ------------------------------------------------- | ----------------------------------------------- |
+| `format`            | `"via [$symbol($version )]($style)"`              | The format for the module.                      |
 | `symbol`            | `"🎯 "`                                           | A format string representing the symbol of Dart |
+| `detect_extensions` | `['dart']`                                        | Which extensions should trigger this moudle.    |
+| `detect_files`      | `["pubspec.yaml", "pubspec.yml", "pubspec.lock"]` | Which filenames should trigger this module.     |
+| `detect_folders`    | `[".dart_tool"]`                                  | Which folders should trigger this module.       |
 | `style`             | `"bold blue"`                                     | The style for the module.                       |
 | `disabled`          | `false`                                           | Disables the `dart` module.                     |
 
@@ -656,15 +676,16 @@ it would have been `nixpkgs/pkgs`.
 | `read_only`         | `"🔒"`                                             | The symbol indicating current directory is read only.                            |
 | `read_only_style`   | `"red"`                                            | The style for the read only symbol.                                              |
 | `truncation_symbol` | `""`                                               | The symbol to prefix to truncated paths. eg: "…/"                                |
+| `home_symbol`       | `"~"`                                              | The symbol indicating home directory.                                           |
 
 <details>
 <summary>This module has a few advanced configuration options that control how the directory is displayed.</summary>
 
 | Advanced Option             | Default | Description                                                               |
-| --------------------------- | ------- | ---------------------------------------------------------------------------------------- |
+| --------------------------- | ------- | ------------------------------------------------------------------------- |
 | `substitutions`             |         | A table of substitutions to be made to the path.                          |
 | `fish_style_pwd_dir_length` | `0`     | The number of characters to use when applying fish shell pwd path logic.  |
-| `use_logical_path`          | `true`  | Displays the logical path provided by the shell (`PWD`) instead of the path from the OS. |
+| `use_logical_path`          | `true`  | If `true` render the logical path sourced from the shell via `PWD` or `--logical-path`. If `false` instead render the physical filesystem path with symlinks resolved. |
 
 `substitutions` allows you to define arbitrary replacements for literal strings that occur in the path, for example long network
 prefixes or development directories (i.e. Java). Note that this will disable the fish style PWD.
@@ -711,12 +732,15 @@ The `docker_context` module shows the currently active
 ### Options
 
 | Option              | Default                                                       | Description                                                                       |
-| ----------------- | ---------------------------------- | --------------------------------------------------------------------------------------- |
+| ------------------- | ------------------------------------------------------------- | --------------------------------------------------------------------------------- |
 | `format`            | `"via [$symbol$context]($style) "`                            | The format for the module.                                                        |
 | `symbol`            | `"🐳 "`                                                       | The symbol used before displaying the Docker context.                             |
+| `only_with_files`   | `true`                                                        | Only show when there's a match                                                    |
+| `detect_extensions` | `[]`                                                          | Which extensions should trigger this module (needs `only_with_files` to be true). |
+| `detect_files`      | `["docker-compose.yml", "docker-compose.yaml", "Dockerfile"]` | Which filenames should trigger this module (needs `only_with_files` to be true).  |
+| `detect_folders`    | `[]`                                                          | Which folders should trigger this module (needs `only_with_files` to be true).    |
 | `style`             | `"blue bold"`                                                 | The style for the module.                                                         |
-| `only_with_files` | `false`                            | Only show when there's a `docker-compose.yml` or `Dockerfile` in the current directory. |
-| `disabled`        | `true`                             | Disables the `docker_context` module.                                                   |
+| `disabled`          | `false`                                                       | Disables the `docker_context` module.                                             |
 
 ### Variables
 
@@ -743,8 +767,8 @@ The `dotnet` module shows the relevant version of the .NET Core SDK for the curr
 the SDK has been pinned in the current directory, the pinned version is shown. Otherwise the module
 shows the latest installed version of the SDK.
 
-This module will only be shown in your prompt when one or more of the following files are present in the
-current directory:
+By default this module will only be shown in your prompt when one or more of
+the following files are present in the current directory:
 
 - `global.json`
 - `project.json`
@@ -770,10 +794,13 @@ when there is a csproj file in the current directory.
 ### Options
 
 | Option              | Default                                                                                                 | Description                                              |
-| ----------- | ----------------------------------------- | -------------------------------------------------------- |
-| `format`    | `"[$symbol$version( 🎯 $tfm)]($style) "`  | The format for the module.                               |
-| `symbol`    | `"•NET "`                                 | The symbol used before displaying the version of dotnet. |
+| ------------------- | ------------------------------------------------------------------------------------------------------- | -------------------------------------------------------- |
+| `format`            | `"[$symbol($version )(🎯 $tfm )]($style)"`                                                              | The format for the module.                               |
+| `symbol`            | `".NET "`                                                                                               | The symbol used before displaying the version of dotnet. |
 | `heuristic`         | `true`                                                                                                  | Use faster version detection to keep starship snappy.    |
+| `detect_extensions` | `["sln", "csproj", "fsproj", "xproj"]`                                                                  | Which extensions should trigger this module.             |
+| `detect_files`      | `["global.json", "project.json", "Directory.Build.props", "Directory.Build.targets", "Packages.props"]` | Which filenames should trigger this module.              |
+| `detect_folders`    | `[]`                                                                                                    | Which folders should trigger this modules.               |
 | `style`             | `"bold blue"`                                                                                           | The style for the module.                                |
 | `disabled`          | `false`                                                                                                 | Disables the `dotnet` module.                            |
 
@@ -802,17 +829,20 @@ heuristic = false
 ## Elixir
 
 The `elixir` module shows the currently installed version of Elixir and Erlang/OTP.
-The module will be shown if any of the following conditions are met:
+By default the module will be shown if any of the following conditions are met:
 
 - The current directory contains a `mix.exs` file.
 
 ### Options
 
 | Option              | Default                                                   | Description                                                     |
-| ---------- | ------------------------------------------------------- | --------------------------------------------------------------- |
+| ------------------- | --------------------------------------------------------- | --------------------------------------------------------------- |
 | `symbol`            | `"💧 "`                                                   | The symbol used before displaying the version of Elixir/Erlang. |
+| `detect_extensions` | `[]`                                                      | Which extensions should trigger this module.                    |
+| `detect_files`      | `["mix.exs"]`                                             | Which filenames should trigger this module.                     |
+| `detect_folders`    | `[]`                                                      | Which folders should trigger this modules.                      |
 | `style`             | `"bold purple"`                                           | The style for the module.                                       |
-| `format`   | `'via [$symbol$version \(OTP $otp_version\)]($style) '` | The format for the module elixir.                               |
+| `format`            | `'via [$symbol($version \(OTP $otp_version\) )]($style)'` | The format for the module elixir.                               |
 | `disabled`          | `false`                                                   | Disables the `elixir` module.                                   |
 
 ### Variables
@@ -838,7 +868,7 @@ symbol = "🔮 "
 ## Elm
 
 The `elm` module shows the currently installed version of Elm.
-The module will be shown if any of the following conditions are met:
+By default the module will be shown if any of the following conditions are met:
 
 - The current directory contains a `elm.json` file
 - The current directory contains a `elm-package.json` file
@@ -849,9 +879,12 @@ The module will be shown if any of the following conditions are met:
 ### Options
 
 | Option              | Default                                            | Description                                     |
-| ---------- | ---------------------------------- | ----------------------------------------------- |
-| `format`   | `"via [$symbol$version]($style) "` | The format for the module.                      |
+| ------------------- | -------------------------------------------------- | ----------------------------------------------- |
+| `format`            | `"via [$symbol($version )]($style)"`               | The format for the module.                      |
 | `symbol`            | `"🌳 "`                                            | A format string representing the symbol of Elm. |
+| `detect_extensions` | `["elm"]`                                          | Which extensions should trigger this module.    |
+| `detect_files`      | `["elm.json", "elm-package.json", ".elm-version"]` | Which filenames should trigger this module.     |
+| `detect_folders`    | `["elm-stuff"]`                                    | Which folders should trigger this modules.      |
 | `style`             | `"cyan bold"`                                      | The style for the module.                       |
 | `disabled`          | `false`                                            | Disables the `elm` module.                      |
 
@@ -915,7 +948,7 @@ default = "unknown shell"
 ## Erlang
 
 The `erlang` module shows the currently installed version of Erlang/OTP.
-The module will be shown if any of the following conditions are met:
+By default the module will be shown if any of the following conditions are met:
 
 - The current directory contains a `rebar.config` file.
 - The current directory contains a `erlang.mk` file.
@@ -923,10 +956,13 @@ The module will be shown if any of the following conditions are met:
 ### Options
 
 | Option              | Default                              | Description                                              |
-| ---------- | ---------------------------------- | -------------------------------------------------------- |
+| ------------------- | ------------------------------------ | -------------------------------------------------------- |
 | `symbol`            | `" "`                               | The symbol used before displaying the version of erlang. |
 | `style`             | `"bold red"`                         | The style for the module.                                |
-| `format`   | `"via [$symbol$version]($style) "` | The format for the module.                               |
+| `detect_extensions` | `[]`                                 | Which extensions should trigger this module.             |
+| `detect_files`      | `["rebar.config", "elang.mk"]`       | Which filenames should trigger this module.              |
+| `detect_folders`    | `[]`                                 | Which folders should trigger this modules.               |
+| `format`            | `"via [$symbol($version )]($style)"` | The format for the module.                               |
 | `disabled`          | `false`                              | Disables the `erlang` module.                            |
 
 ### Variables
@@ -1214,7 +1250,7 @@ behind = "⇣${count}"
 ## Golang
 
 The `golang` module shows the currently installed version of Golang.
-The module will be shown if any of the following conditions are met:
+By default the module will be shown if any of the following conditions are met:
 
 - The current directory contains a `go.mod` file
 - The current directory contains a `go.sum` file
@@ -1228,9 +1264,12 @@ The module will be shown if any of the following conditions are met:
 ### Options
 
 | Option               | Default                                                                        | Description                                    |
-| ---------- | ---------------------------------- | ---------------------------------------------- |
-| `format`   | `"via [$symbol$version]($style) "` | The format for the module.                     |
+| -------------------- | ------------------------------------------------------------------------------ | ---------------------------------------------- |
+| `format`             | `"via [$symbol($version )]($style)"`                                           | The format for the module.                     |
 | `symbol`             | `"🐹 "`                                                                        | A format string representing the symbol of Go. |
+| `detect_extensions`  | `["go"]`                                                                       | Which extensions should trigger this moudle.   |
+| `detect_files`       | `["go.mod", "go.sum", "glide.yaml", "Gopkg.yml", "Gopkg.lock", ".go-version"]` | Which filenames should trigger this module.    |
+| `detect_folders`     | `["Godeps"]`                                                                   | Which folders should trigger this module.      |
 | `style`              | `"bold cyan"`                                                                  | The style for the module.                      |
 | `disabled`           | `false`                                                                        | Disables the `golang` module.                  |
 
@@ -1256,7 +1295,7 @@ format = "via [🏎💨 $version](bold cyan) "
 ## Helm
 
 The `helm` module shows the currently installed version of Helm.
-The module will be shown if any of the following conditions are met:
+By default the module will be shown if any of the following conditions are met:
 
 - The current directory contains a `helmfile.yaml` file
 - The current directory contains a `Chart.yaml` file
@@ -1264,8 +1303,11 @@ The module will be shown if any of the following conditions are met:
 ### Options
 
 | Option              | Default                              | Description                                      |
-| ---------- | ---------------------------------- | ------------------------------------------------ |
-| `format`   | `"via [$symbol$version]($style) "` | The format for the module.                       |
+| ------------------- | ------------------------------------ | ------------------------------------------------ |
+| `format`            | `"via [$symbol($version )]($style)"` | The format for the module.                       |
+| `detect_extensions` | `[]`                                 | Which extensions should trigger this module.     |
+| `detect_files`      | `["helmfile.yaml", "Chart.yaml"]`    | Which filenames should trigger this module.      |
+| `detect_folders`    | `[]`                                 | Which folders should trigger this modules.       |
 | `symbol`            | `"⎈ "`                               | A format string representing the symbol of Helm. |
 | `style`             | `"bold white"`                       | The style for the module.                        |
 | `disabled`          | `false`                              | Disables the `helm` module.                      |
@@ -1327,7 +1369,7 @@ disabled = false
 ## Java
 
 The `java` module shows the currently installed version of Java.
-The module will be shown if any of the following conditions are met:
+By default the module will be shown if any of the following conditions are met:
 
 - The current directory contains a `pom.xml`, `build.gradle.kts`, `build.sbt`, `.java-version`, `.deps.edn`, `project.clj`, or `build.boot` file
 - The current directory contains a file with the `.java`, `.class`, `.gradle`, `.jar`, `.clj`, or `.cljc` extension
@@ -1335,8 +1377,11 @@ The module will be shown if any of the following conditions are met:
 ### Options
 
 | Option              | Default                                                                                                   | Description                                     |
-| ---------- | -------------------------------------- | ----------------------------------------------- |
-| `format`   | `"via [${symbol}${version}]($style) "` | The format for the module.                      |
+| ------------------- | --------------------------------------------------------------------------------------------------------- | ----------------------------------------------- |
+| `format`            | `"via [${symbol}(${version} )]($style)"`                                                                  | The format for the module.                      |
+| `detect_extensions` | `["java", "class", "gradle", "jar", "cljs", "cljc"]`                                                      | Which extensions should trigger this module.    |
+| `detect_files`      | `["pom.xml", "build.gradle.kts", "build.sbt", ".java-version", ".deps.edn", "project.clj", "build.boot"]` | Which filenames should trigger this module.     |
+| `detect_folders`    | `[]`                                                                                                      | Which folders should trigger this modules.      |
 | `symbol`            | `"☕ "`                                                                                                   | A format string representing the symbol of Java |
 | `style`             | `"red dimmed"`                                                                                            | The style for the module.                       |
 | `disabled`          | `false`                                                                                                   | Disables the `java` module.                     |
@@ -1367,6 +1412,12 @@ The module will be shown only if there are background jobs running.
 The module will show the number of jobs running if there is more than 1 job, or
 more than the `threshold` config value, if it exists.
 
+::: warning
+
+This module is not supported on tcsh.
+
+:::
+
 ### Options
 
 | Option      | Default                       | Description                                      |
@@ -1400,7 +1451,7 @@ threshold = 4
 ## Julia
 
 The `julia` module shows the currently installed version of Julia.
-The module will be shown if any of the following conditions are met:
+By default the module will be shown if any of the following conditions are met:
 
 - The current directory contains a `Project.toml` file
 - The current directory contains a `Manifest.toml` file
@@ -1409,8 +1460,11 @@ The module will be shown if any of the following conditions are met:
 ### Options
 
 | Option              | Default                              | Description                                       |
-| ---------- | ---------------------------------- | ------------------------------------------------- |
-| `format`   | `"via [$symbol$version]($style) "` | The format for the module.                        |
+| ------------------- | ------------------------------------ | ------------------------------------------------- |
+| `format`            | `"via [$symbol($version )]($style)"` | The format for the module.                        |
+| `detect_extensions` | `["jl"]`                             | Which extensions should trigger this module.      |
+| `detect_files`      | `["Project.toml", "Manifest.toml"]`  | Which filenames should trigger this module.       |
+| `detect_folders`    | `[]`                                 | Which folders should trigger this modules.        |
 | `symbol`            | `"ஃ "`                               | A format string representing the symbol of Julia. |
 | `style`             | `"bold purple"`                      | The style for the module.                         |
 | `disabled`          | `false`                              | Disables the `julia` module.                      |
@@ -1437,15 +1491,18 @@ symbol = "∴ "
 ## Kotlin
 
 The `kotlin` module shows the currently installed version of Kotlin.
-The module will be shown if any of the following conditions are met:
+By default the module will be shown if any of the following conditions are met:
 
 - The current directory contains a `.kt` or a `.kts` file
 
 ### Options
 
 | Option              | Default                              | Description                                                                   |
-| --------------- | ---------------------------------- | ----------------------------------------------------------------------------- |
-| `format`        | `"via [$symbol$version]($style) "` | The format for the module.                                                    |
+| ------------------- | ------------------------------------ | ----------------------------------------------------------------------------- |
+| `format`            | `"via [$symbol($version )]($style)"` | The format for the module.                                                    |
+| `detect_extensions` | `["kt", "kts"]`                      | Which extensions should trigger this module.                                  |
+| `detect_files`      | `[]`                                 | Which filenames should trigger this module.                                   |
+| `detect_folders`    | `[]`                                 | Which folders should trigger this modules.                                    |
 | `symbol`            | `"🅺 "`                              | A format string representing the symbol of Kotlin.                            |
 | `style`             | `"bold blue"`                        | The style for the module.                                                     |
 | `kotlin_binary`     | `"kotlin"`                           | Configures the kotlin binary that Starship executes when getting the version. |
@@ -1547,7 +1604,7 @@ disabled = true
 ## Lua
 
 The `lua` module shows the currently installed version of Lua.
-The module will be shown if any of the following conditions are met:
+By default the module will be shown if any of the following conditions are met:
 
 - The current directory contains a `.lua-version` file
 - The current directory contains a `lua` directory
@@ -1556,9 +1613,12 @@ The module will be shown if any of the following conditions are met:
 ### Options
 
 | Option              | Default                              | Description                                                                   |
-| ------------ | ---------------------------------- | ----------------------------------------------------------------------------- |
-| `format`     | `"via [$symbol$version]($style) "` | The format for the module.                                                    |
+| ------------------- | ------------------------------------ | ----------------------------------------------------------------------------- |
+| `format`            | `"via [$symbol($version )]($style)"` | The format for the module.                                                    |
 | `symbol`            | `"🌙 "`                              | A format string representing the symbol of Lua.                               |
+| `detect_extensions` | `["lua"]`                            | Which extensions should trigger this moudle.                                  |
+| `detect_files`      | `[".lua-version"]`                   | Which filenames should trigger this module.                                   |
+| `detect_folders`    | `["lua"]`                            | Which folders should trigger this module.                                     |
 | `style`             | `"bold blue"`                        | The style for the module.                                                     |
 | `lua_binary`        | `"lua"`                              | Configures the lua binary that Starship executes when getting the version.    |
 | `disabled`          | `false`                              | Disables the `lua` module.                                                    |
@@ -1670,7 +1730,7 @@ truncation_symbol = ""
 ## Nim
 
 The `nim` module shows the currently installed version of Nim.
-The module will be shown if any of the following conditions are met:
+By default the module will be shown if any of the following conditions are met:
 
 - The current directory contains a `nim.cfg` file
 - The current directory contains a file with the `.nim` extension
@@ -1680,9 +1740,12 @@ The module will be shown if any of the following conditions are met:
 ### Options
 
 | Option               | Default                              | Description                                           |
-| ---------- | ---------------------------------- | ----------------------------------------------------- |
-| `format`   | `"via [$symbol$version]($style) "` | The format for the module                             |
+| -------------------- | ------------------------------------ | ----------------------------------------------------- |
+| `format`             | `"via [$symbol($version )]($style)"` | The format for the module                             |
 | `symbol`             | `"👑 "`                              | The symbol used before displaying the version of Nim. |
+| `detect_extensions`  | `["nim", "nims", "nimble"]`          | Which extensions should trigger this moudle.          |
+| `detect_files`       | `["nim.cfg"]`                        | Which filenames should trigger this module.           |
+| `detect_folders`     | `[]`                                 | Which folders should trigger this module.             |
 | `style`              | `"bold yellow"`                      | The style for the module.                             |
 | `disabled`           | `false`                              | Disables the `nim` module.                            |
 
@@ -1748,7 +1811,7 @@ format = 'via [☃️ $state( \($name\))](bold blue) '
 ## NodeJS
 
 The `nodejs` module shows the currently installed version of NodeJS.
-The module will be shown if any of the following conditions are met:
+By default the module will be shown if any of the following conditions are met:
 
 - The current directory contains a `package.json` file
 - The current directory contains a `.node-version` file
@@ -1759,9 +1822,12 @@ The module will be shown if any of the following conditions are met:
 ### Options
 
 | Option              | Default                              | Description                                        |
-| ---------- | ---------------------------------- | -------------------------------------------------- |
-| `format`   | `"via [$symbol$version]($style) "` | The format for the module.                         |
-| `symbol`   | `"⬢ "`                             | A format string representing the symbol of NodeJS. |
+| ------------------- | ------------------------------------ | -------------------------------------------------- |
+| `format`            | `"via [$symbol($version )]($style)"` | The format for the module.                         |
+| `symbol`            | `" "`                               | A format string representing the symbol of NodeJS. |
+| `detect_extensions` | `["js", "mjs", "cjs", "ts"]`         | Which extensions should trigger this moudle.       |
+| `detect_files`      | `["package.json", ".node-version"]`  | Which filenames should trigger this module.        |
+| `detect_folders`    | `["node_modules"]`                   | Which folders should trigger this module.          |
 | `style`             | `"bold green"`                       | The style for the module.                          |
 | `disabled`          | `false`                              | Disables the `nodejs` module.                      |
 | `not_capable_style` | `bold red`                           | The style for the module when an engines property in Packages.json does not match the NodeJS version. |
@@ -1788,7 +1854,7 @@ format = "via [🤖 $version](bold green) "
 ## OCaml
 
 The `ocaml` module shows the currently installed version of OCaml.
-The module will be shown if any of the following conditions are met:
+By default the module will be shown if any of the following conditions are met:
 
 - The current directory contains a file with `.opam` extension or `_opam` directory
 - The current directory contains a `esy.lock` directory
@@ -1800,9 +1866,12 @@ The module will be shown if any of the following conditions are met:
 ### Options
 
 | Option              | Default                              | Description                                             |
-| ---------- | ---------------------------------- | ------------------------------------------------------- |
-| `format`   | `"via [$symbol$version]($style) "` | The format string for the module.                       |
+| ------------------- | ------------------------------------ | ------------------------------------------------------- |
+| `format`            | `"via [$symbol($version )]($style)"` | The format string for the module.                       |
 | `symbol`            | `"🐫 "`                              | The symbol used before displaying the version of OCaml. |
+| `detect_extensions` | `["opam", "ml", "mli", "re", "rei"]` | Which extensions should trigger this moudle.            |
+| `detect_files`      | `["dune", "dune-project", "jbuild", "jbuild-ignore", ".merlin"]` | Which filenames should trigger this module. |
+| `detect_folders`    | `["_opam", "esy.lock"]`              | Which folders should trigger this module.               |
 | `style`             | `"bold yellow"`                      | The style for the module.                               |
 | `disabled`          | `false`                              | Disables the `ocaml` module.                            |
 
@@ -1891,7 +1960,7 @@ package, and shows its current version. The module currently supports `npm`, `ca
 
 | Option            | Default                            | Description                                                |
 | ----------------- | ---------------------------------- | ---------------------------------------------------------- |
-| `format`          | `"via [$symbol$version]($style) "` | The format for the module.                                 |
+| `format`          | `"is [$symbol$version]($style) "`  | The format for the module.                                 |
 | `symbol`          | `"📦 "`                            | The symbol used before displaying the version the package. |
 | `style`           | `"bold 208"`                       | The style for the module.                                  |
 | `display_private` | `false`                            | Enable displaying version for packages marked as private.  |
@@ -1919,7 +1988,7 @@ format = "via [🎁 $version](208 bold) "
 ## Perl
 
 The `perl` module shows the currently installed version of Perl.
-The module will be shown if any of the following conditions are met:
+By default the module will be shown if any of the following conditions are met:
 
 - The current directory contains a `Makefile.PL` or `Build.PL` file
 - The current directory contains a `cpanfile` or `cpanfile.snapshot` file
@@ -1930,9 +1999,12 @@ The module will be shown if any of the following conditions are met:
 ### Options
 
 | Option               | Default                              | Description                                           |
-| ---------- | ---------------------------------- | ----------------------------------------------------- |
-| `format`   | `"via [$symbol$version]($style) "` | The format string for the module.                     |
+| -------------------- | ------------------------------------ | ----------------------------------------------------- |
+| `format`             | `"via [$symbol($version )]($style)"` | The format string for the module.                     |
 | `symbol`             | `"🐪 "`                              | The symbol used before displaying the version of Perl |
+| `detect_extensions`  | `["pl", "pm", "pod"]`                | Which extensions should trigger this moudle.          |
+| `detect_files`       | `["Makefile.PL", "Build.PL", "cpanfile", "cpanfile.snapshot", "META.json", "META.yml", ".perl-version"]` | Which filenames should trigger this module. |
+| `detect_folders`     | `[]`                                 | Which folders should trigger this module.             |
 | `style`              | `"bold 149"`                         | The style for the module.                             |
 | `disabled`           | `false`                              | Disables the `perl` module.                           |
 
@@ -1956,18 +2028,21 @@ format = "via [🦪 $version]($style) "
 ## PHP
 
 The `php` module shows the currently installed version of PHP.
-The module will be shown if any of the following conditions are met:
+By default the module will be shown if any of the following conditions are met:
 
 - The current directory contains a `composer.json` file
 - The current directory contains a `.php-version` file
-- The current directory contains a `.php` file
+- The current directory contains a `.php` extension
 
 ### Options
 
 | Option               | Default                              | Description                                           |
-| ---------- | ---------------------------------- | ----------------------------------------------------- |
-| `format`   | `"via [$symbol$version]($style) "` | The format for the module.                            |
+| -------------------- | ------------------------------------ | ----------------------------------------------------- |
+| `format`             | `"via [$symbol($version )]($style)"` | The format for the module.                            |
 | `symbol`             | `"🐘 "`                              | The symbol used before displaying the version of PHP. |
+| `detect_extensions`  | `["php"]`                            | Which extensions should trigger this moudle.          |
+| `detect_files`       | `["composer.json", ".php-version"]`  | Which filenames should trigger this module.           |
+| `detect_folders`     | `[]`                                 | Which folders should trigger this module.             |
 | `style`              | `"147 bold"`                         | The style for the module.                             |
 | `disabled`           | `false`                              | Disables the `php` module.                            |
 
@@ -1993,17 +2068,20 @@ format = "via [🔹 $version](147 bold) "
 ## PureScript
 
 The `purescript` module shows the currently installed version of PureScript version.
-The module will be shown if any of the following conditions are met:
+By default the module will be shown if any of the following conditions are met:
 
 - The current directory contains a `spago.dhall` file
-- The current directory contains a \*.purs files
+- The current directory contains a file with the `.purs` extension
 
 ### Options
 
 | Option               | Default                              | Description                                                  |
-| ---------- | ---------------------------------- | ------------------------------------------------------------ |
-| `format`   | `"via [$symbol$version]($style) "` | The format for the module.                                   |
+| -------------------- | ------------------------------------ | ------------------------------------------------------------ |
+| `format`             | `"via [$symbol($version )]($style)"` | The format for the module.                                   |
 | `symbol`             | `"<=> "`                             | The symbol used before displaying the version of PureScript. |
+| `detect_extensions`  | `["purs"]`                           | Which extensions should trigger this moudle.                 |
+| `detect_files`       | `["spago.dhall"]`                    | Which filenames should trigger this module.                  |
+| `detect_folders`     | `[]`                                 | Which folders should trigger this module.                    |
 | `style`              | `"bold white"`                       | The style for the module.                                    |
 | `disabled`           | `false`                              | Disables the `purescript` module.                            |
 
@@ -2034,29 +2112,31 @@ current Python virtual environment if one is activated.
 If `pyenv_version_name` is set to `true`, it will display the pyenv version
 name. Otherwise, it will display the version number from `python --version`.
 
-The module will be shown if any of the following conditions are met:
+By default the module will be shown if any of the following conditions are met:
 
 - The current directory contains a `.python-version` file
-- The current directory contains a `requirements.txt` file
-- The current directory contains a `pyproject.toml` file
-- The current directory contains a file with the `.py` extension (and `scan_for_pyfiles` is true)
 - The current directory contains a `Pipfile` file
-- The current directory contains a `tox.ini` file
-- The current directory contains a `setup.py` file
 - The current directory contains a `__init__.py` file
+- The current directory contains a `pyproject.toml` file
+- The current directory contains a `requirements.txt` file
+- The current directory contains a `setup.py` file
+- The current directory contains a `tox.ini` file
+- The current directory contains a file with the `.py` extension.
 - A virtual environment is currently activated
 
 ### Options
 
 | Option               | Default                                                                                                      | Description                                                                            |
-| -------------------- | ----------------------------------------------------------------------- | -------------------------------------------------------------------------------------- |
-| `format`             | `'via [${symbol}${pyenv_prefix}${version}( \($virtualenv\))]($style) '` | The format for the module.                                                             |
+| -------------------- | ------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------- |
+| `format`             | `'via [${symbol}${pyenv_prefix}(${version} )(\($virtualenv\))]($style)'`                                     | The format for the module.                                                             |
 | `symbol`             | `"🐍 "`                                                                                                      | A format string representing the symbol of Python                                      |
 | `style`              | `"yellow bold"`                                                                                              | The style for the module.                                                              |
 | `pyenv_version_name` | `false`                                                                                                      | Use pyenv to get Python version                                                        |
 | `pyenv_prefix`       | `pyenv `                                                                                                     | Prefix before pyenv version display, only used if pyenv is used                        |
-| `scan_for_pyfiles`   | `true`                                                                  | If false, Python files in the current directory will not show this module.             |
 | `python_binary`      | `["python", "python3, "python2"]`                                                                            | Configures the python binaries that Starship should executes when getting the version. |
+| `detect_extensions`  | `[".py"]`                                                                                                    | Which extensions should trigger this moudle                                            |
+| `detect_files`       | `[".python-version", "Pipfile", "__init__.py", "pyproject.toml", "requirements.txt", "setup.py", "tox.ini"]` | Which filenames should trigger this module                                             |
+| `detect_folders`     | `[]`                                                                                                         | Which folders should trigger this module                                               |
 | `disabled`           | `false`                                                                                                      | Disables the `python` module.                                                          |
 
 ::: tip
@@ -2106,9 +2186,17 @@ pyenv_version_name = true
 python_binary = "python3"
 ```
 
+```toml
+# ~/.config/starship.toml
+
+[python]
+# Don't trigger for files with the py extension
+detect_extensions = []
+```
+
 ## Ruby
 
-The `ruby` module shows the currently installed version of Ruby.
+By default the `ruby` module shows the currently installed version of Ruby.
 The module will be shown if any of the following conditions are met:
 
 - The current directory contains a `Gemfile` file
@@ -2118,9 +2206,12 @@ The module will be shown if any of the following conditions are met:
 ### Options
 
 | Option              | Default                              | Description                                      |
-| ---------- | ---------------------------------- | ------------------------------------------------ |
-| `format`   | `"via [$symbol$version]($style) "` | The format for the module.                       |
+| ------------------- | ------------------------------------ | ------------------------------------------------ |
+| `format`            | `"via [$symbol($version )]($style)"` | The format for the module.                       |
 | `symbol`            | `"💎 "`                              | A format string representing the symbol of Ruby. |
+| `detect_extensions` | `["rb"]`                             | Which extensions should trigger this module.     |
+| `detect_files`      | `["Gemfile", ".ruby-version"]`       | Which filenames should trigger this module.      |
+| `detect_folders`    | `[]`                                 | Which folders should trigger this module.        |
 | `style`             | `"bold red"`                         | The style for the module.                        |
 | `disabled`          | `false`                              | Disables the `ruby` module.                      |
 
@@ -2145,7 +2236,7 @@ symbol = "🔺 "
 
 ## Rust
 
-The `rust` module shows the currently installed version of Rust.
+By default the `rust` module shows the currently installed version of Rust.
 The module will be shown if any of the following conditions are met:
 
 - The current directory contains a `Cargo.toml` file
@@ -2154,9 +2245,12 @@ The module will be shown if any of the following conditions are met:
 ### Options
 
 | Option              | Default                              | Description                                     |
-| ---------- | ---------------------------------- | ----------------------------------------------- |
-| `format`   | `"via [$symbol$version]($style) "` | The format for the module.                      |
+| ------------------- | ------------------------------------ | ----------------------------------------------- |
+| `format`            | `"via [$symbol($version )]($style)"` | The format for the module.                      |
 | `symbol`            | `"🦀 "`                              | A format string representing the symbol of Rust |
+| `detect_extensions` | `["rs"]`                             | Which extensions should trigger this module.    |
+| `detect_files`      | `["Cargo.toml"]`                     | Which filenames should trigger this module.     |
+| `detect_folders`    | `[]`                                 | Which folders should trigger this module.       |
 | `style`             | `"bold red"`                         | The style for the module.                       |
 | `disabled`          | `false`                              | Disables the `rust` module.                     |
 
@@ -2179,6 +2273,90 @@ The module will be shown if any of the following conditions are met:
 format = "via [⚙️ $version](red bold)"
 ```
 
+
+## Scala
+
+The `scala` module shows the currently installed version of Scala.
+By default the module will be shown if any of the following conditions are met:
+
+- The current directory contains a `build.sbt`, `.scalaenv` or `.sbtenv` file
+- The current directory contains a file with the `.scala` or `.sbt` extension
+- The current directory contains a directory named `.metals`
+
+### Options
+
+
+| Option              | Default                                    | Description                                      |
+| ------------------- | -------------------------------------------| -----------------------------------------------  |
+| `format`            | `"via [${symbol}(${version} )]($style)"`   | The format for the module.                       |
+| `detect_extensions` | `["sbt", "scala"]`                         | Which extensions should trigger this module.     |
+| `detect_files`      | `[".scalaenv", ".sbtenv", "build.sbt"]`    | Which filenames should trigger this module.      |
+| `detect_folders`    | `[".metals"]`                              | Which folders should trigger this modules.       |
+| `symbol`            | `"🆂 "`                                    | A format string representing the symbol of Scala.   |
+| `style`             | `"red dimmed"`                             | The style for the module.                        |
+| `disabled`          | `false`                                    | Disables the `scala` module.                     |
+
+### Variables
+
+| Variable | Example    | Description                          |
+| -------- | -----------| ------------------------------------ |
+| version  | `2.13.5`   | The version of `scala`               |
+| symbol   |            | Mirrors the value of option `symbol` |
+| style\*  |            | Mirrors the value of option `style`  |
+
+\*: This variable can only be used as a part of a style string
+
+### Example
+
+```toml
+# ~/.config/starship.toml
+
+[scala]
+symbol = "🌟 "
+```
+
+
+## Shell
+
+The `shell` module shows an indicator for currently used shell.
+
+::: tip
+
+This module is disabled by default.
+To enable it, set `disabled` to `false` in your configuration file.
+
+:::
+
+### Options
+
+| Option                 | Default       | Description |
+| ---------------------- | ------------- | --------------------------------------------- |
+| `bash_indicator`       | `bsh`         | A format string used to represent bash.       |
+| `fish_indicator`       | `fsh`         | A format string used to represent fish.       |
+| `zsh_indicator`        | `zsh`         | A format string used to represent zsh.        |
+| `powershell_indicator` | `psh`         | A format string used to represent powershell. |
+| `ion_indicator`        | `ion`         | A format string used to represent ion.        |
+| `elvish_indicator`     | `esh`         | A format string used to represent elvish.     |
+| `tcsh_indicator`       | `tsh`         | A format string used to represent tcsh.       |
+| `format`               | `$indicator ` | The format for the module.                    |
+| `disabled`             | `true`        | Disables the `shell` module.                  |
+
+### Variables
+
+| Variable    | Default | Description                                                |
+| ----------- | ------- | ---------------------------------------------------------- |
+| indicator   |         | Mirrors the value of `indicator` for currently used shell. |
+
+### Examples
+```toml
+# ~/.config/starship.toml
+
+[shell]
+fish_indicator = ""
+powershell_indicator = "_"
+disabled = false
+```
+
 ## SHLVL
 
 The `shlvl` module shows the current SHLVL ("shell level") environment variable, if it is
@@ -2258,22 +2436,38 @@ The module will be shown only if the exit code is not `0`.
 
 This module is disabled by default.
 To enable it, set `disabled` to `false` in your configuration file.
+
+:::
+
+::: warning
+This module is not supported on elvish shell.
 :::
 
 ### Options
 
 | Option                    | Default                     | Description                                            |
-| ---------- | --------------------------- | ------------------------------------------------------ |
-| `format`   | `[$symbol$status]($style) ` | The format of the module                               |
-| `symbol`   | `"✖"`                       | A format string representing the symbol for the status |
+| ------------------------- | --------------------------- | ------------------------------------------------------ |
+| `format`                  | `"[$symbol$status]($style) "` | The format of the module                               |
+| `symbol`                  | `"✖"`                       | The symbol displayed on program error                  |
+| `not_executable_symbol`   | `"🚫"`                       | The symbol displayed when file isn't executable        |
+| `not_found_symbol`        | `"🔍"`                       | The symbol displayed when the command can't be found   |
+| `sigint_symbol`           | `"🧱"`                       | The symbol displayed on SIGINT (Ctrl + c)              |
+| `signal_symbol`           | `"⚡"`                       | The symbol displayed on any signal |
 | `style`                   | `"bold red"`                | The style for the module.                              |
+| `recognize_signal_code`   | `true`                      | Enable signal mapping from exit code                   |
+| `map_symbol`              | `false`                     | Enable symbols mapping from exit code                  |
 | `disabled`                | `true`                      | Disables the `status` module.                          |
 
 ### Variables
 
 | Variable                | Example | Description                                                             |
-| -------- | ------- | ------------------------------------ |
+| ----------------------- | ------- | ----------------------------------------------------------------------- |
 | status                  | `127`   | The exit code of the last command                                       |
+| int                     | `127`   | The exit code of the last command                                       |
+| common_meaning          | `ERROR` | Meaning of the code if not a signal                                     |
+| signal_number           | `9`     | Signal number corresponding to the exit code, only if signalled         |
+| signal_name             | `KILL`  | Name of the signal corresponding to the exit code, only if signalled    |
+| maybe_int               | `7`     | Contains the exit code number when no meaning has been found            |
 | symbol                  |         | Mirrors the value of option `symbol`                                    |
 | style\*                 |         | Mirrors the value of option `style`                                     |
 
@@ -2287,15 +2481,16 @@ To enable it, set `disabled` to `false` in your configuration file.
 
 [status]
 style = "bg:blue"
-symbol = "💣 "
-format = '[\[$symbol$status\]]($style) '
+symbol = "🔴"
+format = '[\[$symbol $common_meaning$signal_name$maybe_int\]]($style) '
+map_symbol = true
 disabled = false
 
 ```
 
 ## Swift
 
-The `swift` module shows the currently installed version of Swift.
+By default the `swift` module shows the currently installed version of Swift.
 The module will be shown if any of the following conditions are met:
 
 - The current directory contains a `Package.swift` file
@@ -2304,9 +2499,12 @@ The module will be shown if any of the following conditions are met:
 ### Options
 
 | Option              | Default                              | Description                                      |
-| ---------- | ---------------------------------- | ------------------------------------------------ |
-| `format`   | `"via [$symbol$version]($style) "` | The format for the module.                       |
+| ------------------- | ------------------------------------ | ------------------------------------------------ |
+| `format`            | `"via [$symbol($version )]($style)"` | The format for the module.                       |
 | `symbol`            | `"🐦 "`                              | A format string representing the symbol of Swift |
+| `detect_extensions` | `["swift"]`                          | Which extensions should trigger this moudle.     |
+| `detect_files`      | `["Package.swift"]`                  | Which filenames should trigger this module.      |
+| `detect_folders`    | `[]`                                 | Which folders should trigger this module.        |
 | `style`             | `"bold 202"`                         | The style for the module.                        |
 | `disabled`          | `false`                              | Disables the `swift` module.                     |
 
@@ -2332,9 +2530,15 @@ format = "via [🏎  $version](red bold)"
 ## Terraform
 
 The `terraform` module shows the currently selected terraform workspace and version.
-By default the terraform version is not shown, since this is slow on current versions of terraform when a lot of plugins are in use.
+
+::: tip
+
+By default the terraform version is not shown, since this is slow for current versions of terraform when a lot of plugins are in use.
 If you still want to enable it, [follow the example shown below](#with-version).
-The module will be shown if any of the following conditions are met:
+
+:::
+
+By default the module will be shown if any of the following conditions are met:
 
 - The current directory contains a `.terraform` folder
 - Current directory contains a file with the `.tf` or `.hcl` extensions
@@ -2342,9 +2546,12 @@ The module will be shown if any of the following conditions are met:
 ### Options
 
 | Option              | Default                              | Description                                           |
-| ---------- | ------------------------------------ | ----------------------------------------------------- |
+| ------------------- | ------------------------------------ | ----------------------------------------------------- |
 | `format`            | `"via [$symbol$workspace]($style) "` | The format string for the module.                     |
 | `symbol`            | `"💠"`                               | A format string shown before the terraform workspace. |
+| `detect_extensions` | `["tf", "hcl"]`                      | Which extensions should trigger this module.          |
+| `detect_files`      | `[]`                                 | Which filenames should trigger this module.           |
+| `detect_folders`    | `[".terraform"]`                     | Which folders should trigger this module.             |
 | `style`             | `"bold 105"`                         | The style for the module.                             |
 | `disabled`          | `false`                              | Disables the `terraform` module.                      |
 
@@ -2439,9 +2646,11 @@ The module will be shown if any of the following conditions are met:
 - The variable `show_always` is set to true
 
 ::: tip
+
 SSH connection is detected by checking environment variables
 `SSH_CONNECTION`, `SSH_CLIENT`, and `SSH_TTY`. If your SSH host does not set up
 these variables, one workaround is to set one of them with a dummy value.
+
 :::
 
 ### Options
@@ -2474,9 +2683,47 @@ disabled = false
 show_always = true
 ```
 
+## Vagrant
+
+The `vagrant` module shows the currently installed version of Vagrant.
+By default the module will be shown if any of the following conditions are met:
+
+- The current directory contains a `Vagrantfile` file
+
+### Options
+
+| Option              | Default                              | Description                                         |
+| ------------------- | ------------------------------------ | --------------------------------------------------- |
+| `format`            | `"via [$symbol($version )]($style)"` | The format for the module.                          |
+| `symbol`            | `"⍱ "`                               | A format string representing the symbol of Vagrant. |
+| `detect_extensions` | `[]`                                 | Which extensions should trigger this module.        |
+| `detect_files`      | `["Vagrantfile"]`                    | Which filenames should trigger this module.         |
+| `detect_folders`    | `[]`                                 | Which folders should trigger this module.           |
+| `style`             | `"cyan bold"`                        | The style for the module.                           |
+| `disabled`          | `false`                              | Disables the `Vagrant` module.                      |
+
+### Variables
+
+| Variable | Example          | Description                          |
+| -------- | ---------------- | ------------------------------------ |
+| version  | `Vagrant 2.2.10` | The version of `Vagrant`             |
+| symbol   |                  | Mirrors the value of option `symbol` |
+| style\*  |                  | Mirrors the value of option `style`  |
+
+\*: This variable can only be used as a part of a style string
+
+### Example
+
+```toml
+# ~/.config/starship.toml
+
+[vagrant]
+format = "via [⍱ $version](bold white) "
+```
+
 ## Zig
 
-The `zig` module shows the currently installed version of Zig.
+By default the the `zig` module shows the currently installed version of Zig.
 The module will be shown if any of the following conditions are met:
 
 - The current directory contains a `.zig` file
@@ -2484,11 +2731,14 @@ The module will be shown if any of the following conditions are met:
 ### Options
 
 | Option              | Default                              | Description                                           |
-| ---------- | ---------------------------------- | ----------------------------------------------------- |
+| ------------------- | ------------------------------------ | ----------------------------------------------------- |
 | `symbol`            | `"↯ "`                               | The symbol used before displaying the version of Zig. |
 | `style`             | `"bold yellow"`                      | The style for the module.                             |
-| `format`   | `"via [$symbol$version]($style) "` | The format for the module.                            |
+| `format`            | `"via [$symbol($version )]($style)"` | The format for the module.                            |
 | `disabled`          | `false`                              | Disables the `zig` module.                            |
+| `detect_extensions` | `["zig"]`                            | Which extensions should trigger this module.          |
+| `detect_files`      | `[]`                                 | Which filenames should trigger this module.           |
+| `detect_folders`    | `[]`                                 | Which folders should trigger this module.             |
 
 ### Variables
 
@@ -2544,7 +2794,7 @@ If you have an interesting example not covered there, feel free to share it ther
 ### Options
 
 | Option        | Default                       | Description                                                                                                                |
-| ------------- | ----------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
+| ------------- | ------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
 | `command`     |                                 | The command whose output should be printed. The command will be passed on stdin to the shell.                              |
 | `when`        |                                 | A shell command used as a condition to show the module. The module will be shown if the command returns a `0` status code. |
 | `shell`       |                                 | [See below](#custom-command-shell)                                                                                         |
@@ -2554,7 +2804,7 @@ If you have an interesting example not covered there, feel free to share it ther
 | `extensions`  | `[]`                            | The extensions that will be searched in the working directory for a match.                                                 |
 | `symbol`      | `""`                            | The symbol used before displaying the command output.                                                                      |
 | `style`       | `"bold green"`                  | The style for the module.                                                                                                  |
-| `format`      | `"[$symbol$output]($style) "` | The format for the module.                                                                                                 |
+| `format`      | `"[$symbol($output )]($style)"` | The format for the module.                                                                                                 |
 | `disabled`    | `false`                         | Disables this `custom` module.                                                                                             |
 
 ### Variables

docs/de-DE/README.md

@@ -2,7 +2,7 @@
 home: true
 heroImage: /logo.svg
 heroText:
-tagline: The minimal, blazing-fast, and infinitely customizable prompt for any shell!
+tagline: Minimale, super schnelle und unendlich anpassbare Prompt für jede Shell!
 actionText: Loslegen →
 actionLink: ./guide/
 features:
@@ -18,7 +18,7 @@ features:
 footer: ICS lizenziert | Copyright © 2019-heute Starship-Mitwirkende
 #Used for the description meta tag, for SEO
 metaTitle: "Starship: Cross-Shell Prompt"
-description: Starship is the minimal, blazing fast, and extremely customizable prompt for any shell! Shows the information you need, while staying sleek and minimal. Quick installation available for Bash, Fish, ZSH, Ion, and PowerShell.
+description: Starship ist eine minimale, super schnelle, und extrem anpassbare Prompt für jede Shell! Shows the information you need, while staying sleek and minimal. Schnellinstallation verfügbar für Bash, Fish, ZSH, Ion und PowerShell.
 ---
 
 <div class="center">
@@ -110,3 +110,27 @@ description: Starship is the minimal, blazing fast, and extremely customizable p
 
    eval $(starship init ion)
    ```
+
+   #### Elvish
+
+   ::: warning Only elvish v0.15 or higher is supported. :::
+
+   Add the following to the end of `~/.elvish/rc.elv`:
+
+   ```sh
+   # ~/.elvish/rc.elv
+
+   eval (starship init elvish)
+   ```
+
+
+   #### Tcsh
+
+   Add the following to the end of `~/.tcshrc`:
+
+   ```sh
+   # ~/.tcshrc
+
+   eval `starship init tcsh`
+   ```
+

docs/de-DE/advanced-config/README.md

@@ -82,7 +82,7 @@ Style-String sind Wortlisten, getrennt durch Leerzeichen. Die Wörter haben kein
 
 wobei `<color>` eine Farbspezifikation ist (siehe unten). `fg:<color>` und `<color>` tun derzeit dasselbe , das kann sich in Zukunft aber ändern. Die Reihenfolge der Wörter in der Liste spielt keine Rolle.
 
-`None` überschreibt alle anderen Tokens in einem String, so dass z.B. der string `fg:red none fg:blue` kein Styling anzeigen wird. In der Zukunft könnte die Unterstützung von `none` in Verbindung mit anderen Tokens fallen gelassen werden.
+The `none` token overrides all other tokens in a string if it is not part of a `bg:` specifier, so that e.g. `fg:red none fg:blue` will still create a string with no styling. `bg:none`  sets the background to the default color so `fg:red bg:none` is equivalent to `red` or `fg:red` and `bg:green fg:red bg:none` is also equivalent to `fg:red` or `red`. In der Zukunft könnte die Unterstützung von `none` in Verbindung mit anderen Tokens fallen gelassen werden.
 
 Eine Farbspezifikation kann wie folgt aussehen:
 

docs/de-DE/faq/README.md

@@ -12,7 +12,7 @@
 
 ## How do I get command completion as shown in the demo GIF?
 
-Completion support is provided by your shell of choice. In the case of the demo, the demo was done with [Fish Shell](https://fishshell.com/), which provides completions by default. If you use Z Shell (zsh), I'd suggest taking a look at [zsh-autosuggestions](https://github.com/zsh-users/zsh-autosuggestions).
+Completion support, or autocomplete, is provided by your shell of choice. In the case of the demo, the demo was done with [Fish Shell](https://fishshell.com/), which provides completions by default. If you use Z Shell (zsh), I'd suggest taking a look at [zsh-autosuggestions](https://github.com/zsh-users/zsh-autosuggestions).
 
 ## Do top level `format` and `<module>.disabled` do the same thing?
 
@@ -21,7 +21,7 @@ Ja, beide können benutzt werden, um Module in der Prompt zu deaktivieren. Wenn
 - Disabling modules is more explicit than omitting them from the top level `format`
 - Mit der Aktualisierung von Starship werden neu erstellte Module an die Eingabezeile angefügt
 
-## Laut Dokumentation ist Starship cross-shell, aber es läuft nicht auf shell X. Warum?
+## The docs say Starship is cross-shell. Why isn't my preferred shell supported?
 
 Starship ist auf so eine Weise gebaut, das die Unterstützung so gut wie jeder Shell möglch sein sollte. Die Starship Binärdatei läuft völlig unabhängig von der Shell, und sollte auf jeder benutzt werden können, die eine Anpassung des Stils erlaubt.
 
@@ -38,7 +38,7 @@ NUM_JOBS=$(jobs -p | wc -l)
 PS1="$(starship prompt --status=$STATUS --jobs=$NUM_JOBS)"
 ```
 
-Die [Bash Implementation](https://github.com/starship/starship/blob/master/src/init/starship.bash) ist etwas komplexer, um erweiterte Funktionen wie das [Befehlsdauer-Modul](https://starship.rs/config/#Command-Duration) zu ermöglichen und um sicherzustellen, dass Starship mit vorinstallierten Bash Konfigurationen kompatibel ist.
+The [Bash implementation](https://github.com/starship/starship/blob/master/src/init/starship.bash) built into Starship is slightly more complex to allow for advanced features like the [Command Duration module](https://starship.rs/config/#command-duration) and to ensure that Starship is compatible with pre-installed Bash configurations.
 
 Für eine Liste aller Flaggen, die von `Starship-Eingabeaufforderung` akzeptiert wird, verwenden Sie den folgenden Befehl:
 
@@ -56,6 +56,10 @@ If you get an error like "_version 'GLIBC_2.18' not found (required by starship)
 curl -fsSL https://starship.rs/install.sh | bash -s -- --platform unknown-linux-musl
 ```
 
+## I see symbols I don't understand or expect, what do they mean?
+
+If you see symbols that you don't recognise you can use `starship explain` to explain the currently showing modules.
+
 ## 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:

docs/de-DE/guide/README.md

@@ -2,31 +2,36 @@
   <img
     width="400"
     src="https://raw.githubusercontent.com/starship/starship/master/media/logo.png"
-    alt="Starship – Cross-Shell Prompt" />
+    alt="Starship – Cross-Shell Prompt"
+ />
 </p>
 
 <p align="center">
   <a href="https://github.com/starship/starship/actions"
     ><img
       src="https://img.shields.io/github/workflow/status/starship/starship/Main workflow/master?label=workflow&style=flat-square"
-      alt="Workflow-Status der GitHub Actions" /></a>
+      alt="Workflow-Status der GitHub Actions"
+ /></a>
   <a href="https://crates.io/crates/starship"
     ><img
       src="https://img.shields.io/crates/v/starship?style=flat-square"
-      alt="Crates.io-Version" /></a>
+      alt="Crates.io-Version"
+ /></a>
   <a href="https://repology.org/project/starship/versions"
     ><img
       src="https://img.shields.io/repology/repositories/starship?label=in%20repositories&style=flat-square"
       alt="Paket-Status" /></a
 ><br />
-  <a href="https://discord.gg/8Jzqu3T"
+  <a href="https://discord.gg/starship"
     ><img
       src="https://img.shields.io/discord/567163873606500352?label=discord&logoColor=white&style=flat-square"
-      alt="Chat auf Discord" /></a>
+      alt="Chat auf Discord"
+ /></a>
   <a href="https://twitter.com/StarshipPrompt"
     ><img
       src="https://img.shields.io/badge/twitter-@StarshipPrompt-1DA1F3?style=flat-square"
-      alt="Follow @StarshipPrompt on Twitter" /></a>
+      alt="Folge @StarshipPrompt auf Twitter"
+ /></a>
 </p>
 
 <p align="center">
@@ -42,54 +47,72 @@
     ><img
       height="20"
       src="https://raw.githubusercontent.com/starship/starship/master/media/flag-us.png"
-      alt="Englisch" /></a>
+      alt="Englisch"
+ /></a>
   &nbsp;
   <a
     href="https://github.com/starship/starship/blob/master/docs/ja-JP/guide/README.md"
     ><img
       height="20"
       src="https://raw.githubusercontent.com/starship/starship/master/media/flag-jp.png"
-      alt="日本語" /></a>
+      alt="日本語"
+ /></a>
   &nbsp;
   <a
     href="https://github.com/starship/starship/blob/master/docs/zh-TW/guide/README.md"
     ><img
       height="20"
       src="https://raw.githubusercontent.com/starship/starship/master/media/flag-tw.png"
-      alt="繁體中文" /></a>
+      alt="繁體中文"
+ /></a>
   &nbsp;
   <a
     href="https://github.com/starship/starship/blob/master/docs/ru-RU/guide/README.md"
     ><img
       height="20"
       src="https://raw.githubusercontent.com/starship/starship/master/media/flag-ru.png"
-      alt="Russisch" /></a>
+      alt="Russisch"
+ /></a>
   &nbsp;
   <a
     href="https://github.com/starship/starship/blob/master/docs/de-DE/guide/README.md"
     ><img
       height="20"
       src="https://raw.githubusercontent.com/starship/starship/master/media/flag-de.png"
-      alt="Deutsch" /></a>
+      alt="Deutsch"
+ /></a>
   &nbsp;
   <a
     href="https://github.com/starship/starship/blob/master/docs/zh-CN/guide/README.md"
     ><img
       height="20"
       src="https://raw.githubusercontent.com/starship/starship/master/media/flag-cn.png"
-      alt="简体中文" /></a>
+      alt="简体中文"
+ /></a>
   &nbsp;
-  <a href="https://translate.starship.rs/project/starship-prompt/es"
+  <a 
+    href="https://github.com/starship/starship/blob/master/docs/es-ES/guide/README.md"
     ><img
       height="20"
       src="https://raw.githubusercontent.com/starship/starship/master/media/flag-es.png"
-      alt="Español" /></a>
+      alt="Español"
+ /></a>
   &nbsp;
-  <a href="https://translate.starship.rs/project/starship-prompt/fr"
+  <a 
+    href="https://github.com/starship/starship/blob/master/docs/fr-FR/guide/README.md"
     ><img
       height="20"
       src="https://raw.githubusercontent.com/starship/starship/master/media/flag-fr.png"
-      alt="Français" /></a>
+      alt="Français"
+ /></a>
+  &nbsp;
+  <a 
+    href="https://github.com/starship/starship/blob/master/docs/vi-VN/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-vn.png"
+      alt="Tiếng Việt"
+ /></a>
 </p>
 
 <h1></h1>
@@ -98,11 +121,10 @@
   src="https://raw.githubusercontent.com/starship/starship/master/media/demo.gif"
   alt="Starship mit iTem2 und dem Theme „Snazzy“"
   width="50%"
-  align="right" />
-
-
-**The minimal, blazing-fast, and infinitely customizable prompt for any shell!**
+  align="right"
+ />
 
+**Minimale, super schnelle und unendlich anpassbare Prompt für jede Shell!**
 
 - **Fast:** it's fast – _really really_ fast! 🚀
 - **Customizable:** configure every aspect of your prompt.
@@ -121,34 +143,29 @@
 
 ### Voraussetzungen
 
-- A [Nerd Font](https://www.nerdfonts.com/) installed and enabled in your terminal (for example, try the [Fira Code Nerd Font](https://www.nerdfonts.com/font-downloads)).
+- Eine [Nerd Schriftart](https://www.nerdfonts.com/) installiert und im Terminal aktiviert (zum Beispiel [Fira Code Nerd Font](https://www.nerdfonts.com/font-downloads)).
 
 ### Erste Schritte
 
-1. Installiere die Binärversion von **starship**:
+**Note**: due to the proliferation of different platforms, only a subset of supported platforms are shown below. Can't see yours? Have a look at the [extra platform instructions](https://starship.rs/installing/).
+
+1. Installiere **starship**:
 
 
    #### Neueste Version installieren
 
 
-   ##### Neuster GitHub Release mit Shell:
+   ##### Neuster GitHub Release über die Shell:
 
    ```sh
    curl -fsSL https://starship.rs/install.sh | bash
    ```
 
 
-   ##### Von Quellcode auf [crates.io](https://crates.io/):
-
-   ```sh
-   cargo install starship
-   ```
-
-
    #### Installation mithilfe eines Paket-Managers
 
 
-   ##### Mit [Homebrew](https://brew.sh/):
+   ##### Example: [Homebrew](https://brew.sh/):
 
    ```sh
    brew install starship
@@ -161,7 +178,7 @@
    scoop install starship
    ```
 
-1. Füge das init-Skript zur Konfigurationsdatei deiner Shell hinzu:
+2. Füge das init-Skript zur Konfigurationsdatei deiner Shell hinzu:
 
 
    #### Bash
@@ -201,7 +218,7 @@
 
    Add the following to the end of `Microsoft.PowerShell_profile.ps1`. You can check the location of this file by querying the `$PROFILE` variable in PowerShell. Typically the path is `~\Documents\PowerShell\Microsoft.PowerShell_profile.ps1` or `~/.config/powershell/Microsoft.PowerShell_profile.ps1` on -Nix.
 
-   ```sh
+   ```powershell
    Invoke-Expression (&starship init powershell)
    ```
 
@@ -216,28 +233,52 @@
    eval $(starship init ion)
    ```
 
+
+   #### Elvish
+
+   **Warning** Only elvish v0.15 or higher is supported. Add the following to the end of `~/.elvish/rc.elv`:
+
+   ```sh
+   # ~/.elvish/rc.elv
+
+   eval (starship init elvish)
+   ```
+
+
+   #### Tcsh
+
+   Add the following to the end of `~/.tcshrc`:
+
+   ```sh
+   # ~/.tcshrc
+
+   eval `starship init tcsh`
+   ```
+
 ## 🤝 Mitwirken
 
 Wir laden Leute **aller Erfahrungsstufen** herzlich ein mitzumachen! Falls du dich mit dem Projekt vertaut machen willst, versuche ein [good first issue](https://github.com/starship/starship/labels/🌱%20good%20first%20issue).
 
+Wenn du eine andere Sprache flüssig sprichts, würden wir uns sehr freuen wenn du helfen würdest die Dokumentation in anderen Sprachen auf dem aktuellsten Stand zu halten. Hier kannst du bei der Übersetzung helfen [Starship Crowdin](https://translate.starship.rs/).
+
 Falls du an Starship mitwirken willst, wirf bitte einen Blick auf den [Leitfaden zum Mitwirken](https://github.com/starship/starship/blob/master/CONTRIBUTING.md). Schau auch gerne auf unserem [Discord-Server](https://discord.gg/8Jzqu3T) vorbei. 👋
 
-### Code Contributors
+### Mitwirkenden
 
-This project exists thanks to all the people who contribute. [[Contribute](https://github.com/starship/starship/blob/master/CONTRIBUTING.md)].
+Das Projekt existiert dank aller der, die Mitwirken. [[Mitmachen](https://github.com/starship/starship/blob/master/CONTRIBUTING.md)].
 <a href="https://github.com/starship/starship/graphs/contributors"><img src="https://opencollective.com/starship/contributors.svg?width=890&button=false" /></a>
 
-### Financial Contributors
+### Finanzielle Unterstützung
 
-Become a financial contributor and help us sustain our community. [[Contribute](https://opencollective.com/starship/contribute)]
+Become a financial contributor and help us sustain our community. [[Mitmachen](https://opencollective.com/starship/contribute)]
 
 #### Individuals
 
 <a href="https://opencollective.com/starship"><img src="https://opencollective.com/starship/individuals.svg?width=890"></a>
 
-#### Organizations
+#### Organisationen
 
-Support this project with your organization. Your logo will show up here with a link to your website. [[Contribute](https://opencollective.com/starship/contribute)]
+Support this project with your organization. Your logo will show up here with a link to your website. [[Mitmachen](https://opencollective.com/starship/contribute)]
 
 <a href="https://opencollective.com/starship/organization/0/website"><img src="https://opencollective.com/starship/organization/0/avatar.svg"></a>
 <a href="https://opencollective.com/starship/organization/1/website"><img src="https://opencollective.com/starship/organization/1/avatar.svg"></a>
@@ -252,7 +293,7 @@ Support this project with your organization. Your logo will show up here with a
 
 ## 💭 Inspiriert durch
 
-Checkt bitte diese älteren Projekte, die das Entstehen von Starhip inspiriert haben. 🙏
+Bitte schaue dir diese früheren Projekte an, die dazu beigetragen haben, Starship zu kreieren. 🙏
 
 - **[denysdovhan/spaceship-prompt](https://github.com/denysdovhan/spaceship-prompt)** - Ein ZSH-Prompt für Astronauten.
 
@@ -262,9 +303,9 @@ Checkt bitte diese älteren Projekte, die das Entstehen von Starhip inspiriert h
 
 <p align="center">
     <br>
-    <img width="100" src="https://raw.githubusercontent.com/starship/starship/master/media/icon.png" alt="Starship Raketen Icon">
+    <img width="100" src="https://raw.githubusercontent.com/starship/starship/master/media/icon.png" alt="Starship Raketen-Symbol">
 </p>
 
 ## 📝 Lizenz
 
-Copyright © 2019-present, [Starship Contributors](https://github.com/starship/starship/graphs/contributors).<br /> Unter der [ISC](https://github.com/starship/starship/blob/master/LICENSE) Lizens.
+Copyright © 2019-heute [Starship-Mitwirkende](https://github.com/starship/starship/graphs/contributors).<br /> Dieses Projekt ist [ISC](https://github.com/starship/starship/blob/master/LICENSE) lizenziert.

docs/de-DE/installing/README.md

@@ -0,0 +1,84 @@
+# 🚀 Advanced Installation
+
+Um starship zu installieren, musst du zwei Dinge tun:
+
+1. Get the **starship** binary onto your computer
+1. Tell your shell to use the starship binary as its prompt by modifying its init scripts
+
+For most users, the instructions on [the main page](/guide/#🚀-installation) will work great. However, for some more specialized platforms, different instructions are needed.
+
+There are so many platforms out there that they didn't fit into the main README.md file, so here are some installation instructions for other platforms from the community. Is yours not here? Please do add it here if you figure it out!
+
+## [Chocolatey](https://chocolatey.org)
+
+### Voraussetzungen
+
+Head over to the [Chocolatey installation page](https://chocolatey.org/install) and follow the instructions to install Chocolatey.
+
+### Installation
+
+```powershell
+choco install starship
+```
+
+## [termux](https://termux.com)
+
+### Voraussetzungen
+
+```sh
+pkg install getconf
+```
+
+### Installation
+
+```sh
+curl -fsSL https://starship.rs/install.sh | bash -s -- -b /data/data/com.termux/files/usr/bin
+```
+
+## [Nix](https://nixos.wiki/wiki/Nix)
+
+### Getting the Binary
+
+#### Imperatively
+
+```sh
+nix-env -iA nixos.starship
+```
+
+#### Declarative, single user, via [home-manager](home-manager)
+
+Enable the `programs.starship` module in your `home.nix` file, and add your settings
+
+```nix
+{
+  programs.starship = {
+    enable = true;
+    enableZshIntegration = true;
+    # Configuration written to ~/.config/starship.toml
+    settings = {
+      # add_newline = false;
+
+      # character = {
+      #   success_symbol = "[➜](bold green)";
+      #   error_symbol = "[➜](bold red)";
+      # };
+
+      # package.disabled = true;
+    };
+  };
+}
+```
+
+then run
+
+```sh
+home-manager switch
+```
+
+#### Declarative, system-wide, with NixOS
+
+Add `pkgs.starship` to `environment.systemPackages` in your `configuration.nix`, then run
+
+```sh
+sudo nixos-rebuild switch
+```

docs/de-DE/presets/README.md

@@ -18,17 +18,15 @@ This preset doesn't change anything except for the symbols used for each module.
 [aws]
 symbol = "  "
 
-[battery]
-full_symbol = ""
-charging_symbol = ""
-discharging_symbol = ""
-
 [conda]
 symbol = " "
 
 [dart]
 symbol = " "
 
+[directory]
+read_only = " "
+
 [docker]
 symbol = " "
 
@@ -86,6 +84,9 @@ symbol = " "
 [rust]
 symbol = " "
 
+[scala]
+symbol = " "
+
 [swift]
 symbol = "ﯣ "
 ```

docs/es-ES/README.md

@@ -8,17 +8,17 @@ actionLink: ./guide/
 features:
   - 
     title: Compatibilidad primero
-    details: Funciona en las shells más comunes en los sistemas operativos más comunes. ¡Úsalo en todas partes!
+    details: Funciona en los intérprete de comandos más comunes de los sistemas operativos más comunes. ¡Úsalo en todas partes!
   - 
     title: Desarrollado en Rust
     details: Obtén la mayor velocidad y seguridad de Rust, para hacer tu prompt lo más rápida y segura posible.
   - 
     title: Personalizable
-    details: Puedes personalizar cada pequeño detalle a tu gusto, de manera que puedes tener una interfaz minimalista o rica en funcionalidades.
+    details: Puedes personalizar cada pequeño detalle a tu gusto, de manera que puedes tener un prompt minimalista o rico en funcionalidades.
 footer: Bajo una licencia ISC | Derechos de autor © 2019-presente Colaboradores de Starship
 #Used for the description meta tag, for SEO
-metaTitle: "Starship: el indicador de comando multi-intérprete"
-description: Starship es el símbolo de sistema minimalista, ultrarápido e infinitamente customizable para cualquier intérprete de comandos. Muestra la información que necesitas, a la par que es elegante y minimalista. Instalación rápida disponible para Bash, Fish, ZSH, Ion y PowerShell.
+metaTitle: "Starship: el prompt multi-intérprete"
+description: '¡Starship es el prompt minimalista, ultrarápido e infinitamente personalizable para cualquier intérprete de comandos! Muestra la información que necesitas, a la par que es elegante y minimalista. Instalación rápida disponible para Bash, Fish, ZSH, Ion y PowerShell.'
 ---
 
 <div class="center">
@@ -35,7 +35,7 @@ description: Starship es el símbolo de sistema minimalista, ultrarápido e infi
 
    #### Instalar la última versión
 
-   Con la interfaz de línea de comandos:
+   Con el intérprete de comandos:
 
    ```sh
    curl -fsSL https://starship.rs/install.sh | bash
@@ -56,7 +56,7 @@ description: Starship es el símbolo de sistema minimalista, ultrarápido e infi
    scoop install starship
    ```
 
-1. Añade el script de inicio al archivo de configuración de tu interfaz de línea de comandos:
+1. Añade el guión de inicio al archivo de configuración de tu intérprete de comandos:
 
 
    #### Bash
@@ -110,3 +110,27 @@ description: Starship es el símbolo de sistema minimalista, ultrarápido e infi
 
    eval $(starship init ion)
    ```
+
+   #### Elvish
+
+   ::: advertencia Solo se admite Elvish v0.15 o superior. :::
+
+   Añade el siguiente código al final de `~/.elvish/rc.elv`:
+
+   ```sh
+   # ~/.elvish/rc.elv
+
+   eval (starship init elvish)
+   ```
+
+
+   #### Tcsh
+
+   Añade el siguiente código al final de `~/.tcshrc`:
+
+   ```sh
+   # ~/.tcshrc
+
+   eval `starship init tcsh`
+   ```
+

docs/es-ES/advanced-config/README.md

@@ -82,7 +82,7 @@ Las cadenas de estilo son una lista de palabras, separadas por espacios en blanc
 
 donde `<color>` es un especificador de color (discutido a continuación). `fg:<color>` y `<color>` hacen actualmente lo mismo, aunque esto puede cambiar en el futuro. El orden de las palabras en la cadena no importa.
 
-El token `none` anula todas las otras fichas en una cadena, por lo que, por ejemplo, `fg:red none fg:blue` creará una cadena sin ningún tipo de estilo. Puede convertirse en un error usar `none` junto con otros estilos en el futuro.
+El token `none` anula todos los demás tokens en una cadena si no es parte de un especificador `bg:`, de modo que por ejemplo `fg:red none fg:blue` creará una cadena sin ningún estilo. `bg:none`  establece el fondo al color por defecto, así que `fg:red bg:none` es equivalente a `red` o `fg:red` y `bg:green fg:red bg:none` también es equivalente a `fg:red` o `red`. Puede convertirse en un error usar `none` junto con otros tokens en el futuro.
 
 Un especificador de color puede ser uno de los siguientes:
 

docs/es-ES/faq/README.md

@@ -6,24 +6,24 @@
   - **Tema**: Mínimo
   - **Esquema de color**: [Snazzy](https://github.com/sindresorhus/iterm2-snazzy)
   - **Font**: [FiraCode Nerd Font](https://www.nerdfonts.com/font-downloads)
-- **Interfaz de línea de comandos**: [Fish Shell](https://fishshell.com/)
+- **Intérprete de comandos**: [Fish Shell](https://fishshell.com/)
   - **Configuración**: [archivos de configuración de matchai](https://github.com/matchai/dotfiles/blob/b6c6a701d0af8d145a8370288c00bb9f0648b5c2/.config/fish/config.fish)
   - **Prompt**: [Starship](https://starship.rs/)
 
 ## ¿Cómo obtengo el autocompletado del comando como se muestra en el GIF?
 
-El soporte de completado es proporcionado por el intérprete de órdenes elegido. En el caso de la demo, la demo se realizó con [Fish Shell](https://fishshell.com/), que proporciona el completado por defecto. Si usas Z Shell (zsh), te sugeriría echar un vistazo a [zsh-autosuggeries,](https://github.com/zsh-users/zsh-autosuggestions).
+El soporte de terminación, o autocompletado, es proporcionado por tu intérprete de comandos de elección. En el caso de la demo, la demo se realizó con [Fish Shell](https://fishshell.com/), que proporciona el completado por defecto. Si usas Z Shell (zsh), te sugerimos echar un vistazo a [zsh-autosuggeries,](https://github.com/zsh-users/zsh-autosuggestions).
 
 ## ¿`prompt_order` y `<module>.disabled` hacen lo mismo?
 
-Sí, se pueden usar ambos para desactivar los módulos en el símbolo del sistema. Si todo lo que planeas es desactivar módulos, `<module>.disabled` es el método preferido por las siguientes razones:
+Sí, se pueden usar ambos para desactivar los módulos en el prompt. Si todo lo que planeas es desactivar módulos, `<module>.disabled` es el método preferido por las siguientes razones:
 
 - Deshabilitar módulos es más explícito que omitirlos del nivel superior `format`
-- Los nuevos módulos se añadirán al símbolo del sistema en cuanto Starship se actualice
+- Los nuevos módulos se añadirán al prompt en cuanto Starship se actualice
 
-## La documentación dice que Starship es compatible con cualquier intérprete de comandos pero no soporta X Shell. ¿Por qué?
+## La documentación dice que Starship es "cross-shell". ¿Por qué no es compatible mi intérprete de comandos preferido?
 
-Por la forma en que Starshp está construído, debería ser posible añadir soporte para prácticamente cualquier intérprete de comandos. El binario de Starship es sin estado y agnóstico, por lo que mientras que tu intérprete de comandos se pueda ampliar y soporte la personalización del símbolo del sistema, puede utilizar Starship.
+Por la forma en que Starship está construído, debería ser posible añadir soporte para prácticamente cualquier intérprete de comandos. El binario de Starship es sin estado y agnóstico, por lo que mientras que tu intérprete de comandos se pueda ampliar y soporte la personalización del prompt, puedes utilizar Starship.
 
 Aquí tienes un pequeño ejemplo haciendo que Starship funcione con bash:
 
@@ -38,9 +38,9 @@ NUM_JOBS=$(jobs -p | wc -l)
 PS1="$(starship prompt --status=$STATUS --jobs=$NUM_JOBS)"
 ```
 
-La [implementación de Bash](https://github.com/starship/starship/blob/master/src/init/starship.bash) en Starship es sensíblemente is ligeramente más compleja para permitir características avanzadas como [el módulo de duración de comando](https://starship.rs/config/#Command-Duration) y para asegurar que Starship es compatible con las configuraciones preinstaladas de Bash.
+The [Bash implementation](https://github.com/starship/starship/blob/master/src/init/starship.bash) built into Starship is slightly more complex to allow for advanced features like the [Command Duration module](https://starship.rs/config/#command-duration) and to ensure that Starship is compatible with pre-installed Bash configurations.
 
-Para obtener una lista de todos los parámetros aceptados por `el símbolo del sistema starship`, usa el siguiente comando:
+Para obtener una lista de todos los parámetros aceptados por `el prompt de Starship`, usa el siguiente comando:
 
 ```sh
 starship prompt --help
@@ -56,33 +56,37 @@ Si obtienes un error como "_version 'GLIBC_2.18' not found (required by starship
 curl -fsSL https://starship.rs/install.sh | bash -s -- --platform unknown-linux-musl
 ```
 
+## Veo símbolos que no entiendo ni espero, ¿qué significan?
+
+Si ves símbolos que no reconoces, puedes usar `starship explain` para explicar los módulos que se muestran actualmente.
+
 ## ¿Por qué no veo un símbolo de glifo en mi prompt?
 
-La causa más común de esto es la mala configuración del sistema. Algunas distribuciones de Linux en particular no vienen con soporte de fuentes "listo para usare". Tienes que asegurar que:
+La causa más común de esto es la mala configuración del sistema. Algunas distribuciones de Linux en particular no vienen con soporte de fuentes listos para usarse. Tienes que garantizar que:
 
 - Tu configuración regional está establecida con un valor UTF-8, como `de_DE.UTF-8` o `ja_JP.UTF-8`. Si `LC_ALL` no es un valor UTF-8, [necesitarás cambiarlo](https://www.tecmint.com/set-system-locales-in-linux/).
 - Tienes una fuente emoji instalada. La mayoría de los sistemas vienen con una fuente emoji por defecto, pero algunos (notablemente Arch Linux) no. Generalmente puedes instalar uno a través del gestor de paquetes del sistema --[noto emoji](https://www.google.com/get/noto/help/emoji/) es una elección popular.
 - Estás usando un [Nerd Font](https://www.nerdfonts.com/).
 
-Para probar tu sistema, ejecuta los siguientes comandos en un terminal:
+Para probar tu sistema, ejecua los siguientes comandos en un terminal:
 
 ```sh
 echo -e "\xf0\x9f\x90\x8d"
 echo -e "\xee\x82\xa0"
 ```
 
-La primera línea debe producir un [emoji snake](https://emojipedia.org/snake/), mientras que la segunda debe producir un [símbolo de rama de powerline (e0a0)](https://github.com/ryanoasis/powerline-extra-symbols#glyphs).
+La primera línea debe producir un [emoji snake](https://emojipedia.org/snake/), mientras que la segunda debe producir un [símbolo de rama de Powerline(e0a0)](https://github.com/ryanoasis/powerline-extra-symbols#glyphs).
 
-Si cualquiera de los dos símbolos no se puede mostrar correctamente, tu sistema todavía está mal configurado. Desafortunadamente, obtener la configuración correcta de las fuentes es a veces difícil. Los usuarios en el Discord te pueden ayudar. Si ambos símbolos se muestran correctamente, pero todavía no los ves en starship, [¡envía un informe de error!](https://github.com/starship/starship/issues/new/choose)
+Si cualquiera de los dos símbolos no se puede mostrar correctamente, su sistema todavía está mal configurado. Desafortunadamente, obtener la configuración correcta de las fuentes es a veces difícil. Los usuarios en el Discord pueden ayudar. Si ambos símbolos se muestran correctamente, pero todavía no los ves en Starship, [¡envía un informe de error!](https://github.com/starship/starship/issues/new/choose)
 
 ## ¿Cómo puedo desinstalar Starship?
 
 Starship es tan fácil de desinstalar como de instalar en primer lugar.
 
-1. Elimina cualquier línea de tu configuración de shell (por ejemplo, `~/.bashrc`) usada para inicializar Starship.
+1. Elimina cualquier línea de tu configuración de intérprete de comandos (por ejemplo, `~/.bashrc`) usada para inicializar Starship.
 1. Elimina el binario de Starship.
 
-Si Starship fue instalado usando un gestor de paquetes, por favor refiérere a sus documentos para instrucciones de desinstalación.
+Si Starship fue instalado usando un gestor de paquetes, por favor refiérete a sus documentos para instrucciones de desinstalación.
 
 Si Starship fue instalado usando el script `curl | bash`, el siguiente comando eliminará el binario:
 

docs/es-ES/guide/README.md

@@ -2,31 +2,36 @@
   <img
     width="400"
     src="https://raw.githubusercontent.com/starship/starship/master/media/logo.png"
-    alt="Starship - Prompt multi intérprete de comandos" />
+    alt="Starship - Prompt multi-intérprete de comandos"
+ />
 </p>
 
 <p align="center">
   <a href="https://github.com/starship/starship/actions"
     ><img
       src="https://img.shields.io/github/workflow/status/starship/starship/Main workflow/master?label=workflow&style=flat-square"
-      alt="Estado del flujo de trabajo de GitHub Actions" /></a>
+      alt="Estado del flujo de trabajo de GitHub Actions"
+ /></a>
   <a href="https://crates.io/crates/starship"
     ><img
       src="https://img.shields.io/crates/v/starship?style=flat-square"
-      alt="Versión de Crates.io" /></a>
+      alt="Versión de Crates.io"
+ /></a>
   <a href="https://repology.org/project/starship/versions"
     ><img
       src="https://img.shields.io/repology/repositories/starship?label=in%20repositories&style=flat-square"
       alt="Estado de empaquetado" /></a
 ><br />
-  <a href="https://discord.gg/8Jzqu3T"
+  <a href="https://discord.gg/starship"
     ><img
       src="https://img.shields.io/discord/567163873606500352?label=discord&logoColor=white&style=flat-square"
-      alt="Chat en Discord" /></a>
+      alt="Chat en Discord"
+ /></a>
   <a href="https://twitter.com/StarshipPrompt"
     ><img
       src="https://img.shields.io/badge/twitter-@StarshipPrompt-1DA1F3?style=flat-square"
-      alt="Sigue a @StarshipPrompt en Twitter" /></a>
+      alt="Sigue a @StarshipPrompt en Twitter"
+ /></a>
 </p>
 
 <p align="center">
@@ -42,54 +47,72 @@
     ><img
       height="20"
       src="https://raw.githubusercontent.com/starship/starship/master/media/flag-us.png"
-      alt="English" /></a>
+      alt="English"
+ /></a>
   &nbsp;
   <a
     href="https://github.com/starship/starship/blob/master/docs/ja-JP/guide/README.md"
     ><img
       height="20"
       src="https://raw.githubusercontent.com/starship/starship/master/media/flag-jp.png"
-      alt="日本語" /></a>
+      alt="日本語"
+ /></a>
   &nbsp;
   <a
     href="https://github.com/starship/starship/blob/master/docs/zh-TW/guide/README.md"
     ><img
       height="20"
       src="https://raw.githubusercontent.com/starship/starship/master/media/flag-tw.png"
-      alt="繁體中文" /></a>
+      alt="繁體中文"
+ /></a>
   &nbsp;
   <a
     href="https://github.com/starship/starship/blob/master/docs/ru-RU/guide/README.md"
     ><img
       height="20"
       src="https://raw.githubusercontent.com/starship/starship/master/media/flag-ru.png"
-      alt="Русский" /></a>
+      alt="Русский"
+ /></a>
   &nbsp;
   <a
     href="https://github.com/starship/starship/blob/master/docs/de-DE/guide/README.md"
     ><img
       height="20"
       src="https://raw.githubusercontent.com/starship/starship/master/media/flag-de.png"
-      alt="Deutsch" /></a>
+      alt="Deutsch"
+ /></a>
   &nbsp;
   <a
     href="https://github.com/starship/starship/blob/master/docs/zh-CN/guide/README.md"
     ><img
       height="20"
       src="https://raw.githubusercontent.com/starship/starship/master/media/flag-cn.png"
-      alt="简体中文" /></a>
+      alt="简体中文"
+ /></a>
   &nbsp;
-  <a href="https://translate.starship.rs/project/starship-prompt/es"
+  <a 
+    href="https://github.com/starship/starship/blob/master/docs/es-ES/guide/README.md"
     ><img
       height="20"
       src="https://raw.githubusercontent.com/starship/starship/master/media/flag-es.png"
-      alt="Español" /></a>
+      alt="Español"
+ /></a>
   &nbsp;
-  <a href="https://translate.starship.rs/project/starship-prompt/fr"
+  <a 
+    href="https://github.com/starship/starship/blob/master/docs/fr-FR/guide/README.md"
     ><img
       height="20"
       src="https://raw.githubusercontent.com/starship/starship/master/media/flag-fr.png"
-      alt="Francés" /></a>
+      alt="Francés"
+ /></a>
+  &nbsp;
+  <a 
+    href="https://github.com/starship/starship/blob/master/docs/vi-VN/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-vn.png"
+      alt="Tiếng Việt"
+ /></a>
 </p>
 
 <h1></h1>
@@ -98,12 +121,11 @@
   src="https://raw.githubusercontent.com/starship/starship/master/media/demo.gif"
   alt="Starship con iTerm 2 y el tema Snazzy"
   width="50%"
-  align="right" />
-
+  align="right"
+ />
 
 **¡El prompt minimalista, ultrarápido e infinitamente personalizable para cualquier intérprete de comandos!**
 
-
 - **Rápido:** es rápido – _realmente_ rápido! 🚀
 - **Personalizable:** configura cada parte de tu prompt.
 - **Universal:** funciona en cualquier intérprete de comandos, en cualquier sistema operativo.
@@ -125,6 +147,8 @@
 
 ### Comenzar
 
+**Nota**: debido a la proliferación de diferentes plataformas, solo un subconjunto de plataformas soportadas se muestra a continuación. ¿No puedes ver el tuyo? Echa un vistazo a las [instrucciones adicionales de la plataforma](https://starship.rs/installing/).
+
 1. Instala el binario de **Starship**:
 
 
@@ -138,17 +162,10 @@
    ```
 
 
-   ##### Desde el código fuente en [crates.io](https://crates.io/):
-
-   ```sh
-   cargo install starship
-   ```
-
-
    #### Instalar con un gestor de paquetes
 
 
-   ##### Con [Homebew](https://brew.sh/):
+   ##### Ejemplo: [Homebrew](https://brew.sh/):
 
    ```sh
    brew install starship
@@ -161,7 +178,7 @@
    scoop install starship
    ```
 
-1. Añade el script de inicio al archivo de configuración de tu interfaz de línea de comandos:
+2. Añade el guión de inicio al archivo de configuración de tu intérprete de comandos:
 
 
    #### Bash
@@ -201,7 +218,7 @@
 
    Añade lo siguiente al final de `Microsoft.PowerShell_profile.ps1`. Puedes comprobar la ubicación de este archivo consultando la variable `$PROFILE` en PowerShell. Normalmente la ruta es `~\Documents\PowerShell\Microsoft.PowerShell_profile.ps1` o `~/.config/powershell/Microsoft.PowerShell_profile.ps1` en -Nix.
 
-   ```sh
+   ```powershell
    Invoke-Expression (&starship init powershell)
    ```
 
@@ -216,10 +233,34 @@
    eval $(starship init ion)
    ```
 
+
+   #### Elvish
+
+   **Advertencia** Sólo se admite Elvish v0.15 o superior. Añade el siguiente código al final de `~/.elvish/rc.elv`:
+
+   ```sh
+   # ~/.elvish/rc.elv
+
+   eval (starship init elvish)
+   ```
+
+
+   #### Tcsh
+
+   Añade el siguiente código al final de `~/.tcshrc`:
+
+   ```sh
+   # ~/.tcshrc
+
+   eval `starship init tcsh`
+   ```
+
 ## 🤝 Colaborando
 
 ¡Siempre estamos buscando colaboradores de **todos los niveles y habilidades**! Si estas buscando una manera fácil de ayudar este proyecto, puedes intentar resolver un problema con la etiqueta "[good first issue](https://github.com/starship/starship/labels/🌱%20good%20first%20issue)".
 
+Si hablas con fluidez en un idioma que no sea inglés, agradecemos mucho cualquier ayuda para mantener nuestros documentos traducidos y actualizados en otros idiomas. Si quieres ayudar, puedes contribuir con las traducciones en el [Crowdin de Starship](https://translate.starship.rs/).
+
 Si quieres ayudar a colaborar a Starship, por favor mira nuestra [Guía de Colaboradores](https://github.com/starship/starship/blob/master/CONTRIBUTING.md). Además, siéntete libre de entrar en nuestro [servidor de Discord](https://discord.gg/8Jzqu3T) y di "¡Hola!". 👋
 
 ### Desarrolladores
@@ -252,19 +293,19 @@ Apoya este proyecto con tu organización. Su logo se mostrará aquí con un enla
 
 ## 💭 Inspirado por
 
-Por favor, revisa estos proyectos que inspiraron la creación de Starship. 🙏
+Por favor, revisa estos trabajos previos que ayudaron a inspirar la creación de starship. 🙏
 
-- **[denysdovhan/spaceship-prompt](https://github.com/denysdovhan/spaceship-prompt)** - Una prompt ZSH para astronautas.
+- **[denysdovhan/spaceship-prompt](https://github.com/denysdovhan/spaceship-prompt)** - Un prompt ZSH para astronautas.
 
-- **[denysdovhan/robbyrussell-node](https://github.com/denysdovhan/robbyrussell-node)** - robbyrussel, tema multi intérprete de comandos escrito en JavaScript.
+- **[denysdovhan/robbyrussell-node](https://github.com/denysdovhan/robbyrussell-node)** - robbyrussel, tema multi-intérprete de comandos escrito en JavaScript.
 
-- **[reujab/silver](https://github.com/reujab/silver)** - Una prompt multi intérprete de comandos personalizable, basada en Powerline con iconos.
+- **[reujab/silver](https://github.com/reujab/silver)** - Un prompt multi-intérprete de comandos personalizable, basada en Powerline con iconos.
 
 <p align="center">
     <br>
-    <img width="100" src="https://raw.githubusercontent.com/starship/starship/master/media/icon.png" alt="Icono de Starship">
+    <img width="100" src="https://raw.githubusercontent.com/starship/starship/master/media/icon.png" alt="Icono de cohete de Starship">
 </p>
 
 ## 📝 Licencia
 
-Copyright © 2019-actualidad, [Creadores de Starship](https://github.com/starship/starship/graphs/contributors).<br /> Este proyecto está bajo una licencia [ISC](https://github.com/starship/starship/blob/master/LICENSE).
+Derechos de autor © 2019-presente, [Colaboradores de Starship](https://github.com/starship/starship/graphs/contributors).<br />Este proyecto está bajo una licencia [ISC](https://github.com/starship/starship/blob/master/LICENSE).

docs/es-ES/installing/README.md

@@ -0,0 +1,84 @@
+# 🚀 Instalación avanzada
+
+Para instalar Starship, necesitas hacer dos cosas:
+
+1. Consigue el binario de **Starship** en tu ordenador
+1. Decirle a tu intérprete de comandos que use el binario de Starship como su prompt modificando sus guiones de inicio
+
+Para la mayoría de los usuarios, las instrucciones en [la página principal](/guide/#🚀-installation) funcionarán genial. Sin embargo, para algunas plataformas más especializadas, se necesitan diferentes instrucciones.
+
+Hay tantas plataformas ahí fuera que no cabían en el README.md principal, así que aquí están algunas instrucciones de instalación para otras plataformas de la comunidad. ¿No está usted aquí? ¡Por favor, añádelo aquí si lo encuentras!
+
+## [Chocolatey](https://chocolatey.org)
+
+### Prerequisitos
+
+Dirígete a la página de instalación de [Chocolatey](https://chocolatey.org/install) y sigue las instrucciones para instalar Chocolatey.
+
+### Instalación
+
+```powershell
+choco install starship
+```
+
+## [termux](https://termux.com)
+
+### Prerequisitos
+
+```sh
+pkg install getconf
+```
+
+### Instalación
+
+```sh
+curl -fsSL https://starship.rs/install.sh | bash -s -- -b /data/data/com.termux/files/usr/bin
+```
+
+## [Nix](https://nixos.wiki/wiki/Nix)
+
+### Obtener el binario
+
+#### Imperativamente
+
+```sh
+nix-env -iA nixos.starship
+```
+
+#### Declarativo, usuario único, a través de [home-manager](home-manager)
+
+Activa el módulo `programs.starship` en tu archivo `home.nix` y añade tus ajustes
+
+```nix
+{
+  programs.starship = {
+    enable = true;
+    enableZshIntegration = true;
+    # Configuration written to ~/.config/starship.toml
+    settings = {
+      # add_newline = false;
+
+      # character = {
+      #   success_symbol = "[➜](bold green)";
+      #   error_symbol = "[➜](bold red)";
+      # };
+
+      # package.disabled = true;
+    };
+  };
+}
+```
+
+luego ejecutar
+
+```sh
+home-manager switch
+```
+
+#### Declarativo, en todo el sistema, con NixOS
+
+Añade `pkgs.starship` a `environment.systemPackages` en tu `configuration.nix`, luego ejecuta
+
+```sh
+sudo nixos-rebuild switch
+```

docs/es-ES/migrating-to-0.45.0/README.md

@@ -6,7 +6,7 @@ Esta guía pretende guiarle a través de los cambios de ruptura.
 
 ## `prompt_order` ha sido reemplazado por un "nivel raíz" `format`
 
-Anterioramente a v0.45.0, `prompt_order` aceptaría un array de nombres de módulos en el orden que deberían ser renderizados por Starship.
+Anterioramente a v0.45.0, `prompt_order` aceptaría un arreglo de nombres de módulos en el orden que deberían ser renderizados por Starship.
 
 En su lugar, Starship v0.45.0 acepta un valor de `format`, permitiendo la personalización del indicador fuera de los propios módulos.
 
@@ -70,7 +70,7 @@ prefix = "tomó "
 ```toml
 [cmd_duration]
 # $duration – La duración del comando (p. ej. "15s")
-# $style    – El estilo predeterminado del módulo (p. ej. "bold yellow")
+# $style    – El estilo por defecto del módulo (p. ej. "bold yellow")
 format = "tomó [$duration]($style) "
 ```
 

docs/es-ES/presets/README.md

@@ -1,12 +1,12 @@
-# Ajustes predeterminados
+# Ajustes por defecto
 
-Aqui hay una colección de ajustes predeterminados creados por la comunidad de Starship. ¡Si quieres compartir un ajuste predeterminado, por favor, [envía un PR](https://github.com/starship/starship/edit/master/docs/presets/README.md) actualizando este archivo! 😊
+Aquí hay una colección de ajustes por defecto creados por la comunidad de Starship. ¡Si quieres compartir un ajuste por defecto, por favor, [envía un PR](https://github.com/starship/starship/edit/master/docs/presets/README.md) actualizando este archivo! 😊
 
 ## Símbolos de Nerd Font
 
-Este ajuste predeterminado no modifica nada excepto los símbolos usados para cada módulo. Si los emojis no son lo tuyo, ¡esto podría llamar tu atención!
+Este ajuste por defecto no modifica nada excepto los símbolos usados para cada módulo. Si los emojis no son lo tuyo, ¡esto podría llamar tu atención!
 
-![Captura de pantalla de los ajustes predeterminados de los Símbolos de Nerd Font](/presets/nerd-font-symbols.png)
+![Captura de pantalla de los ajustes por defecto de los Símbolos de Nerd Font](/presets/nerd-font-symbols.png)
 
 ### Prerequisitos
 
@@ -18,17 +18,15 @@ Este ajuste predeterminado no modifica nada excepto los símbolos usados para ca
 [aws]
 symbol = "  "
 
-[battery]
-full_symbol = ""
-charging_symbol = ""
-discharging_symbol = ""
-
 [conda]
 symbol = " "
 
 [dart]
 symbol = " "
 
+[directory]
+read_only = " "
+
 [docker]
 symbol = " "
 
@@ -86,6 +84,9 @@ symbol = " "
 [rust]
 symbol = " "
 
+[scala]
+symbol = " "
+
 [swift]
 symbol = "ﯣ "
 ```

docs/faq/README.md

@@ -38,7 +38,7 @@ NUM_JOBS=$(jobs -p | wc -l)
 PS1="$(starship prompt --status=$STATUS --jobs=$NUM_JOBS)"
 ```
 
-The [Bash implementation](https://github.com/starship/starship/blob/master/src/init/starship.bash) built into Starship is slightly more complex to allow for advanced features like the [Command Duration module](https://starship.rs/config/#Command-Duration) and to ensure that Starship is compatible with pre-installed Bash configurations.
+The [Bash implementation](https://github.com/starship/starship/blob/master/src/init/starship.bash) built into Starship is slightly more complex to allow for advanced features like the [Command Duration module](https://starship.rs/config/#command-duration) 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:
 
@@ -56,6 +56,11 @@ If you get an error like "_version 'GLIBC_2.18' not found (required by starship)
 curl -fsSL https://starship.rs/install.sh | bash -s -- --platform unknown-linux-musl
 ```
 
+## I see symbols I don't understand or expect, what do they mean?
+
+If you see symbols that you don't recognise you can use `starship explain` to
+explain the currently showing modules.
+
 ## Why don't I see a glyph symbol in my prompt?
 
 The most common cause of this is system misconfiguration. Some Linux distros in

docs/fr-FR/README.md

@@ -110,3 +110,27 @@ description: Starship est un invite minimaliste, ultra-rapide et hautement perso
 
    eval $(starship init ion)
    ```
+
+   #### Elvish
+
+   ::: warning Only elvish v0.15 or higher is supported. :::
+
+   Add the following to the end of `~/.elvish/rc.elv`:
+
+   ```sh
+   # ~/.elvish/rc.elv
+
+   eval (starship init elvish)
+   ```
+
+
+   #### Tcsh
+
+   Add the following to the end of `~/.tcshrc`:
+
+   ```sh
+   # ~/.tcshrc
+
+   eval `starship init tcsh`
+   ```
+

docs/fr-FR/advanced-config/README.md

@@ -21,7 +21,7 @@ function blastoff(){
 starship_precmd_user_func="blastoff"
 ```
 
-- Pour exécuter une fonction personnalisée juste avant l'exécution d'une commande, vous pouvez utiliser le [` DEBUG` mécanisme d'interruption ](https://jichu4n.com/posts/debug-trap-and-prompt_command-in-bash/). Cependant, vous **devez** pièger le signal DEBUG *avant* initialisation du Starship ! Starship peut préserver la valeur du piège DEBUG, mais si le piège est écrasé après le démarrage de Starship, certaines fonctionnalités vont casser.
+- Pour exécuter une fonction personnalisée juste avant l'exécution d'une commande, vous pouvez utiliser le [` DEBUG` mécanisme d'interruption ](https://jichu4n.com/posts/debug-trap-and-prompt_command-in-bash/). Cependant, vous **devez** piéger le signal DEBUG *avant* initialisation du Starship ! Starship peut préserver la valeur du piège DEBUG, mais si le piège est écrasé après le démarrage de Starship, certaines fonctionnalités vont casser.
 
 ```bash
 function blastoff(){
@@ -45,7 +45,7 @@ function set_titre_fenetre(){
 
 Vous pouvez utiliser des variables pour personnaliser ce titre (`$USER`, `$HOSTNAME`, et `$PWD` sont des choix populaires).
 
-Dans `bash`, définissez cette fonction comme la fonction précmd Starship :
+Dans `bash`, définissez cette fonction comme la fonction precmd Starship :
 
 ```bash
 starship_precmd_user_func="set_titre_gagnante"
@@ -82,7 +82,7 @@ Les chaînes de style sont une liste de mots, séparés par des espaces. Les mot
 
 où `<color>` est un spécificateur de couleur (discuté ci-dessous). `fg:<color>` et `<color>` font actuellement la même chose, même si cela peut changer plus tard. L'ordre des mots dans le string n'a pas d'importance.
 
-Le jeton ` none ` remplace tous les autres jetons d'une string, de sorte que, par exemple, ` fg: red none fg: blue ` créera toujours une string sans style. Il peut devenir une erreur d'utiliser `none` en conjonction avec d'autres jetons dans le futur.
+The `none` token overrides all other tokens in a string if it is not part of a `bg:` specifier, so that e.g. `fg:red none fg:blue` will still create a string with no styling. `bg:none`  sets the background to the default color so `fg:red bg:none` is equivalent to `red` or `fg:red` and `bg:green fg:red bg:none` is also equivalent to `fg:red` or `red`. Il peut devenir une erreur d'utiliser `none` en conjonction avec d'autres jetons dans le futur.
 
 Un spécificateur de couleur peut être l'un des éléments suivants :
 

docs/fr-FR/faq/README.md

@@ -12,7 +12,7 @@
 
 ## Comment puis-je obtenir la complétion de commandes comme montré dans le GIF de démo?
 
-Le support de complétion est fourni par le shell de votre choix. Dans le cas de la démo, elle a été faite avec [Fish Shell](https://fishshell.com/), qui fournit des complétions par défaut. Si vous utilisez le Shell Z (zsh), vous pouvez jeter un œil à [zsh-autosuggestions](https://github.com/zsh-users/zsh-autosuggestions).
+L'aide à la complétion ou autocomplétion est fournie par le shell que vous avez choisi. Dans le cas de la démo, elle a été faite avec [Fish Shell](https://fishshell.com/), qui fournit des complétions par défaut. Si vous utilisez le Shell Z (zsh), vous pouvez jeter un œil à [zsh-autosuggestions](https://github.com/zsh-users/zsh-autosuggestions).
 
 ## Est-ce que l'option globale `format` et `<module>.disabled` font la même chose ?
 
@@ -21,7 +21,7 @@ Oui, ils peuvent tous deux être utilisés pour désactiver les modules dans l'i
 - Désactiver les modules est plus explicite que de les omettre du `format global`
 - Les modules nouvellement créés seront ajoutés à l'invite de commande au fur et à mesure que Starship sera mis à jour
 
-## La doc dit que Starship est cross-shell, mais il ne supporte pas le shell X. Pourquoi ?
+## The docs say Starship is cross-shell. Why isn't my preferred shell supported?
 
 Étant donné la façon dont Starship est construit, il devrait être possible d'ajouter le support pour pratiquement n'importe quel shell. Starship est sans état et agnostique, donc tant que votre shell supporte la personnalisation rapide et l'expansion, Starship peut être utilisé.
 
@@ -38,7 +38,7 @@ NUM_JOBS=$(jobs -p | wc -l)
 PS1="$(starship prompt --status=$STATUS --jobs=$NUM_JOBS)"
 ```
 
-L' [implémentation Bash](https://github.com/starship/starship/blob/master/src/init/starship.bash) intégrée à Starship est légèrement plus complexe pour permettre des fonctionnalités avancées comme le [module de durée de commande](https://starship.rs/config/#Command-Duration) et pour s'assurer que Starship est compatible avec les configurations Bash pré-installées.
+The [Bash implementation](https://github.com/starship/starship/blob/master/src/init/starship.bash) built into Starship is slightly more complex to allow for advanced features like the [Command Duration module](https://starship.rs/config/#command-duration) and to ensure that Starship is compatible with pre-installed Bash configurations.
 
 Pour une liste de tous les flags acceptés par `starship`, utilisez la commande suivante :
 
@@ -56,35 +56,39 @@ Si vous obtenez une erreur du type "_version 'GLIBC_2.18' not found (required by
 curl -fsSL https://starship.rs/install.sh | bash -s -- --platform unknown-linux-musl
 ```
 
-## Pourquoi ne vois-je pas de glyphe dans mon invite?
+## I see symbols I don't understand or expect, what do they mean?
 
-La cause la plus commune est la mauvaise configuration du système. Certaines distributions Linux ne sont pas équipées du support de police 'out of the box'. Vous devez vous assurer que:
+If you see symbols that you don't recognise you can use `starship explain` to explain the currently showing modules.
+
+## 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:
 
 - Votre locale est définie à une valeur UTF-8, comme `de_DE.UTF-8` ou `ja_JP.UTF-8`. Si `LC_ALL` n'est pas une valeur UTF-8, [vous aurez besoin de la modifier](https://www.tecmint.com/set-system-locales-in-linux/).
 - Vous avez une police emoji installée. La plupart des systèmes sont fournis avec une police emoji par défaut, mais certains (notamment Arch Linux) ne le font pas. Vous pouvez habituellement en installer un par le biais du gestionnaire de paquets de votre système -[noto emoji](https://www.google.com/get/noto/help/emoji/) est un choix populaire.
 - Vous utilisez une police [Nerd Font](https://www.nerdfonts.com/).
 
-Pour tester votre système, exécutez les commandes suivantes dans un terminal :
+To test your system, run the following commands in a terminal:
 
 ```sh
 echo -e "\xf0\x9f\x90\x8d"
 echo -e "\xee\x82\xa0"
 ```
 
-La première ligne doit produire un emoji [serpent](https://emojipedia.org/snake/), tandis que la seconde doit produire un symbole [de branche powerline (e0a0)](https://github.com/ryanoasis/powerline-extra-symbols#glyphs).
+The first line should produce a [snake emoji](https://emojipedia.org/snake/), while the second should produce a [powerline branch symbol (e0a0)](https://github.com/ryanoasis/powerline-extra-symbols#glyphs).
 
-Si l'un ou l'autre des symboles ne parvient pas à s'afficher correctement, votre système est toujours mal configuré. Malheureusement, il est parfois difficile d'obtenir une configuration correcte. Les utilisateurs sur Discord peuvent être en mesure d'aider. Si les deux symboles s'affichent correctement, mais vous ne les voyez toujours pas dans starship, [soumettez un rapport de bogue !](https://github.com/starship/starship/issues/new/choose)
+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!](https://github.com/starship/starship/issues/new/choose)
 
-## Comment désinstaller Starship ?
+## How do I uninstall Starship?
 
-Starship est tout aussi facile à désinstaller que d'installer.
+Starship is just as easy to uninstall as it is to install in the first place.
 
 1. Supprimez les lignes de la configuration de votre shell (par exemple `~/.bashrc`) utilisées pour initialiser Starship.
 1. Supprimer l'exécutable de Starship.
 
-Si Starship a été installé à l'aide d'un gestionnaire de paquets, veuillez vous référer à leur documentation pour les instructions de désinstallation.
+If Starship was installed using a package manager, please refer to their docs for uninstallation instructions.
 
-Si Starship a été installé en utilisant le script `curl | bash` , la commande suivante supprimera l'exécutable :
+If Starship was installed using the `curl | bash` script, the following command will delete the binary:
 
 ```sh
 # Localiser et supprimer l'exécutable de Starship

docs/fr-FR/guide/README.md

@@ -2,31 +2,36 @@
   <img
     width="400"
     src="https://raw.githubusercontent.com/starship/starship/master/media/logo.png"
-    alt="Starship – Prompt Shell multi-platformes" />
+    alt="Starship – Prompt Shell multi-platformes"
+ />
 </p>
 
 <p align="center">
   <a href="https://github.com/starship/starship/actions"
     ><img
       src="https://img.shields.io/github/workflow/status/starship/starship/Main workflow/master?label=workflow&style=flat-square"
-      alt="Statut du workflow actions GitHub" /></a>
+      alt="Statut du workflow actions GitHub"
+ /></a>
   <a href="https://crates.io/crates/starship"
     ><img
       src="https://img.shields.io/crates/v/starship?style=flat-square"
-      alt="Version Crates.io" /></a>
+      alt="Version Crates.io"
+ /></a>
   <a href="https://repology.org/project/starship/versions"
     ><img
       src="https://img.shields.io/repology/repositories/starship?label=in%20repositories&style=flat-square"
       alt="Statut du package" /></a
 ><br />
-  <a href="https://discord.gg/8Jzqu3T"
+  <a href="https://discord.gg/starship"
     ><img
       src="https://img.shields.io/discord/567163873606500352?label=discord&logoColor=white&style=flat-square"
-      alt="Discuter sur Discord" /></a>
+      alt="Discuter sur Discord"
+ /></a>
   <a href="https://twitter.com/StarshipPrompt"
     ><img
       src="https://img.shields.io/badge/twitter-@StarshipPrompt-1DA1F3?style=flat-square"
-      alt="Suivez @StarshipPrompt sur Twitter" /></a>
+      alt="Suivez @StarshipPrompt sur Twitter"
+ /></a>
 </p>
 
 <p align="center">
@@ -42,54 +47,72 @@
     ><img
       height="20"
       src="https://raw.githubusercontent.com/starship/starship/master/media/flag-us.png"
-      alt="English" /></a>
+      alt="English"
+ /></a>
   &nbsp;
   <a
     href="https://github.com/starship/starship/blob/master/docs/ja-JP/guide/README.md"
     ><img
       height="20"
       src="https://raw.githubusercontent.com/starship/starship/master/media/flag-jp.png"
-      alt="日本語" /></a>
+      alt="日本語"
+ /></a>
   &nbsp;
   <a
     href="https://github.com/starship/starship/blob/master/docs/zh-TW/guide/README.md"
     ><img
       height="20"
       src="https://raw.githubusercontent.com/starship/starship/master/media/flag-tw.png"
-      alt="繁體中文" /></a>
+      alt="繁體中文"
+ /></a>
   &nbsp;
   <a
     href="https://github.com/starship/starship/blob/master/docs/ru-RU/guide/README.md"
     ><img
       height="20"
       src="https://raw.githubusercontent.com/starship/starship/master/media/flag-ru.png"
-      alt="Русский" /></a>
+      alt="Русский"
+ /></a>
   &nbsp;
   <a
     href="https://github.com/starship/starship/blob/master/docs/de-DE/guide/README.md"
     ><img
       height="20"
       src="https://raw.githubusercontent.com/starship/starship/master/media/flag-de.png"
-      alt="Deutsch" /></a>
+      alt="Deutsch"
+ /></a>
   &nbsp;
   <a
     href="https://github.com/starship/starship/blob/master/docs/zh-CN/guide/README.md"
     ><img
       height="20"
       src="https://raw.githubusercontent.com/starship/starship/master/media/flag-cn.png"
-      alt="简体中文" /></a>
+      alt="简体中文"
+ /></a>
   &nbsp;
-  <a href="https://translate.starship.rs/project/starship-prompt/es"
+  <a 
+    href="https://github.com/starship/starship/blob/master/docs/es-ES/guide/README.md"
     ><img
       height="20"
       src="https://raw.githubusercontent.com/starship/starship/master/media/flag-es.png"
-      alt="Espagnol" /></a>
+      alt="Espagnol"
+ /></a>
   &nbsp;
-  <a href="https://translate.starship.rs/project/starship-prompt/fr"
+  <a 
+    href="https://github.com/starship/starship/blob/master/docs/fr-FR/guide/README.md"
     ><img
       height="20"
       src="https://raw.githubusercontent.com/starship/starship/master/media/flag-fr.png"
-      alt="Français" /></a>
+      alt="Français"
+ /></a>
+  &nbsp;
+  <a 
+    href="https://github.com/starship/starship/blob/master/docs/vi-VN/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-vn.png"
+      alt="Tiếng Việt"
+ /></a>
 </p>
 
 <h1></h1>
@@ -98,12 +121,11 @@
   src="https://raw.githubusercontent.com/starship/starship/master/media/demo.gif"
   alt="Starship avec iTerm2 et le thème Snazzy"
   width="50%"
-  align="right" />
-
+  align="right"
+ />
 
 **L'invite minimaliste, ultra-rapide et personnalisable à l'infini pour n'importe quel shell !**
 
-
 - **Rapide** : il est rapide - _vraiment vraiment_ rapide ! 🚀
 - **Personnalisable:** configurer chaque élément de votre invite.
 - **Universel:** fonctionne avec n'importe quel shell, sur n'importe quel système d'exploitation.
@@ -125,6 +147,8 @@
 
 ### Démarrage rapide
 
+**Note**: due to the proliferation of different platforms, only a subset of supported platforms are shown below. Can't see yours? Have a look at the [extra platform instructions](https://starship.rs/installing/).
+
 1. Installer l'exécutable **starship** :
 
 
@@ -138,17 +162,10 @@
    ```
 
 
-   ##### Depuis la source sur [crates.io](https://crates.io/):
-
-   ```sh
-   cargo install starship
-   ```
-
-
    #### Installer via le gestionnaire de paquets
 
 
-   ##### Avec [Homebrew](https://brew.sh/):
+   ##### Example: [Homebrew](https://brew.sh/):
 
    ```sh
    brew install starship
@@ -161,7 +178,7 @@
    scoop install starship
    ```
 
-1. Ajouter le script d’initialisation au fichier de configuration de votre shell:
+2. Ajouter le script d’initialisation au fichier de configuration de votre shell:
 
 
    #### Bash
@@ -199,9 +216,9 @@
 
    #### PowerShell
 
-    Ajoutez ce qui suit à la fin de `Microsoft.PowerShell_profile.ps1`. Vous pouvez vérifier l'emplacement de ce fichier en regardant la variable `$PROFILE` dans PowerShell. Typically the path is `~\Documents\PowerShell\Microsoft.PowerShell_profile.ps1` or `~/.config/powershell/Microsoft.PowerShell_profile.ps1` on -Nix.
+   Ajouter ce qui suit à la fin de `Microsoft.PowerShell_profile.ps1`. Vous pouvez vérifier l'emplacement de ce fichier en regardant la variable `$PROFILE` dans PowerShell. Typically the path is `~\Documents\PowerShell\Microsoft.PowerShell_profile.ps1` or `~/.config/powershell/Microsoft.PowerShell_profile.ps1` on -Nix.
 
-   ```sh
+   ```powershell
    Invoke-Expression (&starship init powershell)
    ```
 
@@ -216,10 +233,34 @@
    eval $(starship init ion)
    ```
 
+
+   #### Elvish
+
+   **Warning** Only elvish v0.15 or higher is supported. Add the following to the end of `~/.elvish/rc.elv`:
+
+   ```sh
+   # ~/.elvish/rc.elv
+
+   eval (starship init elvish)
+   ```
+
+
+   #### Tcsh
+
+   Add the following to the end of `~/.tcshrc`:
+
+   ```sh
+   # ~/.tcshrc
+
+   eval `starship init tcsh`
+   ```
+
 ## 🤝Contribution
 
 Nous sommes toujours à la recherche de contributeurs de **tous niveaux de compétence**! Si vous cherchez à faciliter votre entrée dans le projet, essayez un [good first issue](https://github.com/starship/starship/labels/🌱%20good%20first%20issue).
 
+If you are fluent in a non-English language, we greatly appreciate any help keeping our docs translated and up-to-date in other languages. If you would like to help, translations can be contributed on the [Starship Crowdin](https://translate.starship.rs/).
+
 Si vous êtes intéressé pour aider et contribuer à Starship, veuillez jeter un coup d'œil à notre [Guide de contribution](https://github.com/starship/starship/blob/master/CONTRIBUTING.md). Aussi, n'hésitez pas à vous rendre sur notre [serveur Discord](https://discord.gg/8Jzqu3T) pour dire bonjour. 👋
 
 ### Contributeurs
@@ -252,7 +293,7 @@ Soutenez ce projet avec votre organisation. Votre logo apparaîtra ici avec un l
 
 ## 💭Inspiré par
 
-Jetez un œil aux précédents projets qui ont inspiré la création de starship. 🙏
+Voyez ces travaux précédents qui ont contribué à inspirer la création de vaisseau. 🙏
 
 - **[denysdovhan/spaceship-prompt](https://github.com/denysdovhan/spaceship-prompt)** - Un invite de commandes ZSH pour les astronautes.
 

docs/fr-FR/installing/README.md

@@ -0,0 +1,84 @@
+# 🚀 Installation avancée
+
+Pour installer starship, vous devez faire deux choses:
+
+1. Installez le binaire **starship** sur votre ordinateur
+1. Dites à votre shell d'utiliser le binaire de starship comme invite en modifiant ses scripts d'initialisation
+
+Pour la plupart des utilisateurs, les instructions sur [la page principale](/guide/#🚀-installation) fonctionneront bien. Cependant, pour certaines plateformes plus spécialisées, des instructions différentes sont nécessaires.
+
+Il y a tellement de plates-formes, qu'il aurait été déraisonnable de les faire apparaître dans le README principal, voici donc quelques instructions d'installation supplémentaires pour celles-ci, écrient par la commaunauté. La vôtre n'est-elle pas là ? S'il vous plaît, ajoutez-la ici pour les suivants !
+
+## [Chocolatey](https://chocolatey.org)
+
+### Pré-requis
+
+Head over to the [Chocolatey installation page](https://chocolatey.org/install) and follow the instructions to install Chocolatey.
+
+### Installation
+
+```powershell
+choco install starship
+```
+
+## [termux](https://termux.com)
+
+### Pré-requis
+
+```sh
+pkg install getconf
+```
+
+### Installation
+
+```sh
+curl -fsSL https://starship.rs/install.sh | bash -s -- -b /data/data/com.termux/files/usr/bin
+```
+
+## [Nix](https://nixos.wiki/wiki/Nix)
+
+### Getting the Binary
+
+#### Impératif
+
+```sh
+nix-env -iA nixos.starship
+```
+
+#### Déclaration, utilisateur unique, via [home-manager](home-manager)
+
+Enable the `programs.starship` module in your `home.nix` file, and add your settings
+
+```nix
+{
+  programs.starship = {
+    enable = true;
+    enableZshIntegration = true;
+    # Configuration written to ~/.config/starship.toml
+    settings = {
+      # add_newline = false;
+
+      # character = {
+      #   success_symbol = "[➜](bold green)";
+      #   error_symbol = "[➜](bold red)";
+      # };
+
+      # package.disabled = true;
+    };
+  };
+}
+```
+
+then run
+
+```sh
+home-manager switch
+```
+
+#### Déclaration, au niveau du système, avec NixOS
+
+Add `pkgs.starship` to `environment.systemPackages` in your `configuration.nix`, then run
+
+```sh
+sudo nixos-rebuild switch
+```

docs/fr-FR/presets/README.md

@@ -18,17 +18,15 @@ Cette configuration ne modifie rien sauf les symboles utilisés pour chaque modu
 [aws]
 symbol = "  "
 
-[battery]
-full_symbol = ""
-charging_symbol = ""
-discharging_symbol = ""
-
 [conda]
 symbol = " "
 
 [dart]
 symbol = " "
 
+[directory]
+read_only = " "
+
 [docker]
 symbol = " "
 
@@ -86,6 +84,9 @@ symbol = " "
 [rust]
 symbol = " "
 
+[scala]
+symbol = " "
+
 [swift]
 symbol = "ﯣ "
 ```

docs/installing/README.md

@@ -0,0 +1,89 @@
+# 🚀 Advanced Installation
+
+To install starship, you need to do two things:
+
+1. Get the **starship** binary onto your computer
+1. Tell your shell to use the starship binary as its prompt by modifying its init scripts
+
+For most users, the instructions on [the main page](/guide/#🚀-installation) will work great. However,
+for some more specialized platforms, different instructions are needed.
+
+There are so many platforms out there that they didn't fit into the main
+README.md file, so here are some installation instructions for other platforms
+from the community. Is yours not here? Please do add it here if you figure it
+out!
+
+## [Chocolatey](https://chocolatey.org)
+
+### Prerequisites
+
+Head over to the [Chocolatey installation page](https://chocolatey.org/install) and follow the instructions to install Chocolatey. 
+
+### Installation
+
+```powershell
+choco install starship
+```
+
+## [termux](https://termux.com)
+
+### Prerequisites
+
+```sh
+pkg install getconf
+```
+
+### Installation
+
+```sh
+curl -fsSL https://starship.rs/install.sh | bash -s -- -b /data/data/com.termux/files/usr/bin
+```
+
+## [Nix](https://nixos.wiki/wiki/Nix)
+
+### Getting the Binary
+
+#### Imperatively
+
+```sh
+nix-env -iA nixos.starship
+```
+
+#### Declarative, single user, via [home-manager](home-manager)
+
+Enable the `programs.starship` module in your `home.nix` file, and add your settings
+
+```nix
+{
+  programs.starship = {
+    enable = true;
+    enableZshIntegration = true;
+    # Configuration written to ~/.config/starship.toml
+    settings = {
+      # add_newline = false;
+
+      # character = {
+      #   success_symbol = "[➜](bold green)";
+      #   error_symbol = "[➜](bold red)";
+      # };
+
+      # package.disabled = true;
+    };
+  };
+}
+```
+
+then run
+
+```sh
+home-manager switch
+```
+
+#### Declarative, system-wide, with NixOS
+
+Add `pkgs.starship` to `environment.systemPackages` in your `configuration.nix`,
+then run
+
+```sh
+sudo nixos-rebuild switch
+```

docs/it-IT/README.md

@@ -0,0 +1,136 @@
+---
+home: true
+heroImage: /logo.svg
+heroText:
+tagline: Il prompt minimalista, super veloce e infinitamente personalizzabile per qualsiasi shell!
+actionText: Inizia →
+actionLink: ./guide/
+features:
+  - 
+    title: Prima la compatibilità
+    details: Funziona sulle shell e sui sistemi operativi più comuni. Usalo ovunque!
+  - 
+    title: Generato in Rust
+    details: Sfrutta la velocità e sicurezza migliori di Rust, per rendere il tuo prompt il più veloce e il più affidabile.
+  - 
+    title: Personalizzabile
+    details: Ogni più piccolo dettaglio è personalizzabile a piacere, per rendere questo messaggio prompt minimalista o ricco delle funzionalità che desideri.
+footer: Licenza ISC | Copyright © 2019-present Starship Collaboratori
+#Used for the description meta tag, for SEO
+metaTitle: "Starship: Cross-Shell Prompt"
+description: Starship è il prompt minimalista, super veloce ed estremamente personalizzabile per qualsiasi shell! Mostra le informazioni di cui hai bisogno, rimanendo elegante e minimale. Installazione rapida disponibile per Bash, Fish, ZSH, Ion e PowerShell.
+---
+
+<div class="center">
+  <video class="demo-video" muted autoplay loop playsinline>
+    <source src="/demo.webm" type="video/webm">
+    <source src="/demo.mp4" type="video/mp4">
+  </video>
+</div>
+
+### Installazione Veloce
+
+1. Installa il binario **starship**:
+
+
+   #### Installa l'ultima Versione
+
+   Con Shell:
+
+   ```sh
+   curl -fsSL https://starship.rs/install.sh <unk> bash
+   ```
+
+
+   #### Installa con Package Manager
+
+   Con [Homebrew](https://brew.sh/):
+
+   ```sh
+   brew install starship
+   ```
+
+   Con [Scoop](https://scoop.sh):
+
+   ```powershell
+   scoop install starship
+   ```
+
+1. Aggiungi lo script di inizializzazione al file di configurazione della shell:
+
+
+   #### Bash
+
+   Aggiungi quanto segue alla fine di `~/.bashrc`:
+
+   ```sh
+   # ~/.bashrc
+
+   eval "$(starship init bash)"
+   ```
+
+
+   #### Fish
+
+   Aggiungi quanto segue alla fine di `~/.config/fish/config.fish`:
+
+   ```sh
+   # ~/.config/fish/config.fish
+
+   starship init fish | source
+   ```
+
+
+   #### Zsh
+
+   Aggiungi quanto segue alla fine di `~/.zshrc`:
+
+   ```sh
+   # ~/.zshrc
+
+   eval "$(starship init zsh)"
+   ```
+
+
+   #### Powershell
+
+   Aggiungi quanto segue alla fine di `Microsoft.PowerShell_profile.ps1`. Puoi controllare la posizione di questo file interrogando la variabile `$PROFILE` in PowerShell. In genere il percorso è `~\Documents\PowerShell\Microsoft.PowerShell_profile.ps1` oppure `~/.config/powershell/Microsoft.PowerShell_profile.ps1` in -Nix.
+
+   ```sh
+   Invoke-Expression (&starship init powershell)
+   ```
+
+
+   #### Ion
+
+   Aggiungi quanto segue alla fine di `~/.config/ion/initrc`:
+
+   ```sh
+   # ~/.config/ion/initrc
+
+   eval $(starship init ion)
+   ```
+
+   #### Elvish
+
+   ::: warning Only elvish v0.15 or higher is supported. :::
+
+   Aggiungi quanto segue alla fine di `~/.elvish/rc.elv`:
+
+   ```sh
+   # ~/.elvish/rc.elv
+
+   eval (starship init elvish)
+   ```
+
+
+   #### Tcsh
+
+   Aggiungi quanto segue alla fine di `~/.tcshrc`:
+
+   ```sh
+   # ~/.tcshrc
+
+   eval `starship init tcsh`
+   ```
+

docs/it-IT/advanced-config/README.md

@@ -0,0 +1,93 @@
+# Configurazione Avanzata
+
+Nonostante Starship sia una shell versatile, a volte devi fare qualche modifica in più in `starship.toml` per ottenere alcune cose. Questa pagina descrive alcune tecniche di configurazione avanzate utilizzate in Starship.
+
+::: Attenzione
+
+Le configurazioni in questa sezione sono soggette a modifiche nelle future versioni di Starship.
+
+:::
+
+## Comandi personalizzati di pre-prompt e pre-esecuzione per Bash
+
+Bash non ha un framework preexec/precmd formale come la maggior parte delle altre shell. Per questo motivo, è difficile fornire hook completamente personalizzabile in `bash`. Tuttavia, Starship dà la limitata possibilità di inserire le tue funzioni nella procedura prompt-rendering:
+
+- Per eseguire una funzione personalizzata a destra del prompt prima che venga disegnato, definisci una nuova funzione e assegna il suo nome a `starship_precmd_user_func`. Per esempio, per visualizzare l'icona di un razzo prima del prompt, si può usare il codice seguente
+
+```bash
+function blastoff(){
+    echo "🚀"
+}
+starship_precmd_user_func="blastoff"
+```
+
+- Per eseguire una funzione personalizzata prima dell'esecuzione di un comando, è possibile utilizzare il meccanismo trappola [`DEBUG`](https://jichu4n.com/posts/debug-trap-and-prompt_command-in-bash/). Tuttavia, **devi** intrappolare il segnale DEBUG *prima di* inizializzare Starship! Starship può preservare il valore trappola di DEBUG, ma se la trappola viene sovrascritta dopo l'avvio di Starship, alcune funzionalità non funzioneranno.
+
+```bash
+function blastoff(){
+    echo "🚀"
+}
+trap blastoff DEBUG # Trap DEBUG *prima* di eseguire starship
+eval $(starship bash)
+```
+
+## Cambia il titolo della finestra
+
+Alcune shell prompt cambieranno automaticamente il titolo della finestra (ad esempio per riflettere la directory di lavoro). Fish lo fa per impostazione predefinita. Starship non lo fa, ma è abbastanza semplice aggiungere questa funzionalità a `bash` o `zsh`.
+
+Innanzitutto, bisogna definire una funzione per il cambio del titolo della finestra (identica sia per bash che zsh):
+
+```bash
+function set_win_title(){
+    echo -ne "\033]0; IL_TUO_TITOLO_QUI \007"
+}
+```
+
+Puoi usare delle variabili per personalizzare questo titolo (`$USER`, `$HOSTNAME`, e `$PWD` sono le scelte più popolari).
+
+In `bash`, impostare questa funzione per essere la precmd Starship function:
+
+```bash
+starship_precmd_user_func="set_win_title"
+```
+
+In `zsh`, aggiungi questo `precmd_functions` all'array:
+
+```bash
+precmd_functions+=(set_win_title)
+```
+
+Se ti piace il risultato, aggiungi queste righe al tuo file shell di configurazione (`~/. ashrc` o `~/.zshrc`) per renderlo permanente.
+
+Ad esempio, se desideri visualizzare la directory corrente nel titolo della scheda del terminale, aggiungi la seguente snippet al tuo `~/. ashrc` or `~/.zshrc`:
+
+```bash
+function set_win_title(){
+    echo -ne "\033]0; $(basename $PWD) \007"
+}
+starship_precmd_user_func="set_win_title"
+```
+
+## Stringhe di stile
+
+Le stringhe di stile sono un elenco di parole, separate da spazi bianchi. Le parole non sono sensibili alle maiuscole (cioè `grassetto` e `BoLd` sono considerate la stessa stringa). Ogni parola può essere una delle seguenti:
+
+  - `bold`
+  - `underline`
+  - `dimmed`
+  - `bg:<color>`
+  - `fg:<color>`
+  - `<color>`
+  - `none`
+
+dove `<color>` è un colore specifico (discusso in seguito). `fg:<color>` e `<color>` attualmente fanno la stessa cosa , anche se questo potrebbe cambiare in futuro. L'ordine delle parole nella stringa non conta.
+
+Il token `none` sovrascrive tutti gli altri token in una stringa se non fa parte di uno specificatore `bg:`, così ad esempio `fg:red none fg:blue` creerà una stringa senza stile. `bg:none` imposta come colore di sfondo quello predefinito così `fg:red bg:none` è equivalente a `red` o `fg:red` e `bg:green fg:red bg:none` è equivalente a `fg:red` o `rosso`. Potrà diventare un errore usare `nessuno` in combinazione con altri token in futuro.
+
+Uno colore specifico può essere uno di questi:
+
+ - Uno dei colori standard del terminale: `nero`, `rosso`, `verde`, `blu`, `giallo`, `viola`, `ciano`, `bianco`. Puoi eventualmente utilizzare il prefisso `bright-` per ottenere la versione luminosa (es. `bright-white`).
+ - Un `#` seguito da un valore esadecimale a sei cifre. Questo specifica un [colore esagesimale in RGB](https://www.w3schools.com/colors/colors_hexadecimal.asp).
+ - Un numero compreso tra 0-255. Specifica un [codice colore ANSI a 8 bit](https://i.stack.imgur.com/KTSQa.png).
+
+Se sono specificati più colori per il primo piano/sfondo, l'ultimo nella stringa avrà la priorità.

docs/it-IT/faq/README.md

@@ -0,0 +1,96 @@
+# FAQ
+
+## Qual è la configurazione utilizzata nella GIF demo?
+
+- **Terminale Emulato**: [iTerm2](https://iterm2.com/)
+  - **Tema**: Minimale
+  - **Schema Colore**: [Snazzy](https://github.com/sindresorhus/iterm2-snazzy)
+  - **Font**: [FiraCode Nerd Font](https://www.nerdfonts.com/font-downloads)
+- **Shell**: [Fish Shell](https://fishshell.com/)
+  - **Configurazione**: [matchai Dotfiles](https://github.com/matchai/dotfiles/blob/b6c6a701d0af8d145a8370288c00bb9f0648b5c2/.config/fish/config.fish)
+  - **Chiedi**: [Starship](https://starship.rs/)
+
+## Come posso ottenere il completamento dei comandi come mostrato nella GIF demo?
+
+Completion support, or autocomplete, is provided by your shell of choice. Nel caso della demo, la demo è stata fatta con [Fish Shell](https://fishshell.com/), che fornisce i completamenti per impostazione predefinita. Se usi Z Shell (zsh), ti suggerirei di dare un'occhiata a [zsh-autosuggestions](https://github.com/zsh-users/zsh-autosuggestions).
+
+## Il formato di primo livello `` e `<module>.disabled` fanno la stessa cosa?
+
+Sì, entrambi possono essere utilizzati per disabilitare i moduli nel prompt. Se tutto quello che pensi di fare è disabilitare i moduli, `<module>.disabled` è il modo preferito per per queste ragioni:
+
+- Disabilitare i moduli è più esplicito che ometterli dal primo `formato` di livello
+- I nuovi moduli creati saranno aggiunti al prompt come Starship viene aggiornato
+
+## The docs say Starship is cross-shell. Why isn't my preferred shell supported?
+
+Il modo in cui Starship è costruito, dovrebbe rendere possibile aggiungere il supporto per qualsiasi shell. Il binario di Starship è apolide e indipendente dalla shell, fino a quando la tua shell supporterà prompt personalizzati, Starship può essere utilizzato.
+
+Ecco un piccolo esempio per avere Starship lavorando con bash:
+
+```sh
+# Ottenere lo status code dall'ultimo comando eseguito
+STATUS=$?
+
+# Ottieni il numero di processi in esecuzione.
+NUM_JOBS=$(jobs -p | wc -l)
+
+# Imposta il prompt come output di `starship prompt`
+PS1="$(starship prompt --status=$STATUS --jobs=$NUM_JOBS)"
+```
+
+The [Bash implementation](https://github.com/starship/starship/blob/master/src/init/starship.bash) built into Starship is slightly more complex to allow for advanced features like the [Command Duration module](https://starship.rs/config/#command-duration) and to ensure that Starship is compatible with pre-installed Bash configurations.
+
+Per un elenco di tutti i flag accettati da `starship prompt`, utilizzare il seguente comando:
+
+```sh
+starship prompt --help
+```
+
+The prompt will use as much context as is provided, but no flags are "required".
+
+## Come faccio a eseguire le distribuzioni Starship su Linux con vecchie versioni di glibc?
+
+Se si ottiene un errore come "_versione 'GLIBC_2. 8' non trovato (richiesta da Starship)_" quando si utilizza il binario precostruito (per esempio, su CentOS 6 o 7), puoi usare un binario compilato con `musl` invece di `glibc`:
+
+```sh
+curl -fsSL https://starship.rs/install.sh | bash -s -- --platform unknown-linux-musl
+```
+
+## I see symbols I don't understand or expect, what do they mean?
+
+If you see symbols that you don't recognise you can use `starship explain` to explain the currently showing modules.
+
+## 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:
+
+- In locale sia impostato un valore UTF-8, come `de_DE.UTF-8` o `ja_JP.UTF-8`. Se `LC_ALL` non è un valore UTF-8, [dovrai cambiarlo](https://www.tecmint.com/set-system-locales-in-linux/).
+- Hai un font emoji installato. La maggior parte dei sistemi ha un font emoji per impostazione predefinita, ma alcuni (in particolare Arch Linux) non lo fanno. Di solito puoi installarne uno attraverso il gestore dei pacchetti del tuo sistema-[noto emoji](https://www.google.com/get/noto/help/emoji/) è uno dei popolari.
+- Stai usando un [font Nerd](https://www.nerdfonts.com/).
+
+To test your system, run the following commands in a terminal:
+
+```sh
+echo -e "\xf0\x9f\x90\x8d"
+echo -e "\xee\x82\xa0"
+```
+
+The first line should produce a [snake emoji](https://emojipedia.org/snake/), while the second should produce a [powerline branch symbol (e0a0)](https://github.com/ryanoasis/powerline-extra-symbols#glyphs).
+
+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!](https://github.com/starship/starship/issues/new/choose)
+
+## How do I uninstall Starship?
+
+Starship is just as easy to uninstall as it is to install in the first place.
+
+1. Rimuovi qualsiasi riga utilizzata per inizializzare Starship nella configurazione della tua shell (ad es. `~/.bashrc`).
+1. Elimina il binario di Starship.
+
+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:
+
+```sh
+# Individua ed elimina il binario di Starship
+rm "$(che starship)"
+```

docs/it-IT/guide/README.md

@@ -0,0 +1,311 @@
+<p align="center">
+  <img
+    width="400"
+    src="https://raw.githubusercontent.com/starship/starship/master/media/logo.png"
+    alt="Starship: Cross-Shell Prompt"
+ />
+</p>
+
+<p align="center">
+  <a href="https://github.com/starship/starship/actions"
+    ><img
+      src="https://img.shields.io/github/workflow/status/starship/starship/Main workflow/master?label=workflow&style=flat-square"
+      alt="GitHub Actions workflow status"
+ /></a>
+  <a href="https://crates.io/crates/starship"
+    ><img
+      src="https://img.shields.io/crates/v/starship?style=flat-square"
+      alt="Versione Crates.io"
+ /></a>
+  <a href="https://repology.org/project/starship/versions"
+    ><img
+      src="https://img.shields.io/repology/repositories/starship?label=in%20repositories&style=flat-square"
+      alt="Stato del pacchetto" /></a
+><br />
+  <a href="https://discord.gg/starship"
+    ><img
+      src="https://img.shields.io/discord/567163873606500352?label=discord&logoColor=white&style=flat-square"
+      alt="Chat su Discord"
+ /></a>
+  <a href="https://twitter.com/StarshipPrompt"
+    ><img
+      src="https://img.shields.io/badge/twitter-@StarshipPrompt-1DA1F3?style=flat-square"
+      alt="Segui @StarshipPrompt su Twitter"
+ /></a>
+</p>
+
+<p align="center">
+  <a href="https://starship.rs">Sito web</a>
+  ·
+  <a href="#🚀-installation">Installazione</a>
+  ·
+  <a href="https://starship.rs/config/">Configurazione</a>
+</p>
+
+<p align="center">
+  <a href="https://github.com/starship/starship/blob/master/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-us.png"
+      alt="Inglese"
+ /></a>
+  &nbsp;
+  <a
+    href="https://github.com/starship/starship/blob/master/docs/ja-JP/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-jp.png"
+      alt="日本語"
+ /></a>
+  &nbsp;
+  <a
+    href="https://github.com/starship/starship/blob/master/docs/zh-TW/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-tw.png"
+      alt="繁體中文"
+ /></a>
+  &nbsp;
+  <a
+    href="https://github.com/starship/starship/blob/master/docs/ru-RU/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-ru.png"
+      alt="Russo"
+ /></a>
+  &nbsp;
+  <a
+    href="https://github.com/starship/starship/blob/master/docs/de-DE/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-de.png"
+      alt="Tedesco"
+ /></a>
+  &nbsp;
+  <a
+    href="https://github.com/starship/starship/blob/master/docs/zh-CN/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-cn.png"
+      alt="简体中文"
+ /></a>
+  &nbsp;
+  <a 
+    href="https://github.com/starship/starship/blob/master/docs/es-ES/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-es.png"
+      alt="Spagnolo"
+ /></a>
+  &nbsp;
+  <a 
+    href="https://github.com/starship/starship/blob/master/docs/fr-FR/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-fr.png"
+      alt="Francese"
+ /></a>
+  &nbsp;
+  <a 
+    href="https://github.com/starship/starship/blob/master/docs/vi-VN/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-vn.png"
+      alt="Tiếng Việt"
+ /></a>
+</p>
+
+<h1></h1>
+
+<img
+  src="https://raw.githubusercontent.com/starship/starship/master/media/demo.gif"
+  alt="Starship con iTerm2 e il tema Snazzy"
+  width="50%"
+  align="right"
+ />
+
+**Il prompt minimalista, super veloce e infinitamente personalizzabile per qualsiasi shell!**
+
+- **Velocità:** è veloce – _davvero_ veloce! 🚀
+- **Personalizzabile:** configura ogni aspetto del tuo prompt.
+- **Universale:** funziona su qualsiasi shell, con qualsiasi sistema operativo.
+- **Intelligente:** mostra le informazioni rilevanti a colpo d'occhio.
+- **Ricco di funzionalità:** supporta tutti i tuoi strumenti preferiti.
+- **Facile:** veloce da installare - inizia ad usarlo in pochi minuti.
+
+<p align="center">
+<a href="https://starship.rs/config/"><strong>Esplora la documentazione di Starship&nbsp;&nbsp;▶</strong></a>
+</p>
+
+<a name="🚀-installation"></a>
+
+## 🚀 Installazione
+
+### Prerequisiti
+
+- Un [Nerd Font](https://www.nerdfonts.com/) installato e abilitato nel tuo terminale (per esempio, prova [Fira Code Nerd Font](https://www.nerdfonts.com/font-downloads)).
+
+### Inizia
+
+**Nota**: a causa della proliferazione di piattaforme diverse, un sottoinsieme di piattaforme supportate sono mostrate di seguito. Non riesci a vedere la tua? Dai un'occhiata alle [istruzioni aggiuntive della piattaforma](https://starship.rs/installing/).
+
+1. Installa il binario **starship**:
+
+
+   #### Installa l'ultima Versione
+
+
+   ##### Da un binario precompilato, con Shell:
+
+   ```sh
+   curl -fsSL https://starship.rs/install.sh | bash
+   ```
+
+
+   #### Installa via Package Manager
+
+
+   ##### Esempio: [Homebrew](https://brew.sh/):
+
+   ```sh
+   brew install starship
+   ```
+
+
+   ##### Con [Scoop](https://scoop.sh):
+
+   ```powershell
+   scoop install starship
+   ```
+
+2. Aggiungi lo script di inizializzazione al file di configurazione della shell:
+
+
+   #### Bash
+
+   Aggiungi quanto segue alla fine di `~/.bashrc`:
+
+   ```sh
+   # ~/.bashrc
+
+   eval "$(starship init bash)"
+   ```
+
+
+   #### Fish
+
+   Aggiungi quanto segue alla fine di `~/.config/fish/config.fish`:
+
+   ```sh
+   # ~/.config/fish/config.fish
+
+   starship init fish | source
+   ```
+
+
+   #### Zsh
+
+   Aggiungi quanto segue alla fine di `~/.zshrc`:
+
+   ```sh
+   # ~/.zshrc
+
+   eval "$(starship init zsh)"
+   ```
+
+
+   #### PowerShell
+
+   Aggiungi quanto segue alla fine di `Microsoft.PowerShell_profile.ps1`. Puoi controllare la posizione di questo file interrogando la variabile `$PROFILE` in PowerShell. Tipicamente il percorso è `~\Documents\PowerShell\Microsoft.PowerShell_profile.ps1` oppure `~/.config/powershell/Microsoft.PowerShell_profile.ps1` su -Nix.
+
+   ```powershell
+   Invoke-Expression (&starship init powershell)
+   ```
+
+
+   #### Ion
+
+   Aggiungi quanto segue alla fine di `~/.config/ion/initrc`:
+
+   ```sh
+   # ~/.config/ion/initrc
+
+   eval $(starship init ion)
+   ```
+
+
+   #### Elvish
+
+   **Attenzione** È supportato solo elvish v0.15 o superiore. Aggiungi quanto segue alla fine di `~/.elvish/rc.elv`:
+
+   ```sh
+   # ~/.elvish/rc.elv
+
+   eval (starship init elvish)
+   ```
+
+
+   #### Tcsh
+
+   Aggiungi quanto segue alla fine di `~/.tcshrc`:
+
+   ```sh
+   # ~/.tcshrc
+
+   eval `starship init tcsh`
+   ```
+
+## 🤝 Contribuire
+
+Siamo sempre alla ricerca di collaboratori di **tutti i livelli**! Se stai cercando di entrare facilmente nel progetto, prova un [buon primo problema](https://github.com/starship/starship/labels/🌱%20good%20first%20issue).
+
+Se parli correntemente una lingua diversa dall'inglese, apprezziamo molto qualsiasi aiuto per mantenere i nostri documenti tradotti e aggiornati in altre lingue. Se desideri collaborare, le traduzioni possono essere fornite su [Starship Crowdin](https://translate.starship.rs/).
+
+Se sei interessato ad aiutare a contribuire a Starship, dai un'occhiata alla nostra [Guida al Contributo](https://github.com/starship/starship/blob/master/CONTRIBUTING.md). Inoltre, sentiti libero di entrare nel nostro [server Discord](https://discord.gg/8Jzqu3T) e dire ciao. 👋
+
+### Contributori di codice
+
+Questi progetto esiste grazie a tutte le persone che contribuiscono. [[Contributo](https://github.com/starship/starship/blob/master/CONTRIBUTING.md)].
+<a href="https://github.com/starship/starship/graphs/contributors"><img src="https://opencollective.com/starship/contributors.svg?width=890&button=false" /></a>
+
+### Contributori Finanziari
+
+Diventa un contributore finanziario e aiutaci a sostenere la nostra comunità. [[Contribuisci](https://opencollective.com/starship/contribute)]
+
+#### Privati
+
+<a href="https://opencollective.com/starship"><img src="https://opencollective.com/starship/individuals.svg?width=890"></a>
+
+#### Organizzazioni
+
+Supporta questo progetto con la tua organizzazione. Il tuo logo apparirà qui con un link al tuo sito web. [[Contribuisci](https://opencollective.com/starship/contribute)]
+
+<a href="https://opencollective.com/starship/organization/0/website"><img src="https://opencollective.com/starship/organization/0/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/1/website"><img src="https://opencollective.com/starship/organization/1/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/2/website"><img src="https://opencollective.com/starship/organization/2/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/3/website"><img src="https://opencollective.com/starship/organization/3/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/4/website"><img src="https://opencollective.com/starship/organization/4/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/5/website"><img src="https://opencollective.com/starship/organization/5/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/6/website"><img src="https://opencollective.com/starship/organization/6/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/7/website"><img src="https://opencollective.com/starship/organization/7/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/8/website"><img src="https://opencollective.com/starship/organization/8/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/9/website"><img src="https://opencollective.com/starship/organization/9/avatar.svg"></a>
+
+## 💭 Ispirato Da
+
+Ti invito di controllare questi lavori precedenti che hanno contribuito a ispirare la creazione di Starship. 🙏
+
+- **[denysdovhan/spaceship-prompt](https://github.com/denysdovhan/spaceship-prompt)** - Un prompt ZSH per astronauti.
+
+- **[denysdovhan/robbyrussell-node](https://github.com/denysdovhan/robbyrussell-node)** - Tema robbyrussell Cross-shell scritto in JavaScript.
+
+- **[reujab/silver](https://github.com/reujab/silver)** - Un prompt multi-shell personalizzabile powerline-like con icone.
+
+<p align="center">
+    <br>
+    <img width="100" src="https://raw.githubusercontent.com/starship/starship/master/media/icon.png" alt="Starship rocket icon">
+</p>
+
+## 📝 Licenza
+
+Copyright © 2019-presente, [Starship Contributors](https://github.com/starship/starship/graphs/contributors).<br /> Questo progetto è sotto licenza [ISC](https://github.com/starship/starship/blob/master/LICENSE).

docs/it-IT/installing/README.md

@@ -0,0 +1,84 @@
+# 🚀 Advanced Installation
+
+To install starship, you need to do two things:
+
+1. Get the **starship** binary onto your computer
+1. Tell your shell to use the starship binary as its prompt by modifying its init scripts
+
+For most users, the instructions on [the main page](/guide/#🚀-installation) will work great. However, for some more specialized platforms, different instructions are needed.
+
+There are so many platforms out there that they didn't fit into the main README.md file, so here are some installation instructions for other platforms from the community. Is yours not here? Please do add it here if you figure it out!
+
+## [Chocolatey](https://chocolatey.org)
+
+### Prerequisiti
+
+Head over to the [Chocolatey installation page](https://chocolatey.org/install) and follow the instructions to install Chocolatey.
+
+### Installation
+
+```powershell
+choco install starship
+```
+
+## [termux](https://termux.com)
+
+### Prerequisiti
+
+```sh
+pkg install getconf
+```
+
+### Installation
+
+```sh
+curl -fsSL https://starship.rs/install.sh | bash -s -- -b /data/data/com.termux/files/usr/bin
+```
+
+## [Nix](https://nixos.wiki/wiki/Nix)
+
+### Getting the Binary
+
+#### Imperatively
+
+```sh
+nix-env -iA nixos.starship
+```
+
+#### Declarative, single user, via [home-manager](home-manager)
+
+Enable the `programs.starship` module in your `home.nix` file, and add your settings
+
+```nix
+{
+  programs.starship = {
+    enable = true;
+    enableZshIntegration = true;
+    # Configuration written to ~/.config/starship.toml
+    settings = {
+      # add_newline = false;
+
+      # character = {
+      #   success_symbol = "[➜](bold green)";
+      #   error_symbol = "[➜](bold red)";
+      # };
+
+      # package.disabled = true;
+    };
+  };
+}
+```
+
+then run
+
+```sh
+home-manager switch
+```
+
+#### Declarative, system-wide, with NixOS
+
+Add `pkgs.starship` to `environment.systemPackages` in your `configuration.nix`, then run
+
+```sh
+sudo nixos-rebuild switch
+```

docs/it-IT/migrating-to-0.45.0/README.md

@@ -0,0 +1,267 @@
+# Migrazione alla versione 0.45.0
+
+Starship v0.45.0 è una versione contenente importanti cambiamenti in preparazione della grande versione 1.0.0. Abbiamo apportato alcuni importanti cambiamenti per come la configurazione viene fatta sul prompt, al fine di consentire un maggior grado di personalizzazione.
+
+Questa guida è destinata ad attraversare questi grandi cambiamenti.
+
+## `prompt_order` è stato sostituito da un formato root-level ``
+
+Previously to v0.45.0, `prompt_order` would accept an array of module names in the order which they should be rendered by Starship.
+
+Starship v0.45.0 invece accetta un valore `format`, consentendo la personalizzazione del prompt al di fuori dei moduli stessi.
+
+**Esempio di configurazione pre-v0.45.0**
+
+```toml
+prompt_order = [
+  "username",
+  "hostname",
+  "directory",
+  "git_branch",
+  "git_commit",
+  "git_state",
+  "git_status",
+  "cmd_duration",
+  "custom",
+  "line_break",
+  "jobs",
+  "battery",
+  "time",
+  "character",
+]
+```
+
+**Esempio di configurazione v0.45.0**
+
+```toml
+format = """\
+  $username\
+  $hostname\
+  $directory\
+  $git_branch\
+  $git_commit\
+  $git_state\
+  $git_status\
+  $cmd_duration\
+  $custom\
+  $line_break\
+  $jobs\
+  $battery\
+  $time\
+  $character\
+  """
+```
+
+## Il prefisso `del modulo` e il suffisso `` sono stati sostituiti dal formato ``
+
+Precedentemente la v0.45.0, alcuni moduli accetterebbero `prefisso` e/o `suffisso` per stilare il modo in cui i moduli vengono renderizzati.
+
+Starship v0.45.0 invece accetta un valore `format`, consentendo la personalizzazione del prompt al di fuori dei moduli stessi. Invece di definire un prefisso e un suffisso per le variabili basate sul contesto, le variabili possono ora essere sostituite da una stringa di formato, che rappresenta l'output del modulo.
+
+**Esempio di configurazione pre-v0.45.0**
+
+```toml
+[cmd_duration]
+prefisso = "tak"
+```
+
+**Esempio di configurazione v0.45.0**
+
+```toml
+[cmd_duration]
+# $duration – The command duration (e.g. "15s")
+# $style    – The default style of the module (e.g. "bold yellow")
+format = "took [$duration]($style) "
+```
+
+### Moduli soggetti
+
+#### Character
+
+| Proprietà rimossa       | Sostituta        |
+| ----------------------- | ---------------- |
+| `symbol`                | `success_symbol` |
+| `use_symbol_for_status` | `error_symbol`   |
+| `style_success`         | `success_symbol` |
+| `style_failure`         | `error_symbol`   |
+
+**Modifiche alla configurazione predefinita**
+
+```diff
+[character]
+-- symbol = "❯"
+-- error_symbol = "✖"
+-- use_symbol_for_status = true
+-- vicmd_symbol = "❮"
+++ success_symbol = "[❯](bold green)"
+++ error_symbol = "[❯](bold red)"
+++ vicmd_symbol = "[❮](bold green)"
+```
+
+Precedentemente, la proprietà `use_symbol_for_status` è stata utilizzata per configurare il prompt per mostrare `error_symbol` quando l'ultimo comando ha prodotto un codice di stato diverso da zero.
+
+Con il rilascio di v0.45.0, ora usiamo sempre `error_symbol` dopo codici di stato diversi da zero, unificando le proprietà `use_symbol_for_status` e `error_symbol`.
+
+Per configurare il prompt al fine di usare la vecchia configurazione `use_symbol_for_status = true`, aggiungi quanto segue al tuo file di configurazione:
+
+```toml
+[character]
+error_symbol = "[✖](bold red)"
+```
+
+*Nota:* L'elemento `carattere` aggiunge dopo automaticamente uno spazio, quindi a differenza delle altre stringhe `formato`, non ne aggiungiamo uno specificamente agli esempi di cui sopra.
+
+#### Command Duration
+
+| Proprietà rimossa | Sostituta |
+| ----------------- | --------- |
+| `prefix`          | `format`  |
+
+**Modifiche alla configurazione predefinita**
+
+```diff
+[cmd_duration]
+-- prefix = "took "
+++ format = "took [$duration]($style) "
+```
+
+#### Directory
+
+| Proprietà rimossa | Sostituta |
+| ----------------- | --------- |
+| `prefix`          | `format`  |
+
+**Modifiche alla configurazione predefinita**
+
+```diff
+[directory]
+-- prefix = "in "
+++ format = "[$path]($style)[$read_only]($read_only_style) "
+```
+
+#### Variabili di ambiente
+
+| Proprietà rimossa | Sostituta |
+| ----------------- | --------- |
+| `prefix`          | `format`  |
+| `suffix`          | `format`  |
+
+**Modifiche alla configurazione predefinita**
+
+```diff
+[env_var]
+-- prefix = ""
+-- suffix = ""
+++ format = "with [$env_value]($style) "
+```
+
+#### Git Commit
+
+| Proprietà rimossa | Sostituta |
+| ----------------- | --------- |
+| `prefix`          | `format`  |
+| `suffix`          | `format`  |
+
+**Modifiche alla configurazione predefinita**
+
+```diff
+[git_commit]
+-- prefix = "("
+-- suffix = ")"
+++ format = '[\($hash\)]($style) '
+```
+
+#### Git Status
+
+| Proprietà rimossa | Sostituta |
+| ----------------- | --------- |
+| `prefix`          | `format`  |
+| `suffix`          | `format`  |
+| `show_sync_count` | `format`  |
+
+**Modifiche alla configurazione predefinita**
+
+```diff
+[git_status]
+-- prefix = "["
+-- suffix = "]"
+-- show_sync_count = false
+++ format = '([\[$all_status$ahead_behind\]]($style) )'
+```
+
+Precedentemente, la proprietà `show_sync_count` è stata utilizzata per configurare il prompt per mostrare il numero di commit che il ramo era avanti o dietro il ramo in remoto.
+
+Con il rilascio della v0.45.0, questo è stato sostituito con tre proprietà separate, `ahead`, ` behind` e `diverged`.
+
+Per configurare il prompt al fine di usare la vecchia configurazione `show_sync_count = true`, aggiungi quanto segue al tuo file di configurazione:
+
+```toml
+[git_status]
+ahead = "⇡${count}"
+diverged = "⇕⇡${ahead_count}⇣${behind_count}"
+behind = "⇣${count}"
+```
+
+#### Hostname
+
+| Proprietà rimossa | Sostituta |
+| ----------------- | --------- |
+| `prefix`          | `format`  |
+| `suffix`          | `format`  |
+
+**Modifiche alla configurazione predefinita**
+
+```diff
+[hostname]
+-- prefix = ""
+-- suffix = ""
+++ format = "[$hostname]($style) in "
+```
+
+#### Singolarità
+
+| Proprietà rimossa | Sostituta |
+| ----------------- | --------- |
+| `label`           | `format`  |
+| `prefix`          | `format`  |
+| `suffix`          | `format`  |
+
+**Modifiche alla configurazione predefinita**
+
+```diff
+[singularity]
+-- prefix = ""
+-- suffix = ""
+++ format = '[$symbol\[$env\]]($style) '
+```
+
+#### Time
+
+| Proprietà rimossa | Sostituta     |
+| ----------------- | ------------- |
+| `format`          | `time_format` |
+
+**Modifiche alla configurazione predefinita**
+
+```diff
+[time]
+-- format = "🕙[ %T ]"
+++ time_format = "%T"
+++ format = "at 🕙[$time]($style) "
+```
+
+#### Comandi Personalizzati
+
+| Proprietà rimossa | Sostituta |
+| ----------------- | --------- |
+| `prefix`          | `format`  |
+| `suffix`          | `format`  |
+
+**Modifiche alla configurazione predefinita**
+
+```diff
+[custom.example]
+-- prefix = ""
+-- suffix = ""
+++ format = "[$symbol$output]($style) "
+```

docs/it-IT/presets/README.md

@@ -0,0 +1,92 @@
+# Preset
+
+Ecco una raccolta dei preset di configurazione inviati dalla community per Starship. Se hai un preset da condividere, per favore [ invia un PR ](https://github.com/starship/starship/edit/master/docs/presets/README.md) aggiornando questo file! 😊
+
+## Nerd Font Symbols
+
+Questo preset non cambia nulla tranne i simboli utilizzati per ogni modulo. Se gli emoji non fanno per te, questo potrebbe attirare la tua attenzione!
+
+![Screenshot dei preset di Nerd Font Symbols](/presets/nerd-font-symbols.png)
+
+### Prerequisiti
+
+- Un [ Nerd Font ](https://www.nerdfonts.com/) installato e abilitato nel tuo terminale (l'esempio usa Fira Code Nerd Font)
+
+### Configurazione
+
+```toml
+[aws]
+symbol = "  "
+
+[conda]
+symbol = " "
+
+[dart]
+symbol = " "
+
+[directory]
+read_only = " "
+
+[docker]
+symbol = " "
+
+[elixir]
+symbol = " "
+
+[elm]
+symbol = " "
+
+[git_branch]
+symbol = " "
+
+[golang]
+symbol = " "
+
+[haskell]
+symbol = " "
+
+[hg_branch]
+symbol = " "
+
+[java]
+symbol = " "
+
+[julia]
+symbol = " "
+
+[memory_usage]
+symbol = " "
+
+[nim]
+symbol = " "
+
+[nix_shell]
+symbol = " "
+
+[nodejs]
+symbol = " "
+
+[package]
+symbol = " "
+
+[perl]
+symbol = " "
+
+[php]
+symbol = " "
+
+[python]
+symbol = " "
+
+[ruby]
+symbol = " "
+
+[rust]
+symbol = " "
+
+[scala]
+symbol = " "
+
+[swift]
+symbol = "ﯣ "
+```

docs/ja-JP/README.md

@@ -94,7 +94,7 @@ description: Starship はミニマルで、非常に高速で、カスタマイ
 
    #### Powershell
 
-   Add the following to the end of `Microsoft.PowerShell_profile.ps1`. You can check the location of this file by querying the `$PROFILE` variable in PowerShell. Typically the path is `~\Documents\PowerShell\Microsoft.PowerShell_profile.ps1` or `~/.config/powershell/Microsoft.PowerShell_profile.ps1` on -Nix.
+   Add the following to the end of `Microsoft.PowerShell_profile.ps1`. You can check the location of this file by querying the `$PROFILE` variable in PowerShell. 通常、パスは `~\Documents\PowerShell\Microsoft.PowerShell_profile.ps1` または -Nix 上では `~/.config/powershell/Microsoft.PowerShell_profile.ps1` です。
 
    ```sh
    Invoke-Expression (&starship init powershell)
@@ -110,3 +110,27 @@ description: Starship はミニマルで、非常に高速で、カスタマイ
 
    eval $(starship init ion)
    ```
+
+   #### Elvish
+
+   ::: warning Only elvish v0.15 or higher is supported. :::
+
+   `~/.elvish/rc.elv` の最後に以下を追記してください。
+
+   ```sh
+   # ~/.elvish/rc.elv
+
+   eval (starship init elvish)
+   ```
+
+
+   #### Tcsh
+
+   `~/.tcshrc` の最後に以下を追加します:
+
+   ```sh
+   # ~/.tcshrc
+
+   eval `starship init tcsh`
+   ```
+

docs/ja-JP/advanced-config/README.md

@@ -82,7 +82,7 @@ starship_precmd_user_func="set_win_title"
 
 ここで、 `<color>` は色を指定します（以下で述べます）。 `fg:<color>` と `<color>` は現在同様の動作ですが、将来変更される可能性があります。 文字列中の単語の順序は関係ありません。
 
-例えば `fg:red none fg:blue` は依然としてスタイルのない文字列となるように、 `none` は他の文字列中の他の単語すべてを上書きします。 将来 `none` を他の単語と一緒に使用することはエラーになるかもしれません。
+`none` トークンは、文字列中の`bg:` 指定子の一部でない場合、他のすべてのトークンをオーバーライドします。そのため、たとえば、`fg:red none fg:blue` と指定した場合、スタイルなしの文字列が作られます。 `bg:none`  sets the background to the default color so `fg:red bg:none` is equivalent to `red` or `fg:red` and `bg:green fg:red bg:none` is also equivalent to `fg:red` or `red`. 将来 `none` を他の単語と一緒に使用することはエラーになるかもしれません。
 
 色は以下のいずれか1つを指定できます。
 

docs/ja-JP/faq/README.md

@@ -10,22 +10,22 @@
   - **設定**: [matchaiのDotfiles](https://github.com/matchai/dotfiles/blob/b6c6a701d0af8d145a8370288c00bb9f0648b5c2/.config/fish/config.fish)
   - **プロンプト**: [Starship](https://starship.rs/)
 
-## How do I get command completion as shown in the demo GIF?
+## デモのGIFのようにコマンド補完はどうしたら使用できますか？
 
-Completion support is provided by your shell of choice. In the case of the demo, the demo was done with [Fish Shell](https://fishshell.com/), which provides completions by default. If you use Z Shell (zsh), I'd suggest taking a look at [zsh-autosuggestions](https://github.com/zsh-users/zsh-autosuggestions).
+補完サポート、または自動補完は選択したシェルによって提供されます。 デモ中では、デフォルトの[Fish Shell](https://fishshell.com/)によって補完されています。 Z Shell (zsh) を利用しているのであれば、[zsh-autosuggestions](https://github.com/zsh-users/zsh-autosuggestions)を照参してください。
 
-## Do top level `format` and `<module>.disabled` do the same thing?
+## トップレベルの`format`と`<module>.disabled`は同じように動作しますか？
 
 はい、両方ともプロンプトでモジュールを無効にするために使用できます。 モジュールを無効にするだけの場合は、これらの理由から` <module> .disabled `を無効にする方法をお勧めします。
 
-- Disabling modules is more explicit than omitting them from the top level `format`
+- モジュールを無効化することは、トップレベルの`format`を削除するよりも明示的です。
 - Starshipが更新されると、新しく作成されたモジュールがプロンプトに追加されます
 
-## ドキュメントによると、Starshipはクロスシェル対応をしているようですが、Xシェルはサポートしていません。 なぜですか？
+## Starshipはcross-shellとのことです。 私の好みのshellはサポートしていないようですが。
 
 Starshipの構築方法は、事実上すべてのシェルのサポートを追加できるはずです。 Starshipのバイナリはステートレスであり、シェルに依存しないため、シェルがプロンプトのカスタマイズとシェルの拡張をサポートしている限り、Starshipを使用できます。
 
-Starshipをbashで動作させる小さな例を次に示します。
+Starshipをbashで動作させる例を次に示します。
 
 ```sh
 # Get the status code from the last command executed
@@ -38,7 +38,7 @@ NUM_JOBS=$(jobs -p | wc -l)
 PS1="$(starship prompt --status=$STATUS --jobs=$NUM_JOBS)"
 ```
 
-Starshipに組み込まれた[Bashの実装](https://github.com/starship/starship/blob/master/src/init/starship.bash)は、[ Command Durationモジュール](https://starship.rs/config/#Command-Duration)などの高度な機能を可能にし、Starshipが事前にインストールされたBash構成と互換性があるようにするため、少し複雑です。
+The [Bash implementation](https://github.com/starship/starship/blob/master/src/init/starship.bash) built into Starship is slightly more complex to allow for advanced features like the [Command Duration module](https://starship.rs/config/#command-duration) and to ensure that Starship is compatible with pre-installed Bash configurations.
 
 `Starshipのプロンプト`で受け入れられるすべてのフラグのリストは、次のコマンドを取得できます。
 
@@ -50,43 +50,47 @@ starship prompt --help
 
 ## 古いバージョンの glibc を使用する Linux ディストリビューションで Starship を実行するにはどうすればよいですか?
 
-"_version 'GLIBC_2のようなエラーが表示された場合。 8' が見つかりません (starshipで要求されます)_" プリビルドバイナリを使用しています（例えば、 CentOS 6 または 7 では、`glibc`の代わりに`musl`でコンパイルされたバイナリを使用できます。
+CentOS6や7などで事前にビルドされたバイナリを使用していて、"_version 'GLIBC_2.18' not found (required by starship)_" のようなエラーが出た場合、`glibc`の替わりに `musl`でコンパイルされたバイナリを使用できます。
 
 ```sh
 curl -fsSL https://starship.rs/install.sh | bash -s --- -platform unknown-linux-musl
 ```
 
-## プロンプトにグリフ記号が表示されないのはなぜですか?
+## よくわからない記号を見つけました。これはどういった意味ですか？
 
-これの最も一般的な原因は、システムの設定ミスです。 いくつかのLinuxディストリビューション 特に、すぐに使用できるフォントサポートは付属していません。 次のことを確認する必要があります。
+不明な記号に遭遇した場合、`starship explain` を使用することで、現在表示しているモジュールの説明を見ることができます。
 
-- ロケールは、`de_DE.UTF-8`や` ja_JP.UTF-8</ 0>などのUTF-8値に設定されています。 <code>LC_ALL`がUTF-8値でない場合、[変更する必要があります](https://www.tecmint.com/set-system-locales-in-linux/)。
-- 絵文字フォントがインストールされています。 ほとんどのシステムにはデフォルトで絵文字フォントが付属していますが、 一部(特にArch Linux) はそうではありません。 通常、システムの パッケージマネージャーからインストールすることができます--[noto emoji](https://www.google.com/get/noto/help/emoji/)は人気な選択肢です。
-- [Nerd Font](https://www.nerdfonts.com/)を使用しています。
+## 私のプロンプトで記号のグリフがないのはなぜですか？
 
-システムをテストするには、ターミナルで次のコマンドを実行します。
+よくある原因はシステム上での設定ミスです。 いくつかのLinuxディストリビューションの初期設定にフォントサポートがありません。 次のことを確認してください。
+
+- ロケールが、`de_DE.UTF-8`や` ja_JP.UTF-8`などのUTF-8に設定されている。 `LC_ALL`がUTF-8でない場合、[変更する必要があります](https://www.tecmint.com/set-system-locales-in-linux/)。
+- 絵文字フォントがインストールされている。 ほとんどのシステムにはデフォルトで絵文字フォントが付属していますが、 一部 (特にArch Linux) はそうではありません。 通常、システムの パッケージマネージャーからインストールすることができます。--[noto emoji](https://www.google.com/get/noto/help/emoji/)は一般的な選択肢です。
+- [Nerd Font](https://www.nerdfonts.com/)を使用している。
+
+ターミナルで以下のコマンドを実行することでテストできます。
 
 ```sh
 echo -e "\xf0\x9f\x90\x8d"
 echo -e "\xee\x82\xa0"
 ```
 
-1行目は[snake emoji](https://emojipedia.org/snake/)を生成し、2行目は[powerline branch symbol (e0a0)](https://github.com/ryanoasis/powerline-extra-symbols#glyphs)を生成するはずです。
+一行目は[蛇の絵文字](https://emojipedia.org/snake/)、二行目は[powerline branch symbol (e0a0)](https://github.com/ryanoasis/powerline-extra-symbols#glyphs)が表示されるはずです。
 
-いずれかのシンボルが正しく表示されない場合でも、システムの設定が間違っています。 残念ながら、フォント設定を正しくするのは難しい場合があります。 Discordのユーザーがお役に立てるかもしれません。 両方の記号が正しく表示されているにもかかわらず、まだStarshipに表示されていない場合は、[バグ報告をしてください!](https://github.com/starship/starship/issues/new/choose)
+もし、どちらの記号とも正しく表示されない場合は、システムの設定が間違っています。 不幸にも、正しくフォントを設定するのは難しいものです。 Discordのユーザーが助けてくれるかもしれません！ もし記号が正しく表示されているのにもかかわらず、Starshipが正しく表示されていない場合は、[バグの報告](https://github.com/starship/starship/issues/new/choose)をお願いします。
 
-## Starshipをアンインストールするにはどうすればいいですか?
+## Starshipをアンインストールしたい
 
-Starshipは、最初の場所にインストールするのと同じくらい簡単にアンインストールできます。
+Starshipのアンインストールはインストールと同じぐらい簡単です。
 
-1. Starshipを初期化するために使用されるシェル設定の行を削除します(例:`~/.bashrc`)。
+1. Starshipを初期化するために使用した、シェルの設定行を削除します (例:`~/.bashrc`)。
 1. Starshipのバイナリを削除します。
 
-Starship がパッケージマネージャを使用してインストールされている場合は、アンインストール手順については、そのドキュメントを参照してください。
+パッケージマネージャーを使用してStarshipをインストールした場合は、パッケージマネージャーのアンインストールガイドを参照してください。
 
-Starship が `curl | bash` スクリプトを使用してインストールされた場合、次のコマンドはバイナリを削除します:
+`curl | bash` スクリプトを使用してStarshipをインストールした場合は、以下のコマンドでバイナリを削除してください。
 
 ```sh
-# starshipバイナリを見つけて削除します
+# starshipバイナリを見つけて削除
 rm "$(which starship)"
 ```

docs/ja-JP/guide/README.md

@@ -2,31 +2,36 @@
   <img
     width="400"
     src="https://raw.githubusercontent.com/starship/starship/master/media/logo.png"
-    alt="Starship – Cross-shell prompt" />
+    alt="Starship – Cross-shell prompt"
+ />
 </p>
 
 <p align="center">
   <a href="https://github.com/starship/starship/actions"
     ><img
       src="https://img.shields.io/github/workflow/status/starship/starship/Main workflow/master?label=workflow&style=flat-square"
-      alt="GitHub Actions workflow status" /></a>
+      alt="GitHub Actions workflow status"
+ /></a>
   <a href="https://crates.io/crates/starship"
     ><img
       src="https://img.shields.io/crates/v/starship?style=flat-square"
-      alt="Crates.io version" /></a>
+      alt="Crates.io version"
+ /></a>
   <a href="https://repology.org/project/starship/versions"
     ><img
       src="https://img.shields.io/repology/repositories/starship?label=in%20repositories&style=flat-square"
       alt="Packaging status" /></a
 ><br />
-  <a href="https://discord.gg/8Jzqu3T"
+  <a href="https://discord.gg/starship"
     ><img
       src="https://img.shields.io/discord/567163873606500352?label=discord&logoColor=white&style=flat-square"
-      alt="Chat on Discord" /></a>
+      alt="Chat on Discord"
+ /></a>
   <a href="https://twitter.com/StarshipPrompt"
     ><img
       src="https://img.shields.io/badge/twitter-@StarshipPrompt-1DA1F3?style=flat-square"
-      alt="Follow @StarshipPrompt on Twitter" /></a>
+      alt="Follow @StarshipPrompt on Twitter"
+ /></a>
 </p>
 
 <p align="center">
@@ -42,54 +47,72 @@
     ><img
       height="20"
       src="https://raw.githubusercontent.com/starship/starship/master/media/flag-us.png"
-      alt="English" /></a>
+      alt="English"
+ /></a>
   &nbsp;
   <a
     href="https://github.com/starship/starship/blob/master/docs/ja-JP/guide/README.md"
     ><img
       height="20"
       src="https://raw.githubusercontent.com/starship/starship/master/media/flag-jp.png"
-      alt="日本語" /></a>
+      alt="日本語"
+ /></a>
   &nbsp;
   <a
     href="https://github.com/starship/starship/blob/master/docs/zh-TW/guide/README.md"
     ><img
       height="20"
       src="https://raw.githubusercontent.com/starship/starship/master/media/flag-tw.png"
-      alt="繁體中文" /></a>
+      alt="繁體中文"
+ /></a>
   &nbsp;
   <a
     href="https://github.com/starship/starship/blob/master/docs/ru-RU/guide/README.md"
     ><img
       height="20"
       src="https://raw.githubusercontent.com/starship/starship/master/media/flag-ru.png"
-      alt="Русский" /></a>
+      alt="Русский"
+ /></a>
   &nbsp;
   <a
     href="https://github.com/starship/starship/blob/master/docs/de-DE/guide/README.md"
     ><img
       height="20"
       src="https://raw.githubusercontent.com/starship/starship/master/media/flag-de.png"
-      alt="Deutsch" /></a>
+      alt="Deutsch"
+ /></a>
   &nbsp;
   <a
     href="https://github.com/starship/starship/blob/master/docs/zh-CN/guide/README.md"
     ><img
       height="20"
       src="https://raw.githubusercontent.com/starship/starship/master/media/flag-cn.png"
-      alt="简体中文" /></a>
+      alt="简体中文"
+ /></a>
   &nbsp;
-  <a href="https://translate.starship.rs/project/starship-prompt/es"
+  <a 
+    href="https://github.com/starship/starship/blob/master/docs/es-ES/guide/README.md"
     ><img
       height="20"
       src="https://raw.githubusercontent.com/starship/starship/master/media/flag-es.png"
-      alt="Español" /></a>
+      alt="Español"
+ /></a>
   &nbsp;
-  <a href="https://translate.starship.rs/project/starship-prompt/fr"
+  <a 
+    href="https://github.com/starship/starship/blob/master/docs/fr-FR/guide/README.md"
     ><img
       height="20"
       src="https://raw.githubusercontent.com/starship/starship/master/media/flag-fr.png"
-      alt="Français" /></a>
+      alt="Français"
+ /></a>
+  &nbsp;
+  <a 
+    href="https://github.com/starship/starship/blob/master/docs/vi-VN/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-vn.png"
+      alt="Tiếng Việt"
+ /></a>
 </p>
 
 <h1></h1>
@@ -98,12 +121,11 @@
   src="https://raw.githubusercontent.com/starship/starship/master/media/demo.gif"
   alt="Starship with iTerm2 and the Snazzy theme"
   width="50%"
-  align="right" />
-
+  align="right"
+ />
 
 **シェル用の最小限の、非常に高速で、無限にカスタマイズ可能なプロンプトです！**
 
-
 - **高速:** _本当に_ 高速です！ 🚀
 - **カスタマイズ可能:** プロンプトのあらゆる側面を構成します。
 - **ユニバーサル:** あらゆるシェル、あらゆるオペレーティングシステムで動作します。
@@ -125,6 +147,8 @@
 
 ### 入門
 
+**注意**: さまざまなプラットフォームが急増しているため、ここでは対応プラットフォームの一部だけを挙げています。 自分が使っているシェルがありませんか？ [extra platform instructions](https://starship.rs/installing/) を確認してください。
+
 1. **Starship** のバイナリをインストール
 
 
@@ -138,17 +162,10 @@
    ```
 
 
-   ##### [crates.io](https://crates.io/)からソースをインストール
-
-   ```sh
-   cargo install starship
-   ```
-
-
    #### パッケージマネージャー経由でインストール
 
 
-   ##### [ Homebrew ](https://brew.sh/)の場合：
+   ##### 例: [Homebrew の場合](https://brew.sh/):
 
    ```sh
    brew install starship
@@ -161,7 +178,7 @@
    scoop install starship
    ```
 
-1. 初期化のためのスクリプトをシェルの設定ファイルに追加
+2. 初期化のためのスクリプトをシェルの設定ファイルに追加
 
 
    #### Bash
@@ -199,9 +216,9 @@
 
    #### PowerShell
 
-    Add the following to the end of `Microsoft.PowerShell_profile.ps1`. You can check the location of this file by querying the `$PROFILE` variable in PowerShell. Typically the path is `~\Documents\PowerShell\Microsoft.PowerShell_profile.ps1` or `~/.config/powershell/Microsoft.PowerShell_profile.ps1` on -Nix.
+   `Microsoft.PowerShell_profile.ps1` の最後に以下を追記してください。 PowerShell 上で `$PROFILE` 変数を問い合わせると、ファイルの場所を確認できます。 通常、パスは `~\Documents\PowerShell\Microsoft.PowerShell_profile.ps1` または -Nix 上では `~/.config/powershell/Microsoft.PowerShell_profile.ps1` です。
 
-   ```sh
+   ```powershell
    Invoke-Expression (&starship init powershell)
    ```
 
@@ -216,10 +233,34 @@
    eval $(starship init ion)
    ```
 
+
+   #### Elvish
+
+   **警告** elvish v0.15 以上のみがサポートされています。 `~/.elvish/rc.elv` の最後に以下を追記してください。
+
+   ```sh
+   # ~/.elvish/rc.elv
+
+   eval (starship init elvish)
+   ```
+
+
+   #### Tcsh
+
+   `~/.tcshrc` の最後に以下を追加します:
+
+   ```sh
+   # ~/.tcshrc
+
+   eval `starship init tcsh`
+   ```
+
 ## 🤝 貢献
 
 私たちは常に**すべてのスキルレベル**の貢献者を探しています！ もし簡単にプロジェクトへ参加する方法をお探しなら、 [good first issue](https://github.com/starship/starship/labels/🌱%20good%20first%20issue) に取り組んでみてください。
 
+あなたが英語以外の言語に堪能な場合、ドキュメントの翻訳と更新に協力していただけると嬉しいです。 協力してくれる場合、翻訳は [Starship Crowdin](https://translate.starship.rs/) から貢献できます。
+
 もしあなたが Starship への貢献に興味がある場合は、我々の[貢献ガイド](https://github.com/starship/starship/blob/master/CONTRIBUTING.md)をご覧ください。 また、気軽に我々の[Discord サーバー](https://discord.gg/8Jzqu3T)へ顔を出してください。 👋
 
 ### コードに貢献していただいた方々

docs/ja-JP/installing/README.md

@@ -0,0 +1,84 @@
+# 🚀 Advanced Installation
+
+To install starship, you need to do two things:
+
+1. Get the **starship** binary onto your computer
+1. Tell your shell to use the starship binary as its prompt by modifying its init scripts
+
+For most users, the instructions on [the main page](/guide/#🚀-installation) will work great. However, for some more specialized platforms, different instructions are needed.
+
+There are so many platforms out there that they didn't fit into the main README.md file, so here are some installation instructions for other platforms from the community. Is yours not here? Please do add it here if you figure it out!
+
+## [Chocolatey](https://chocolatey.org)
+
+### 必要なもの
+
+Head over to the [Chocolatey installation page](https://chocolatey.org/install) and follow the instructions to install Chocolatey.
+
+### Installation
+
+```powershell
+choco install starship
+```
+
+## [termux](https://termux.com)
+
+### 必要なもの
+
+```sh
+pkg install getconf
+```
+
+### Installation
+
+```sh
+curl -fsSL https://starship.rs/install.sh | bash -s -- -b /data/data/com.termux/files/usr/bin
+```
+
+## [Nix](https://nixos.wiki/wiki/Nix)
+
+### Getting the Binary
+
+#### Imperatively
+
+```sh
+nix-env -iA nixos.starship
+```
+
+#### Declarative, single user, via [home-manager](home-manager)
+
+Enable the `programs.starship` module in your `home.nix` file, and add your settings
+
+```nix
+{
+  programs.starship = {
+    enable = true;
+    enableZshIntegration = true;
+    # Configuration written to ~/.config/starship.toml
+    settings = {
+      # add_newline = false;
+
+      # character = {
+      #   success_symbol = "[➜](bold green)";
+      #   error_symbol = "[➜](bold red)";
+      # };
+
+      # package.disabled = true;
+    };
+  };
+}
+```
+
+then run
+
+```sh
+home-manager switch
+```
+
+#### Declarative, system-wide, with NixOS
+
+Add `pkgs.starship` to `environment.systemPackages` in your `configuration.nix`, then run
+
+```sh
+sudo nixos-rebuild switch
+```

docs/ja-JP/presets/README.md

@@ -18,17 +18,15 @@
 [aws]
 symbol = "  "
 
-[battery]
-full_symbol = ""
-charging_symbol = ""
-discharging_symbol = ""
-
 [conda]
 symbol = " "
 
 [dart]
 symbol = " "
 
+[directory]
+read_only = " "
+
 [docker]
 symbol = " "
 
@@ -86,6 +84,9 @@ symbol = " "
 [rust]
 symbol = " "
 
+[scala]
+symbol = " "
+
 [swift]
 symbol = "ﯣ "
 ```

docs/ko-KR/README.md

@@ -0,0 +1,136 @@
+---
+home: true
+heroImage: /logo.svg
+heroText:
+tagline: The minimal, blazing-fast, and infinitely customizable prompt for any shell!
+actionText: Get Started →
+actionLink: ./guide/
+features:
+  - 
+    title: Compatibility First
+    details: Works on the most common shells on the most common operating systems. Use it everywhere!
+  - 
+    title: Rust-Powered
+    details: Brings the best-in-class speed and safety of Rust, to make your prompt as quick and reliable as possible.
+  - 
+    title: Customizable
+    details: Every little detail is customizable to your liking, to make this prompt as minimal or feature-rich as you'd like it to be.
+footer: ISC Licensed | Copyright © 2019-present Starship Contributors
+#Used for the description meta tag, for SEO
+metaTitle: "Starship: Cross-Shell Prompt"
+description: Starship is the minimal, blazing fast, and extremely customizable prompt for any shell! Shows the information you need, while staying sleek and minimal. Quick installation available for Bash, Fish, ZSH, Ion, and PowerShell.
+---
+
+<div class="center">
+  <video class="demo-video" muted autoplay loop playsinline>
+    <source src="/demo.webm" type="video/webm">
+    <source src="/demo.mp4" type="video/mp4">
+  </video>
+</div>
+
+### 빠른 설치
+
+1. **starship** 바이러니 설치:
+
+
+   #### 최근 버전 설치
+
+   With Shell:
+
+   ```sh
+   curl -fsSL https://starship.rs/install.sh | bash
+   ```
+
+
+   #### 패키지 매니저를 이용한 설치
+
+   [Homebrew](https://brew.sh/)를 통한 설치:
+
+   ```sh
+   brew install starship
+   ```
+
+   With [Scoop](https://scoop.sh):
+
+   ```powershell
+   scoop install starship
+   ```
+
+1. 쉘 설정에 시동 스크립트를 추가:
+
+
+   #### Bash
+
+   `~/.bashrc`에 아래 라인을 추가
+
+   ```sh
+   # ~/.bashrc
+
+   eval "$(starship init bash)"
+   ```
+
+
+   #### Fish
+
+   `~/.config/fish/config.fish`에 아래 라인을 추가
+
+   ```sh
+   # ~/.config/fish/config.fish
+
+   starship init fish | source
+   ```
+
+
+   #### Zsh
+
+   `~/.zshrc`에 아래 라인을 추가
+
+   ```sh
+   # ~/.zshrc
+
+   eval "$(starship init zsh)"
+   ```
+
+
+   #### Powershell
+
+   `Microsoft.PowerShell_profile.ps1`의 끝부분에 아래 내용을 추가. 해당 설정파일은 파워쉘에서 `$PROFILE` 변수 확인을 통해 확인 가능. 일반적으로 해당 파일은 `~\Documents\PowerShell\Microsoft.PowerShell_profile.ps1` 혹은 -Nix의 경우 `~/.config/powershell/Microsoft.PowerShell_profile.ps1`에 위치.
+
+   ```sh
+   Invoke-Expression (&starship init powershell)
+   ```
+
+
+   #### Ion
+
+   아래의 라인을 `~/.config/ion/initrc` 마지막에 추가:
+
+   ```sh
+   # ~/.config/ion/initrc
+
+   eval $(starship init ion)
+   ```
+
+   #### Elvish
+
+   ::: 주의 elvish v0.15 이상만 지원. :::
+
+   아래의 라인을 `~/.elvish/rc.elv` 마지막에 추가:
+
+   ```sh
+   # ~/.elvish/rc.elv
+
+   eval (starship init elvish)
+   ```
+
+
+   #### Tcsh
+
+   아래의 라인을 `~/.tcshrc` 마지막에 추가:
+
+   ```sh
+   # ~/.tcshrc
+
+   eval `starship init tcsh`
+   ```
+

docs/ko-KR/advanced-config/README.md

@@ -0,0 +1,93 @@
+# Advanced Configuration
+
+While Starship is a versatile shell, sometimes you need to do more than edit `starship.toml` to get it to do certain things. This page details some of the more advanced configuration techniques used in starship.
+
+::: warning
+
+The configurations in this section are subject to change in future releases of Starship.
+
+:::
+
+## Custom pre-prompt and pre-execution Commands in Bash
+
+Bash does not have a formal preexec/precmd framework like most other shells. Because of this, it is difficult to provide fully customizable hooks in `bash`. However, Starship does give you limited ability to insert your own functions into the prompt-rendering procedure:
+
+- To run a custom function right before the prompt is drawn, define a new function and then assign its name to `starship_precmd_user_func`. For example, to draw a rocket before the prompt, you would do
+
+```bash
+function blastoff(){
+    echo "🚀"
+}
+starship_precmd_user_func="blastoff"
+```
+
+- To run a custom function right before a command runs, you can use the [`DEBUG` trap mechanism](https://jichu4n.com/posts/debug-trap-and-prompt_command-in-bash/). However, you **must** trap the DEBUG signal *before* initializing Starship! Starship can preserve the value of the DEBUG trap, but if the trap is overwritten after starship starts up, some functionality will break.
+
+```bash
+function blastoff(){
+    echo "🚀"
+}
+trap blastoff DEBUG     # Trap DEBUG *before* running starship
+eval $(starship init bash)
+```
+
+## Change Window Title
+
+Some shell prompts will automatically change the window title for you (e.g. to reflect your working directory). Fish even does it by default. Starship does not do this, but it's fairly straightforward to add this functionality to `bash` or `zsh`.
+
+First, define a window title change function (identical in bash and zsh):
+
+```bash
+function set_win_title(){
+    echo -ne "\033]0; YOUR_WINDOW_TITLE_HERE \007"
+}
+```
+
+You can use variables to customize this title (`$USER`, `$HOSTNAME`, and `$PWD` are popular choices).
+
+In `bash`, set this function to be the precmd starship function:
+
+```bash
+starship_precmd_user_func="set_win_title"
+```
+
+In `zsh`, add this to the `precmd_functions` array:
+
+```bash
+precmd_functions+=(set_win_title)
+```
+
+If you like the result, add these lines to your shell configuration file (`~/.bashrc` or `~/.zshrc`) to make it permanent.
+
+For example, if you want to display your current directory in your terminal tab title, add the following snippet to your `~/.bashrc` or `~/.zshrc`:
+
+```bash
+function set_win_title(){
+    echo -ne "\033]0; $(basename $PWD) \007"
+}
+starship_precmd_user_func="set_win_title"
+```
+
+## Style Strings
+
+Style strings are a list of words, separated by whitespace. The words are not case sensitive (i.e. `bold` and `BoLd` are considered the same string). Each word can be one of the following:
+
+  - `bold`
+  - `underline`
+  - `dimmed`
+  - `bg:<color>`
+  - `fg:<color>`
+  - `<color>`
+  - `none`
+
+where `<color>` is a color specifier (discussed below). `fg:<color>` and `<color>` currently do the same thing , though this may change in the future. The order of words in the string does not matter.
+
+The `none` token overrides all other tokens in a string if it is not part of a `bg:` specifier, so that e.g. `fg:red none fg:blue` will still create a string with no styling. `bg:none`  sets the background to the default color so `fg:red bg:none` is equivalent to `red` or `fg:red` and `bg:green fg:red bg:none` is also equivalent to `fg:red` or `red`. It may become an error to use `none` in conjunction with other tokens in the future.
+
+A color specifier can be one of the following:
+
+ - One of the standard terminal colors: `black`, `red`, `green`, `blue`, `yellow`, `purple`, `cyan`, `white`. You can optionally prefix these with `bright-` to get the bright version (e.g. `bright-white`).
+ - A `#` followed by a six-digit hexadecimal number. This specifies an [RGB color hex code](https://www.w3schools.com/colors/colors_hexadecimal.asp).
+ - A number between 0-255. This specifies an [8-bit ANSI Color Code](https://i.stack.imgur.com/KTSQa.png).
+
+If multiple colors are specified for foreground/background, the last one in the string will take priority.

docs/ko-KR/faq/README.md

@@ -0,0 +1,96 @@
+# FAQ
+
+## What is the configuration used in the demo GIF?
+
+- **Terminal Emulator**: [iTerm2](https://iterm2.com/)
+  - **Theme**: Minimal
+  - **Color Scheme**: [Snazzy](https://github.com/sindresorhus/iterm2-snazzy)
+  - **Font**: [FiraCode Nerd Font](https://www.nerdfonts.com/font-downloads)
+- **Shell**: [Fish Shell](https://fishshell.com/)
+  - **Configuration**: [matchai's Dotfiles](https://github.com/matchai/dotfiles/blob/b6c6a701d0af8d145a8370288c00bb9f0648b5c2/.config/fish/config.fish)
+  - **Prompt**: [Starship](https://starship.rs/)
+
+## How do I get command completion as shown in the demo GIF?
+
+Completion support, or autocomplete, is provided by your shell of choice. In the case of the demo, the demo was done with [Fish Shell](https://fishshell.com/), which provides completions by default. If you use Z Shell (zsh), I'd suggest taking a look at [zsh-autosuggestions](https://github.com/zsh-users/zsh-autosuggestions).
+
+## 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. Why isn't my preferred shell supported?
+
+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:
+
+```sh
+# 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](https://github.com/starship/starship/blob/master/src/init/starship.bash) built into Starship is slightly more complex to allow for advanced features like the [Command Duration module](https://starship.rs/config/#command-duration) 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:
+
+```sh
+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`:
+
+```sh
+curl -fsSL https://starship.rs/install.sh | bash -s -- --platform unknown-linux-musl
+```
+
+## I see symbols I don't understand or expect, what do they mean?
+
+If you see symbols that you don't recognise you can use `starship explain` to explain the currently showing modules.
+
+## 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](https://www.tecmint.com/set-system-locales-in-linux/).
+- 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](https://www.google.com/get/noto/help/emoji/) is a popular choice.
+- You are using a [Nerd Font](https://www.nerdfonts.com/).
+
+To test your system, run the following commands in a terminal:
+
+```sh
+echo -e "\xf0\x9f\x90\x8d"
+echo -e "\xee\x82\xa0"
+```
+
+The first line should produce a [snake emoji](https://emojipedia.org/snake/), while the second should produce a [powerline branch symbol (e0a0)](https://github.com/ryanoasis/powerline-extra-symbols#glyphs).
+
+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!](https://github.com/starship/starship/issues/new/choose)
+
+## 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.
+1. 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:
+
+```sh
+# Locate and delete the starship binary
+rm "$(which starship)"
+```

docs/ko-KR/guide/README.md

@@ -0,0 +1,311 @@
+<p align="center">
+  <img
+    width="400"
+    src="https://raw.githubusercontent.com/starship/starship/master/media/logo.png"
+    alt="Starship – Cross-shell prompt"
+ />
+</p>
+
+<p align="center">
+  <a href="https://github.com/starship/starship/actions"
+    ><img
+      src="https://img.shields.io/github/workflow/status/starship/starship/Main workflow/master?label=workflow&style=flat-square"
+      alt="깃헙 액션 워크풀로 상태"
+ /></a>
+  <a href="https://crates.io/crates/starship"
+    ><img
+      src="https://img.shields.io/crates/v/starship?style=flat-square"
+      alt="Crates.io 버전"
+ /></a>
+  <a href="https://repology.org/project/starship/versions"
+    ><img
+      src="https://img.shields.io/repology/repositories/starship?label=in%20repositories&style=flat-square"
+      alt="패키징 상태" /></a
+><br />
+  <a href="https://discord.gg/starship"
+    ><img
+      src="https://img.shields.io/discord/567163873606500352?label=discord&logoColor=white&style=flat-square"
+      alt="디스코드에 채팅을 하세요"
+ /></a>
+  <a href="https://twitter.com/StarshipPrompt"
+    ><img
+      src="https://img.shields.io/badge/twitter-@StarshipPrompt-1DA1F3?style=flat-square"
+      alt="트위터에서 @StarshipPrompt를 팔로우 하세요"
+ /></a>
+</p>
+
+<p align="center">
+  <a href="https://starship.rs">웹사이트</a>
+  ·
+  <a href="#🚀-installation">설치</a>
+  ·
+  <a href="https://starship.rs/config/">설정</a>
+</p>
+
+<p align="center">
+  <a href="https://github.com/starship/starship/blob/master/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-us.png"
+      alt="English"
+ /></a>
+  &nbsp;
+  <a
+    href="https://github.com/starship/starship/blob/master/docs/ja-JP/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-jp.png"
+      alt="日本語"
+ /></a>
+  &nbsp;
+  <a
+    href="https://github.com/starship/starship/blob/master/docs/zh-TW/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-tw.png"
+      alt="繁體中文"
+ /></a>
+  &nbsp;
+  <a
+    href="https://github.com/starship/starship/blob/master/docs/ru-RU/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-ru.png"
+      alt="Русский"
+ /></a>
+  &nbsp;
+  <a
+    href="https://github.com/starship/starship/blob/master/docs/de-DE/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-de.png"
+      alt="Deutsch"
+ /></a>
+  &nbsp;
+  <a
+    href="https://github.com/starship/starship/blob/master/docs/zh-CN/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-cn.png"
+      alt="简体中文"
+ /></a>
+  &nbsp;
+  <a 
+    href="https://github.com/starship/starship/blob/master/docs/es-ES/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-es.png"
+      alt="Español"
+ /></a>
+  &nbsp;
+  <a 
+    href="https://github.com/starship/starship/blob/master/docs/fr-FR/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-fr.png"
+      alt="Français"
+ /></a>
+  &nbsp;
+  <a 
+    href="https://github.com/starship/starship/blob/master/docs/vi-VN/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-vn.png"
+      alt="Tiếng Việt"
+ /></a>
+</p>
+
+<h1></h1>
+
+<img
+  src="https://raw.githubusercontent.com/starship/starship/master/media/demo.gif"
+  alt="Starship with iTerm2 and the Snazzy theme"
+  width="50%"
+  align="right"
+ />
+
+**The minimal, blazing-fast, and infinitely customizable prompt for any shell!**
+
+- **Fast:** it's fast – _really really_ fast! 🚀
+- **Customizable:** configure every aspect of your prompt.
+- **Universal:** works on any shell, on any operating system.
+- **Intelligent:** shows relevant information at a glance.
+- **Feature rich:** support for all your favorite tools.
+- **Easy:** quick to install – start using it in minutes.
+
+<p align="center">
+<a href="https://starship.rs/config/"><strong>Explore the Starship docs&nbsp;&nbsp;▶</strong></a>
+</p>
+
+<a name="🚀-installation"></a>
+
+## 🚀 설치
+
+### Prerequisites
+
+- A [Nerd Font](https://www.nerdfonts.com/) installed and enabled in your terminal (for example, try the [Fira Code Nerd Font](https://www.nerdfonts.com/font-downloads)).
+
+### 시작하기
+
+**Note**: due to the proliferation of different platforms, only a subset of supported platforms are shown below. Can't see yours? Have a look at the [extra platform instructions](https://starship.rs/installing/).
+
+1. **starship** 바이러니 설치:
+
+
+   #### 최근 버전 설치
+
+
+   ##### From prebuilt binary, with Shell:
+
+   ```sh
+   curl -fsSL https://starship.rs/install.sh | bash
+   ```
+
+
+   #### Install via Package Manager
+
+
+   ##### 예제: [Homebrew](https://brew.sh/):
+
+   ```sh
+   brew install starship
+   ```
+
+
+   ##### With [Scoop](https://scoop.sh):
+
+   ```powershell
+   scoop install starship
+   ```
+
+2. Add the init script to your shell's config file:
+
+
+   #### Bash
+
+   Add the following to the end of `~/.bashrc`:
+
+   ```sh
+   # ~/.bashrc
+
+   eval "$(starship init bash)"
+   ```
+
+
+   #### Fish
+
+   Add the following to the end of `~/.config/fish/config.fish`:
+
+   ```sh
+   # ~/.config/fish/config.fish
+
+   starship init fish | source
+   ```
+
+
+   #### Zsh
+
+   Add the following to the end of `~/.zshrc`:
+
+   ```sh
+   # ~/.zshrc
+
+   eval "$(starship init zsh)"
+   ```
+
+
+   #### 파워셀
+
+   `Microsoft.PowerShell_profile.ps1`의 끝부분에 아래 내용을 추가. 해당 설정파일은 파워쉘에서 `$PROFILE` 변수 확인을 통해 확인 가능. Typically the path is `~\Documents\PowerShell\Microsoft.PowerShell_profile.ps1` or `~/.config/powershell/Microsoft.PowerShell_profile.ps1` on -Nix.
+
+   ```powershell
+   Invoke-Expression (&starship init powershell)
+   ```
+
+
+   #### Ion
+
+   Add the following to the end of `~/.config/ion/initrc`:
+
+   ```sh
+   # ~/.config/ion/initrc
+
+   eval $(starship init ion)
+   ```
+
+
+   #### Elvish
+
+   **Warning** Only elvish v0.15 or higher is supported. Add the following to the end of `~/.elvish/rc.elv`:
+
+   ```sh
+   # ~/.elvish/rc.elv
+
+   eval (starship init elvish)
+   ```
+
+
+   #### Tcsh
+
+   Add the following to the end of `~/.tcshrc`:
+
+   ```sh
+   # ~/.tcshrc
+
+   eval `starship init tcsh`
+   ```
+
+## 🤝 기여
+
+We are always looking for contributors of **all skill levels**! If you're looking to ease your way into the project, try out a [good first issue](https://github.com/starship/starship/labels/🌱%20good%20first%20issue).
+
+If you are fluent in a non-English language, we greatly appreciate any help keeping our docs translated and up-to-date in other languages. If you would like to help, translations can be contributed on the [Starship Crowdin](https://translate.starship.rs/).
+
+If you are interested in helping contribute to starship, please take a look at our [Contributing Guide](https://github.com/starship/starship/blob/master/CONTRIBUTING.md). Also, feel free to drop into our [Discord server](https://discord.gg/8Jzqu3T) and say hi. 👋
+
+### 코드 기여
+
+This project exists thanks to all the people who contribute. [[기여](https://github.com/starship/starship/blob/master/CONTRIBUTING.md)].
+<a href="https://github.com/starship/starship/graphs/contributors"><img src="https://opencollective.com/starship/contributors.svg?width=890&button=false" /></a>
+
+### Financial Contributors
+
+Become a financial contributor and help us sustain our community. [[기여](https://opencollective.com/starship/contribute)]
+
+#### Individuals
+
+<a href="https://opencollective.com/starship"><img src="https://opencollective.com/starship/individuals.svg?width=890"></a>
+
+#### 조직
+
+Support this project with your organization. Your logo will show up here with a link to your website. [[기여](https://opencollective.com/starship/contribute)]
+
+<a href="https://opencollective.com/starship/organization/0/website"><img src="https://opencollective.com/starship/organization/0/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/1/website"><img src="https://opencollective.com/starship/organization/1/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/2/website"><img src="https://opencollective.com/starship/organization/2/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/3/website"><img src="https://opencollective.com/starship/organization/3/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/4/website"><img src="https://opencollective.com/starship/organization/4/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/5/website"><img src="https://opencollective.com/starship/organization/5/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/6/website"><img src="https://opencollective.com/starship/organization/6/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/7/website"><img src="https://opencollective.com/starship/organization/7/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/8/website"><img src="https://opencollective.com/starship/organization/8/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/9/website"><img src="https://opencollective.com/starship/organization/9/avatar.svg"></a>
+
+## 💭 Inspired By
+
+Please check out these previous works that helped inspire the creation of starship. 🙏
+
+- **[denysdovhan/spaceship-prompt](https://github.com/denysdovhan/spaceship-prompt)** - A ZSH prompt for astronauts.
+
+- **[denysdovhan/robbyrussell-node](https://github.com/denysdovhan/robbyrussell-node)** - Cross-shell robbyrussell theme written in JavaScript.
+
+- **[reujab/silver](https://github.com/reujab/silver)** - A cross-shell customizable powerline-like prompt with icons.
+
+<p align="center">
+    <br>
+    <img width="100" src="https://raw.githubusercontent.com/starship/starship/master/media/icon.png" alt="Starship 로켓 아이콘">
+</p>
+
+## 📝라이선스
+
+Copyright © 2019-present, [Starship Contributors](https://github.com/starship/starship/graphs/contributors).<br /> This project is [ISC](https://github.com/starship/starship/blob/master/LICENSE) licensed.

docs/ko-KR/installing/README.md

@@ -0,0 +1,84 @@
+# 🚀 Advanced Installation
+
+To install starship, you need to do two things:
+
+1. Get the **starship** binary onto your computer
+1. Tell your shell to use the starship binary as its prompt by modifying its init scripts
+
+For most users, the instructions on [the main page](/guide/#🚀-installation) will work great. However, for some more specialized platforms, different instructions are needed.
+
+There are so many platforms out there that they didn't fit into the main README.md file, so here are some installation instructions for other platforms from the community. Is yours not here? Please do add it here if you figure it out!
+
+## [Chocolatey](https://chocolatey.org)
+
+### Prerequisites
+
+Head over to the [Chocolatey installation page](https://chocolatey.org/install) and follow the instructions to install Chocolatey.
+
+### Installation
+
+```powershell
+choco install starship
+```
+
+## [termux](https://termux.com)
+
+### Prerequisites
+
+```sh
+pkg install getconf
+```
+
+### Installation
+
+```sh
+curl -fsSL https://starship.rs/install.sh | bash -s -- -b /data/data/com.termux/files/usr/bin
+```
+
+## [Nix](https://nixos.wiki/wiki/Nix)
+
+### Getting the Binary
+
+#### Imperatively
+
+```sh
+nix-env -iA nixos.starship
+```
+
+#### Declarative, single user, via [home-manager](home-manager)
+
+Enable the `programs.starship` module in your `home.nix` file, and add your settings
+
+```nix
+{
+  programs.starship = {
+    enable = true;
+    enableZshIntegration = true;
+    # Configuration written to ~/.config/starship.toml
+    settings = {
+      # add_newline = false;
+
+      # character = {
+      #   success_symbol = "[➜](bold green)";
+      #   error_symbol = "[➜](bold red)";
+      # };
+
+      # package.disabled = true;
+    };
+  };
+}
+```
+
+then run
+
+```sh
+home-manager switch
+```
+
+#### Declarative, system-wide, with NixOS
+
+Add `pkgs.starship` to `environment.systemPackages` in your `configuration.nix`, then run
+
+```sh
+sudo nixos-rebuild switch
+```

docs/ko-KR/migrating-to-0.45.0/README.md

@@ -0,0 +1,267 @@
+# Migrating to v0.45.0
+
+Starship v0.45.0 is a release containing breaking changes, in preparation for the big v1.0.0. We have made some major changes around how configuration is done on the prompt, to allow for a greater degree of customization.
+
+This guide is intended to walk you through the breaking changes.
+
+## `prompt_order` has been replaced by a root-level `format`
+
+Previously to v0.45.0, `prompt_order` would accept an array of module names in the order which they should be rendered by Starship.
+
+Starship v0.45.0 instead accepts a `format` value, allowing for customization of the prompt outside of the modules themselves.
+
+**Example pre-v0.45.0 configuration**
+
+```toml
+prompt_order = [
+  "username",
+  "hostname",
+  "directory",
+  "git_branch",
+  "git_commit",
+  "git_state",
+  "git_status",
+  "cmd_duration",
+  "custom",
+  "line_break",
+  "jobs",
+  "battery",
+  "time",
+  "character",
+]
+```
+
+**Example v0.45.0 configuration**
+
+```toml
+format = """\
+  $username\
+  $hostname\
+  $directory\
+  $git_branch\
+  $git_commit\
+  $git_state\
+  $git_status\
+  $cmd_duration\
+  $custom\
+  $line_break\
+  $jobs\
+  $battery\
+  $time\
+  $character\
+  """
+```
+
+## Module `prefix` and `suffix` have been replaced by `format`
+
+Previously to v0.45.0, some modules would accept `prefix` and/or `suffix` in order to stylize the way that modules are rendered.
+
+Starship v0.45.0 instead accepts a `format` value, allowing for further customization of how modules are rendered. Instead of defining a prefix and suffix for the context-based variables, the variables can now be substituted from within a format string, which represents the module's output.
+
+**Example pre-v0.45.0 configuration**
+
+```toml
+[cmd_duration]
+prefix = "took "
+```
+
+**Example v0.45.0 configuration**
+
+```toml
+[cmd_duration]
+# $duration – The command duration (e.g. "15s")
+# $style    – The default style of the module (e.g. "bold yellow")
+format = "took [$duration]($style) "
+```
+
+### Affected Modules
+
+#### Character
+
+| Removed Property        | Replacement      |
+| ----------------------- | ---------------- |
+| `symbol`                | `success_symbol` |
+| `use_symbol_for_status` | `error_symbol`   |
+| `style_success`         | `success_symbol` |
+| `style_failure`         | `error_symbol`   |
+
+**Changes to the Default Configuration**
+
+```diff
+[character]
+-- symbol = "❯"
+-- error_symbol = "✖"
+-- use_symbol_for_status = true
+-- vicmd_symbol = "❮"
+++ success_symbol = "[❯](bold green)"
+++ error_symbol = "[❯](bold red)"
+++ vicmd_symbol = "[❮](bold green)"
+```
+
+Previously, the `use_symbol_for_status` property was used to configure the prompt to show the `error_symbol` when the last command resulted in a non-zero status code.
+
+With the release of v0.45.0, we now always use `error_symbol` after non-zero status codes, unifying `use_symbol_for_status` and `error_symbol` properties.
+
+To configure the prompt to use the older `use_symbol_for_status = true` configuration, add the following to your config file:
+
+```toml
+[character]
+error_symbol = "[✖](bold red)"
+```
+
+*Note:* The `character` element automatically adds a space after, so unlike the other `format` strings, we specifically do not add one in the above examples.
+
+#### Command Duration
+
+| Removed Property | Replacement |
+| ---------------- | ----------- |
+| `prefix`         | `format`    |
+
+**Changes to the Default Configuration**
+
+```diff
+[cmd_duration]
+-- prefix = "took "
+++ format = "took [$duration]($style) "
+```
+
+#### Directory
+
+| Removed Property | Replacement |
+| ---------------- | ----------- |
+| `prefix`         | `format`    |
+
+**Changes to the Default Configuration**
+
+```diff
+[directory]
+-- prefix = "in "
+++ format = "[$path]($style)[$read_only]($read_only_style) "
+```
+
+#### Environment Variable
+
+| Removed Property | Replacement |
+| ---------------- | ----------- |
+| `prefix`         | `format`    |
+| `suffix`         | `format`    |
+
+**Changes to the Default Configuration**
+
+```diff
+[env_var]
+-- prefix = ""
+-- suffix = ""
+++ format = "with [$env_value]($style) "
+```
+
+#### Git Commit
+
+| Removed Property | Replacement |
+| ---------------- | ----------- |
+| `prefix`         | `format`    |
+| `suffix`         | `format`    |
+
+**Changes to the Default Configuration**
+
+```diff
+[git_commit]
+-- prefix = "("
+-- suffix = ")"
+++ format = '[\($hash\)]($style) '
+```
+
+#### Git Status
+
+| Removed Property  | Replacement |
+| ----------------- | ----------- |
+| `prefix`          | `format`    |
+| `suffix`          | `format`    |
+| `show_sync_count` | `format`    |
+
+**Changes to the Default Configuration**
+
+```diff
+[git_status]
+-- prefix = "["
+-- suffix = "]"
+-- show_sync_count = false
+++ format = '([\[$all_status$ahead_behind\]]($style) )'
+```
+
+Previously, the `show_sync_count` property was used to configure the prompt to show the number of commits the branch was ahead or behind the remote branch.
+
+With the release of v0.45.0, this has been replaced with three separate properties, `ahead`, `behind`, and `diverged`.
+
+To configure the prompt to use the older `show_sync_count = true` configuration, set the following to your config file:
+
+```toml
+[git_status]
+ahead = "⇡${count}"
+diverged = "⇕⇡${ahead_count}⇣${behind_count}"
+behind = "⇣${count}"
+```
+
+#### Hostname
+
+| Removed Property | Replacement |
+| ---------------- | ----------- |
+| `prefix`         | `format`    |
+| `suffix`         | `format`    |
+
+**Changes to the Default Configuration**
+
+```diff
+[hostname]
+-- prefix = ""
+-- suffix = ""
+++ format = "[$hostname]($style) in "
+```
+
+#### Singularity
+
+| Removed Property | Replacement |
+| ---------------- | ----------- |
+| `label`          | `format`    |
+| `prefix`         | `format`    |
+| `suffix`         | `format`    |
+
+**Changes to the Default Configuration**
+
+```diff
+[singularity]
+-- prefix = ""
+-- suffix = ""
+++ format = '[$symbol\[$env\]]($style) '
+```
+
+#### Time
+
+| Removed Property | Replacement   |
+| ---------------- | ------------- |
+| `format`         | `time_format` |
+
+**Changes to the Default Configuration**
+
+```diff
+[time]
+-- format = "🕙[ %T ]"
+++ time_format = "%T"
+++ format = "at 🕙[$time]($style) "
+```
+
+#### Custom Commands
+
+| Removed Property | Replacement |
+| ---------------- | ----------- |
+| `prefix`         | `format`    |
+| `suffix`         | `format`    |
+
+**Changes to the Default Configuration**
+
+```diff
+[custom.example]
+-- prefix = ""
+-- suffix = ""
+++ format = "[$symbol$output]($style) "
+```

docs/ko-KR/presets/README.md

@@ -0,0 +1,92 @@
+# Presets
+
+Here is a collection of community-submitted configuration presets for Starship. If you have a preset to share, please [submit a PR](https://github.com/starship/starship/edit/master/docs/presets/README.md) updating this file! 😊
+
+## Nerd Font Symbols
+
+This preset doesn't change anything except for the symbols used for each module. If emojis aren't your thing, this might catch your eye!
+
+![Screenshot of Nerd Font Symbols preset](/presets/nerd-font-symbols.png)
+
+### Prerequisites
+
+- A [Nerd Font](https://www.nerdfonts.com/) installed and enabled in your terminal (the example uses Fira Code Nerd Font)
+
+### Configuration
+
+```toml
+[aws]
+symbol = "  "
+
+[conda]
+symbol = " "
+
+[dart]
+symbol = " "
+
+[directory]
+read_only = " "
+
+[docker]
+symbol = " "
+
+[elixir]
+symbol = " "
+
+[elm]
+symbol = " "
+
+[git_branch]
+symbol = " "
+
+[golang]
+symbol = " "
+
+[haskell]
+symbol = " "
+
+[hg_branch]
+symbol = " "
+
+[java]
+symbol = " "
+
+[julia]
+symbol = " "
+
+[memory_usage]
+symbol = " "
+
+[nim]
+symbol = " "
+
+[nix_shell]
+symbol = " "
+
+[nodejs]
+symbol = " "
+
+[package]
+symbol = " "
+
+[perl]
+symbol = " "
+
+[php]
+symbol = " "
+
+[python]
+symbol = " "
+
+[ruby]
+symbol = " "
+
+[rust]
+symbol = " "
+
+[scala]
+symbol = " "
+
+[swift]
+symbol = "ﯣ "
+```

docs/nl-NL/README.md

@@ -0,0 +1,136 @@
+---
+home: true
+heroImage: /logo.svg
+heroText:
+tagline: The minimal, blazing-fast, and infinitely customizable prompt for any shell!
+actionText: Get Started →
+actionLink: ./guide/
+features:
+  - 
+    title: Compatibility First
+    details: Works on the most common shells on the most common operating systems. Use it everywhere!
+  - 
+    title: Rust-Powered
+    details: Brings the best-in-class speed and safety of Rust, to make your prompt as quick and reliable as possible.
+  - 
+    title: Customizable
+    details: Every little detail is customizable to your liking, to make this prompt as minimal or feature-rich as you'd like it to be.
+footer: ISC Licensed | Copyright © 2019-present Starship Contributors
+#Used for the description meta tag, for SEO
+metaTitle: "Starship: Cross-Shell Prompt"
+description: Starship is the minimal, blazing fast, and extremely customizable prompt for any shell! Shows the information you need, while staying sleek and minimal. Quick installation available for Bash, Fish, ZSH, Ion, and PowerShell.
+---
+
+<div class="center">
+  <video class="demo-video" muted autoplay loop playsinline>
+    <source src="/demo.webm" type="video/webm">
+    <source src="/demo.mp4" type="video/mp4">
+  </video>
+</div>
+
+### Quick Install
+
+1. Install the **starship** binary:
+
+
+   #### Install Latest Version
+
+   With Shell:
+
+   ```sh
+   curl -fsSL https://starship.rs/install.sh | bash
+   ```
+
+
+   #### Install via Package Manager
+
+   With [Homebrew](https://brew.sh/):
+
+   ```sh
+   brew install starship
+   ```
+
+   With [Scoop](https://scoop.sh):
+
+   ```powershell
+   scoop install starship
+   ```
+
+1. Add the init script to your shell's config file:
+
+
+   #### Bash
+
+   Add the following to the end of `~/.bashrc`:
+
+   ```sh
+   # ~/.bashrc
+
+   eval "$(starship init bash)"
+   ```
+
+
+   #### Fish
+
+   Add the following to the end of `~/.config/fish/config.fish`:
+
+   ```sh
+   # ~/.config/fish/config.fish
+
+   starship init fish | source
+   ```
+
+
+   #### Zsh
+
+   Add the following to the end of `~/.zshrc`:
+
+   ```sh
+   # ~/.zshrc
+
+   eval "$(starship init zsh)"
+   ```
+
+
+   #### Powershell
+
+   Add the following to the end of `Microsoft.PowerShell_profile.ps1`. You can check the location of this file by querying the `$PROFILE` variable in PowerShell. Typically the path is `~\Documents\PowerShell\Microsoft.PowerShell_profile.ps1` or `~/.config/powershell/Microsoft.PowerShell_profile.ps1` on -Nix.
+
+   ```sh
+   Invoke-Expression (&starship init powershell)
+   ```
+
+
+   #### Ion
+
+   Add the following to the end of `~/.config/ion/initrc`:
+
+   ```sh
+   # ~/.config/ion/initrc
+
+   eval $(starship init ion)
+   ```
+
+   #### Elvish
+
+   ::: warning Only elvish v0.15 or higher is supported. :::
+
+   Add the following to the end of `~/.elvish/rc.elv`:
+
+   ```sh
+   # ~/.elvish/rc.elv
+
+   eval (starship init elvish)
+   ```
+
+
+   #### Tcsh
+
+   Add the following to the end of `~/.tcshrc`:
+
+   ```sh
+   # ~/.tcshrc
+
+   eval `starship init tcsh`
+   ```
+

docs/nl-NL/advanced-config/README.md

@@ -0,0 +1,93 @@
+# Advanced Configuration
+
+While Starship is a versatile shell, sometimes you need to do more than edit `starship.toml` to get it to do certain things. This page details some of the more advanced configuration techniques used in starship.
+
+::: warning
+
+The configurations in this section are subject to change in future releases of Starship.
+
+:::
+
+## Custom pre-prompt and pre-execution Commands in Bash
+
+Bash does not have a formal preexec/precmd framework like most other shells. Because of this, it is difficult to provide fully customizable hooks in `bash`. However, Starship does give you limited ability to insert your own functions into the prompt-rendering procedure:
+
+- To run a custom function right before the prompt is drawn, define a new function and then assign its name to `starship_precmd_user_func`. For example, to draw a rocket before the prompt, you would do
+
+```bash
+function blastoff(){
+    echo "🚀"
+}
+starship_precmd_user_func="blastoff"
+```
+
+- To run a custom function right before a command runs, you can use the [`DEBUG` trap mechanism](https://jichu4n.com/posts/debug-trap-and-prompt_command-in-bash/). However, you **must** trap the DEBUG signal *before* initializing Starship! Starship can preserve the value of the DEBUG trap, but if the trap is overwritten after starship starts up, some functionality will break.
+
+```bash
+function blastoff(){
+    echo "🚀"
+}
+trap blastoff DEBUG     # Trap DEBUG *before* running starship
+eval $(starship init bash)
+```
+
+## Change Window Title
+
+Some shell prompts will automatically change the window title for you (e.g. to reflect your working directory). Fish even does it by default. Starship does not do this, but it's fairly straightforward to add this functionality to `bash` or `zsh`.
+
+First, define a window title change function (identical in bash and zsh):
+
+```bash
+function set_win_title(){
+    echo -ne "\033]0; YOUR_WINDOW_TITLE_HERE \007"
+}
+```
+
+You can use variables to customize this title (`$USER`, `$HOSTNAME`, and `$PWD` are popular choices).
+
+In `bash`, set this function to be the precmd starship function:
+
+```bash
+starship_precmd_user_func="set_win_title"
+```
+
+In `zsh`, add this to the `precmd_functions` array:
+
+```bash
+precmd_functions+=(set_win_title)
+```
+
+If you like the result, add these lines to your shell configuration file (`~/.bashrc` or `~/.zshrc`) to make it permanent.
+
+For example, if you want to display your current directory in your terminal tab title, add the following snippet to your `~/.bashrc` or `~/.zshrc`:
+
+```bash
+function set_win_title(){
+    echo -ne "\033]0; $(basename $PWD) \007"
+}
+starship_precmd_user_func="set_win_title"
+```
+
+## Style Strings
+
+Style strings are a list of words, separated by whitespace. The words are not case sensitive (i.e. `bold` and `BoLd` are considered the same string). Each word can be one of the following:
+
+  - `bold`
+  - `underline`
+  - `dimmed`
+  - `bg:<color>`
+  - `fg:<color>`
+  - `<color>`
+  - `none`
+
+where `<color>` is a color specifier (discussed below). `fg:<color>` and `<color>` currently do the same thing , though this may change in the future. The order of words in the string does not matter.
+
+The `none` token overrides all other tokens in a string if it is not part of a `bg:` specifier, so that e.g. `fg:red none fg:blue` will still create a string with no styling. `bg:none`  sets the background to the default color so `fg:red bg:none` is equivalent to `red` or `fg:red` and `bg:green fg:red bg:none` is also equivalent to `fg:red` or `red`. It may become an error to use `none` in conjunction with other tokens in the future.
+
+A color specifier can be one of the following:
+
+ - One of the standard terminal colors: `black`, `red`, `green`, `blue`, `yellow`, `purple`, `cyan`, `white`. You can optionally prefix these with `bright-` to get the bright version (e.g. `bright-white`).
+ - A `#` followed by a six-digit hexadecimal number. This specifies an [RGB color hex code](https://www.w3schools.com/colors/colors_hexadecimal.asp).
+ - A number between 0-255. This specifies an [8-bit ANSI Color Code](https://i.stack.imgur.com/KTSQa.png).
+
+If multiple colors are specified for foreground/background, the last one in the string will take priority.

docs/nl-NL/faq/README.md

@@ -0,0 +1,96 @@
+# FAQ
+
+## What is the configuration used in the demo GIF?
+
+- **Terminal Emulator**: [iTerm2](https://iterm2.com/)
+  - **Theme**: Minimal
+  - **Color Scheme**: [Snazzy](https://github.com/sindresorhus/iterm2-snazzy)
+  - **Font**: [FiraCode Nerd Font](https://www.nerdfonts.com/font-downloads)
+- **Shell**: [Fish Shell](https://fishshell.com/)
+  - **Configuration**: [matchai's Dotfiles](https://github.com/matchai/dotfiles/blob/b6c6a701d0af8d145a8370288c00bb9f0648b5c2/.config/fish/config.fish)
+  - **Prompt**: [Starship](https://starship.rs/)
+
+## How do I get command completion as shown in the demo GIF?
+
+Completion support, or autocomplete, is provided by your shell of choice. In the case of the demo, the demo was done with [Fish Shell](https://fishshell.com/), which provides completions by default. If you use Z Shell (zsh), I'd suggest taking a look at [zsh-autosuggestions](https://github.com/zsh-users/zsh-autosuggestions).
+
+## 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. Why isn't my preferred shell supported?
+
+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:
+
+```sh
+# 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](https://github.com/starship/starship/blob/master/src/init/starship.bash) built into Starship is slightly more complex to allow for advanced features like the [Command Duration module](https://starship.rs/config/#command-duration) 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:
+
+```sh
+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`:
+
+```sh
+curl -fsSL https://starship.rs/install.sh | bash -s -- --platform unknown-linux-musl
+```
+
+## I see symbols I don't understand or expect, what do they mean?
+
+If you see symbols that you don't recognise you can use `starship explain` to explain the currently showing modules.
+
+## 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](https://www.tecmint.com/set-system-locales-in-linux/).
+- 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](https://www.google.com/get/noto/help/emoji/) is a popular choice.
+- You are using a [Nerd Font](https://www.nerdfonts.com/).
+
+To test your system, run the following commands in a terminal:
+
+```sh
+echo -e "\xf0\x9f\x90\x8d"
+echo -e "\xee\x82\xa0"
+```
+
+The first line should produce a [snake emoji](https://emojipedia.org/snake/), while the second should produce a [powerline branch symbol (e0a0)](https://github.com/ryanoasis/powerline-extra-symbols#glyphs).
+
+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!](https://github.com/starship/starship/issues/new/choose)
+
+## 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.
+1. 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:
+
+```sh
+# Locate and delete the starship binary
+rm "$(which starship)"
+```

docs/nl-NL/guide/README.md

@@ -0,0 +1,311 @@
+<p align="center">
+  <img
+    width="400"
+    src="https://raw.githubusercontent.com/starship/starship/master/media/logo.png"
+    alt="Starship – Cross-shell prompt"
+ />
+</p>
+
+<p align="center">
+  <a href="https://github.com/starship/starship/actions"
+    ><img
+      src="https://img.shields.io/github/workflow/status/starship/starship/Main workflow/master?label=workflow&style=flat-square"
+      alt="GitHub Actions workflow status"
+ /></a>
+  <a href="https://crates.io/crates/starship"
+    ><img
+      src="https://img.shields.io/crates/v/starship?style=flat-square"
+      alt="Crates.io version"
+ /></a>
+  <a href="https://repology.org/project/starship/versions"
+    ><img
+      src="https://img.shields.io/repology/repositories/starship?label=in%20repositories&style=flat-square"
+      alt="Packaging status" /></a
+><br />
+  <a href="https://discord.gg/starship"
+    ><img
+      src="https://img.shields.io/discord/567163873606500352?label=discord&logoColor=white&style=flat-square"
+      alt="Chat on Discord"
+ /></a>
+  <a href="https://twitter.com/StarshipPrompt"
+    ><img
+      src="https://img.shields.io/badge/twitter-@StarshipPrompt-1DA1F3?style=flat-square"
+      alt="Follow @StarshipPrompt on Twitter"
+ /></a>
+</p>
+
+<p align="center">
+  <a href="https://starship.rs">Website</a>
+  ·
+  <a href="#🚀-installation">Installation</a>
+  ·
+  <a href="https://starship.rs/config/">Configuration</a>
+</p>
+
+<p align="center">
+  <a href="https://github.com/starship/starship/blob/master/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-us.png"
+      alt="English"
+ /></a>
+  &nbsp;
+  <a
+    href="https://github.com/starship/starship/blob/master/docs/ja-JP/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-jp.png"
+      alt="日本語"
+ /></a>
+  &nbsp;
+  <a
+    href="https://github.com/starship/starship/blob/master/docs/zh-TW/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-tw.png"
+      alt="繁體中文"
+ /></a>
+  &nbsp;
+  <a
+    href="https://github.com/starship/starship/blob/master/docs/ru-RU/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-ru.png"
+      alt="Русский"
+ /></a>
+  &nbsp;
+  <a
+    href="https://github.com/starship/starship/blob/master/docs/de-DE/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-de.png"
+      alt="Deutsch"
+ /></a>
+  &nbsp;
+  <a
+    href="https://github.com/starship/starship/blob/master/docs/zh-CN/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-cn.png"
+      alt="简体中文"
+ /></a>
+  &nbsp;
+  <a 
+    href="https://github.com/starship/starship/blob/master/docs/es-ES/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-es.png"
+      alt="Español"
+ /></a>
+  &nbsp;
+  <a 
+    href="https://github.com/starship/starship/blob/master/docs/fr-FR/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-fr.png"
+      alt="Français"
+ /></a>
+  &nbsp;
+  <a 
+    href="https://github.com/starship/starship/blob/master/docs/vi-VN/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-vn.png"
+      alt="Tiếng Việt"
+ /></a>
+</p>
+
+<h1></h1>
+
+<img
+  src="https://raw.githubusercontent.com/starship/starship/master/media/demo.gif"
+  alt="Starship with iTerm2 and the Snazzy theme"
+  width="50%"
+  align="right"
+ />
+
+**The minimal, blazing-fast, and infinitely customizable prompt for any shell!**
+
+- **Fast:** it's fast – _really really_ fast! 🚀
+- **Customizable:** configure every aspect of your prompt.
+- **Universal:** works on any shell, on any operating system.
+- **Intelligent:** shows relevant information at a glance.
+- **Feature rich:** support for all your favorite tools.
+- **Easy:** quick to install – start using it in minutes.
+
+<p align="center">
+<a href="https://starship.rs/config/"><strong>Explore the Starship docs&nbsp;&nbsp;▶</strong></a>
+</p>
+
+<a name="🚀-installation"></a>
+
+## 🚀 Installation
+
+### Prerequisites
+
+- A [Nerd Font](https://www.nerdfonts.com/) installed and enabled in your terminal (for example, try the [Fira Code Nerd Font](https://www.nerdfonts.com/font-downloads)).
+
+### Getting Started
+
+**Note**: due to the proliferation of different platforms, only a subset of supported platforms are shown below. Can't see yours? Have a look at the [extra platform instructions](https://starship.rs/installing/).
+
+1. Install the **starship** binary:
+
+
+   #### Install Latest Version
+
+
+   ##### From prebuilt binary, with Shell:
+
+   ```sh
+   curl -fsSL https://starship.rs/install.sh | bash
+   ```
+
+
+   #### Install via Package Manager
+
+
+   ##### Example: [Homebrew](https://brew.sh/):
+
+   ```sh
+   brew install starship
+   ```
+
+
+   ##### With [Scoop](https://scoop.sh):
+
+   ```powershell
+   scoop install starship
+   ```
+
+2. Add the init script to your shell's config file:
+
+
+   #### Bash
+
+   Add the following to the end of `~/.bashrc`:
+
+   ```sh
+   # ~/.bashrc
+
+   eval "$(starship init bash)"
+   ```
+
+
+   #### Fish
+
+   Add the following to the end of `~/.config/fish/config.fish`:
+
+   ```sh
+   # ~/.config/fish/config.fish
+
+   starship init fish | source
+   ```
+
+
+   #### Zsh
+
+   Add the following to the end of `~/.zshrc`:
+
+   ```sh
+   # ~/.zshrc
+
+   eval "$(starship init zsh)"
+   ```
+
+
+   #### PowerShell
+
+   Add the following to the end of `Microsoft.PowerShell_profile.ps1`. You can check the location of this file by querying the `$PROFILE` variable in PowerShell. Typically the path is `~\Documents\PowerShell\Microsoft.PowerShell_profile.ps1` or `~/.config/powershell/Microsoft.PowerShell_profile.ps1` on -Nix.
+
+   ```powershell
+   Invoke-Expression (&starship init powershell)
+   ```
+
+
+   #### Ion
+
+   Add the following to the end of `~/.config/ion/initrc`:
+
+   ```sh
+   # ~/.config/ion/initrc
+
+   eval $(starship init ion)
+   ```
+
+
+   #### Elvish
+
+   **Warning** Only elvish v0.15 or higher is supported. Add the following to the end of `~/.elvish/rc.elv`:
+
+   ```sh
+   # ~/.elvish/rc.elv
+
+   eval (starship init elvish)
+   ```
+
+
+   #### Tcsh
+
+   Add the following to the end of `~/.tcshrc`:
+
+   ```sh
+   # ~/.tcshrc
+
+   eval `starship init tcsh`
+   ```
+
+## 🤝 Contributing
+
+We are always looking for contributors of **all skill levels**! If you're looking to ease your way into the project, try out a [good first issue](https://github.com/starship/starship/labels/🌱%20good%20first%20issue).
+
+If you are fluent in a non-English language, we greatly appreciate any help keeping our docs translated and up-to-date in other languages. If you would like to help, translations can be contributed on the [Starship Crowdin](https://translate.starship.rs/).
+
+If you are interested in helping contribute to starship, please take a look at our [Contributing Guide](https://github.com/starship/starship/blob/master/CONTRIBUTING.md). Also, feel free to drop into our [Discord server](https://discord.gg/8Jzqu3T) and say hi. 👋
+
+### Code Contributors
+
+This project exists thanks to all the people who contribute. [[Contribute](https://github.com/starship/starship/blob/master/CONTRIBUTING.md)].
+<a href="https://github.com/starship/starship/graphs/contributors"><img src="https://opencollective.com/starship/contributors.svg?width=890&button=false" /></a>
+
+### Financial Contributors
+
+Become a financial contributor and help us sustain our community. [[Contribute](https://opencollective.com/starship/contribute)]
+
+#### Individuals
+
+<a href="https://opencollective.com/starship"><img src="https://opencollective.com/starship/individuals.svg?width=890"></a>
+
+#### Organizations
+
+Support this project with your organization. Your logo will show up here with a link to your website. [[Contribute](https://opencollective.com/starship/contribute)]
+
+<a href="https://opencollective.com/starship/organization/0/website"><img src="https://opencollective.com/starship/organization/0/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/1/website"><img src="https://opencollective.com/starship/organization/1/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/2/website"><img src="https://opencollective.com/starship/organization/2/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/3/website"><img src="https://opencollective.com/starship/organization/3/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/4/website"><img src="https://opencollective.com/starship/organization/4/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/5/website"><img src="https://opencollective.com/starship/organization/5/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/6/website"><img src="https://opencollective.com/starship/organization/6/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/7/website"><img src="https://opencollective.com/starship/organization/7/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/8/website"><img src="https://opencollective.com/starship/organization/8/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/9/website"><img src="https://opencollective.com/starship/organization/9/avatar.svg"></a>
+
+## 💭 Inspired By
+
+Please check out these previous works that helped inspire the creation of starship. 🙏
+
+- **[denysdovhan/spaceship-prompt](https://github.com/denysdovhan/spaceship-prompt)** - A ZSH prompt for astronauts.
+
+- **[denysdovhan/robbyrussell-node](https://github.com/denysdovhan/robbyrussell-node)** - Cross-shell robbyrussell theme written in JavaScript.
+
+- **[reujab/silver](https://github.com/reujab/silver)** - A cross-shell customizable powerline-like prompt with icons.
+
+<p align="center">
+    <br>
+    <img width="100" src="https://raw.githubusercontent.com/starship/starship/master/media/icon.png" alt="Starship rocket icon">
+</p>
+
+## 📝 License
+
+Copyright © 2019-present, [Starship Contributors](https://github.com/starship/starship/graphs/contributors).<br /> This project is [ISC](https://github.com/starship/starship/blob/master/LICENSE) licensed.

docs/nl-NL/installing/README.md

@@ -0,0 +1,84 @@
+# 🚀 Advanced Installation
+
+To install starship, you need to do two things:
+
+1. Get the **starship** binary onto your computer
+1. Tell your shell to use the starship binary as its prompt by modifying its init scripts
+
+For most users, the instructions on [the main page](/guide/#🚀-installation) will work great. However, for some more specialized platforms, different instructions are needed.
+
+There are so many platforms out there that they didn't fit into the main README.md file, so here are some installation instructions for other platforms from the community. Is yours not here? Please do add it here if you figure it out!
+
+## [Chocolatey](https://chocolatey.org)
+
+### Prerequisites
+
+Head over to the [Chocolatey installation page](https://chocolatey.org/install) and follow the instructions to install Chocolatey.
+
+### Installation
+
+```powershell
+choco install starship
+```
+
+## [termux](https://termux.com)
+
+### Prerequisites
+
+```sh
+pkg install getconf
+```
+
+### Installation
+
+```sh
+curl -fsSL https://starship.rs/install.sh | bash -s -- -b /data/data/com.termux/files/usr/bin
+```
+
+## [Nix](https://nixos.wiki/wiki/Nix)
+
+### Getting the Binary
+
+#### Imperatively
+
+```sh
+nix-env -iA nixos.starship
+```
+
+#### Declarative, single user, via [home-manager](home-manager)
+
+Enable the `programs.starship` module in your `home.nix` file, and add your settings
+
+```nix
+{
+  programs.starship = {
+    enable = true;
+    enableZshIntegration = true;
+    # Configuration written to ~/.config/starship.toml
+    settings = {
+      # add_newline = false;
+
+      # character = {
+      #   success_symbol = "[➜](bold green)";
+      #   error_symbol = "[➜](bold red)";
+      # };
+
+      # package.disabled = true;
+    };
+  };
+}
+```
+
+then run
+
+```sh
+home-manager switch
+```
+
+#### Declarative, system-wide, with NixOS
+
+Add `pkgs.starship` to `environment.systemPackages` in your `configuration.nix`, then run
+
+```sh
+sudo nixos-rebuild switch
+```

docs/nl-NL/migrating-to-0.45.0/README.md

@@ -0,0 +1,267 @@
+# Migrating to v0.45.0
+
+Starship v0.45.0 is a release containing breaking changes, in preparation for the big v1.0.0. We have made some major changes around how configuration is done on the prompt, to allow for a greater degree of customization.
+
+This guide is intended to walk you through the breaking changes.
+
+## `prompt_order` has been replaced by a root-level `format`
+
+Previously to v0.45.0, `prompt_order` would accept an array of module names in the order which they should be rendered by Starship.
+
+Starship v0.45.0 instead accepts a `format` value, allowing for customization of the prompt outside of the modules themselves.
+
+**Example pre-v0.45.0 configuration**
+
+```toml
+prompt_order = [
+  "username",
+  "hostname",
+  "directory",
+  "git_branch",
+  "git_commit",
+  "git_state",
+  "git_status",
+  "cmd_duration",
+  "custom",
+  "line_break",
+  "jobs",
+  "battery",
+  "time",
+  "character",
+]
+```
+
+**Example v0.45.0 configuration**
+
+```toml
+format = """\
+  $username\
+  $hostname\
+  $directory\
+  $git_branch\
+  $git_commit\
+  $git_state\
+  $git_status\
+  $cmd_duration\
+  $custom\
+  $line_break\
+  $jobs\
+  $battery\
+  $time\
+  $character\
+  """
+```
+
+## Module `prefix` and `suffix` have been replaced by `format`
+
+Previously to v0.45.0, some modules would accept `prefix` and/or `suffix` in order to stylize the way that modules are rendered.
+
+Starship v0.45.0 instead accepts a `format` value, allowing for further customization of how modules are rendered. Instead of defining a prefix and suffix for the context-based variables, the variables can now be substituted from within a format string, which represents the module's output.
+
+**Example pre-v0.45.0 configuration**
+
+```toml
+[cmd_duration]
+prefix = "took "
+```
+
+**Example v0.45.0 configuration**
+
+```toml
+[cmd_duration]
+# $duration – The command duration (e.g. "15s")
+# $style    – The default style of the module (e.g. "bold yellow")
+format = "took [$duration]($style) "
+```
+
+### Affected Modules
+
+#### Character
+
+| Removed Property        | Replacement      |
+| ----------------------- | ---------------- |
+| `symbol`                | `success_symbol` |
+| `use_symbol_for_status` | `error_symbol`   |
+| `style_success`         | `success_symbol` |
+| `style_failure`         | `error_symbol`   |
+
+**Changes to the Default Configuration**
+
+```diff
+[character]
+-- symbol = "❯"
+-- error_symbol = "✖"
+-- use_symbol_for_status = true
+-- vicmd_symbol = "❮"
+++ success_symbol = "[❯](bold green)"
+++ error_symbol = "[❯](bold red)"
+++ vicmd_symbol = "[❮](bold green)"
+```
+
+Previously, the `use_symbol_for_status` property was used to configure the prompt to show the `error_symbol` when the last command resulted in a non-zero status code.
+
+With the release of v0.45.0, we now always use `error_symbol` after non-zero status codes, unifying `use_symbol_for_status` and `error_symbol` properties.
+
+To configure the prompt to use the older `use_symbol_for_status = true` configuration, add the following to your config file:
+
+```toml
+[character]
+error_symbol = "[✖](bold red)"
+```
+
+*Note:* The `character` element automatically adds a space after, so unlike the other `format` strings, we specifically do not add one in the above examples.
+
+#### Command Duration
+
+| Removed Property | Replacement |
+| ---------------- | ----------- |
+| `prefix`         | `format`    |
+
+**Changes to the Default Configuration**
+
+```diff
+[cmd_duration]
+-- prefix = "took "
+++ format = "took [$duration]($style) "
+```
+
+#### Directory
+
+| Removed Property | Replacement |
+| ---------------- | ----------- |
+| `prefix`         | `format`    |
+
+**Changes to the Default Configuration**
+
+```diff
+[directory]
+-- prefix = "in "
+++ format = "[$path]($style)[$read_only]($read_only_style) "
+```
+
+#### Environment Variable
+
+| Removed Property | Replacement |
+| ---------------- | ----------- |
+| `prefix`         | `format`    |
+| `suffix`         | `format`    |
+
+**Changes to the Default Configuration**
+
+```diff
+[env_var]
+-- prefix = ""
+-- suffix = ""
+++ format = "with [$env_value]($style) "
+```
+
+#### Git Commit
+
+| Removed Property | Replacement |
+| ---------------- | ----------- |
+| `prefix`         | `format`    |
+| `suffix`         | `format`    |
+
+**Changes to the Default Configuration**
+
+```diff
+[git_commit]
+-- prefix = "("
+-- suffix = ")"
+++ format = '[\($hash\)]($style) '
+```
+
+#### Git Status
+
+| Removed Property  | Replacement |
+| ----------------- | ----------- |
+| `prefix`          | `format`    |
+| `suffix`          | `format`    |
+| `show_sync_count` | `format`    |
+
+**Changes to the Default Configuration**
+
+```diff
+[git_status]
+-- prefix = "["
+-- suffix = "]"
+-- show_sync_count = false
+++ format = '([\[$all_status$ahead_behind\]]($style) )'
+```
+
+Previously, the `show_sync_count` property was used to configure the prompt to show the number of commits the branch was ahead or behind the remote branch.
+
+With the release of v0.45.0, this has been replaced with three separate properties, `ahead`, `behind`, and `diverged`.
+
+To configure the prompt to use the older `show_sync_count = true` configuration, set the following to your config file:
+
+```toml
+[git_status]
+ahead = "⇡${count}"
+diverged = "⇕⇡${ahead_count}⇣${behind_count}"
+behind = "⇣${count}"
+```
+
+#### Hostname
+
+| Removed Property | Replacement |
+| ---------------- | ----------- |
+| `prefix`         | `format`    |
+| `suffix`         | `format`    |
+
+**Changes to the Default Configuration**
+
+```diff
+[hostname]
+-- prefix = ""
+-- suffix = ""
+++ format = "[$hostname]($style) in "
+```
+
+#### Singularity
+
+| Removed Property | Replacement |
+| ---------------- | ----------- |
+| `label`          | `format`    |
+| `prefix`         | `format`    |
+| `suffix`         | `format`    |
+
+**Changes to the Default Configuration**
+
+```diff
+[singularity]
+-- prefix = ""
+-- suffix = ""
+++ format = '[$symbol\[$env\]]($style) '
+```
+
+#### Time
+
+| Removed Property | Replacement   |
+| ---------------- | ------------- |
+| `format`         | `time_format` |
+
+**Changes to the Default Configuration**
+
+```diff
+[time]
+-- format = "🕙[ %T ]"
+++ time_format = "%T"
+++ format = "at 🕙[$time]($style) "
+```
+
+#### Custom Commands
+
+| Removed Property | Replacement |
+| ---------------- | ----------- |
+| `prefix`         | `format`    |
+| `suffix`         | `format`    |
+
+**Changes to the Default Configuration**
+
+```diff
+[custom.example]
+-- prefix = ""
+-- suffix = ""
+++ format = "[$symbol$output]($style) "
+```

docs/nl-NL/presets/README.md

@@ -0,0 +1,92 @@
+# Presets
+
+Here is a collection of community-submitted configuration presets for Starship. If you have a preset to share, please [submit a PR](https://github.com/starship/starship/edit/master/docs/presets/README.md) updating this file! 😊
+
+## Nerd Font Symbols
+
+This preset doesn't change anything except for the symbols used for each module. If emojis aren't your thing, this might catch your eye!
+
+![Screenshot of Nerd Font Symbols preset](/presets/nerd-font-symbols.png)
+
+### Prerequisites
+
+- A [Nerd Font](https://www.nerdfonts.com/) installed and enabled in your terminal (the example uses Fira Code Nerd Font)
+
+### Configuration
+
+```toml
+[aws]
+symbol = "  "
+
+[conda]
+symbol = " "
+
+[dart]
+symbol = " "
+
+[directory]
+read_only = " "
+
+[docker]
+symbol = " "
+
+[elixir]
+symbol = " "
+
+[elm]
+symbol = " "
+
+[git_branch]
+symbol = " "
+
+[golang]
+symbol = " "
+
+[haskell]
+symbol = " "
+
+[hg_branch]
+symbol = " "
+
+[java]
+symbol = " "
+
+[julia]
+symbol = " "
+
+[memory_usage]
+symbol = " "
+
+[nim]
+symbol = " "
+
+[nix_shell]
+symbol = " "
+
+[nodejs]
+symbol = " "
+
+[package]
+symbol = " "
+
+[perl]
+symbol = " "
+
+[php]
+symbol = " "
+
+[python]
+symbol = " "
+
+[ruby]
+symbol = " "
+
+[rust]
+symbol = " "
+
+[scala]
+symbol = " "
+
+[swift]
+symbol = "ﯣ "
+```

docs/package.json

@@ -4,9 +4,9 @@
     "build": "vuepress build"
   },
   "devDependencies": {
-    "@vuepress/plugin-google-analytics": "^1.7.1",
-    "vuepress": "^1.7.1",
-    "vuepress-theme-default-prefers-color-scheme": "^1.1.2",
+    "@vuepress/plugin-google-analytics": "^1.8.2",
+    "vuepress": "^1.8.2",
+    "vuepress-theme-default-prefers-color-scheme": "^2.0.0",
     "vuepress-plugin-sitemap": "^2.3.1"
   }
 }

docs/pl-PL/README.md

@@ -0,0 +1,136 @@
+---
+home: true
+heroImage: /logo.svg
+heroText:
+tagline: The minimal, blazing-fast, and infinitely customizable prompt for any shell!
+actionText: Get Started →
+actionLink: ./guide/
+features:
+  - 
+    title: Compatibility First
+    details: Works on the most common shells on the most common operating systems. Use it everywhere!
+  - 
+    title: Rust-Powered
+    details: Brings the best-in-class speed and safety of Rust, to make your prompt as quick and reliable as possible.
+  - 
+    title: Customizable
+    details: Every little detail is customizable to your liking, to make this prompt as minimal or feature-rich as you'd like it to be.
+footer: ISC Licensed | Copyright © 2019-present Starship Contributors
+#Used for the description meta tag, for SEO
+metaTitle: "Starship: Cross-Shell Prompt"
+description: Starship is the minimal, blazing fast, and extremely customizable prompt for any shell! Shows the information you need, while staying sleek and minimal. Quick installation available for Bash, Fish, ZSH, Ion, and PowerShell.
+---
+
+<div class="center">
+  <video class="demo-video" muted autoplay loop playsinline>
+    <source src="/demo.webm" type="video/webm">
+    <source src="/demo.mp4" type="video/mp4">
+  </video>
+</div>
+
+### Quick Install
+
+1. Install the **starship** binary:
+
+
+   #### Install Latest Version
+
+   With Shell:
+
+   ```sh
+   curl -fsSL https://starship.rs/install.sh | bash
+   ```
+
+
+   #### Install via Package Manager
+
+   With [Homebrew](https://brew.sh/):
+
+   ```sh
+   brew install starship
+   ```
+
+   With [Scoop](https://scoop.sh):
+
+   ```powershell
+   scoop install starship
+   ```
+
+1. Add the init script to your shell's config file:
+
+
+   #### Bash
+
+   Add the following to the end of `~/.bashrc`:
+
+   ```sh
+   # ~/.bashrc
+
+   eval "$(starship init bash)"
+   ```
+
+
+   #### Fish
+
+   Add the following to the end of `~/.config/fish/config.fish`:
+
+   ```sh
+   # ~/.config/fish/config.fish
+
+   starship init fish | source
+   ```
+
+
+   #### Zsh
+
+   Add the following to the end of `~/.zshrc`:
+
+   ```sh
+   # ~/.zshrc
+
+   eval "$(starship init zsh)"
+   ```
+
+
+   #### Powershell
+
+   Add the following to the end of `Microsoft.PowerShell_profile.ps1`. You can check the location of this file by querying the `$PROFILE` variable in PowerShell. Typically the path is `~\Documents\PowerShell\Microsoft.PowerShell_profile.ps1` or `~/.config/powershell/Microsoft.PowerShell_profile.ps1` on -Nix.
+
+   ```sh
+   Invoke-Expression (&starship init powershell)
+   ```
+
+
+   #### Ion
+
+   Add the following to the end of `~/.config/ion/initrc`:
+
+   ```sh
+   # ~/.config/ion/initrc
+
+   eval $(starship init ion)
+   ```
+
+   #### Elvish
+
+   ::: warning Only elvish v0.15 or higher is supported. :::
+
+   Add the following to the end of `~/.elvish/rc.elv`:
+
+   ```sh
+   # ~/.elvish/rc.elv
+
+   eval (starship init elvish)
+   ```
+
+
+   #### Tcsh
+
+   Add the following to the end of `~/.tcshrc`:
+
+   ```sh
+   # ~/.tcshrc
+
+   eval `starship init tcsh`
+   ```
+

docs/pl-PL/advanced-config/README.md

@@ -0,0 +1,93 @@
+# Advanced Configuration
+
+While Starship is a versatile shell, sometimes you need to do more than edit `starship.toml` to get it to do certain things. This page details some of the more advanced configuration techniques used in starship.
+
+::: warning
+
+The configurations in this section are subject to change in future releases of Starship.
+
+:::
+
+## Custom pre-prompt and pre-execution Commands in Bash
+
+Bash does not have a formal preexec/precmd framework like most other shells. Because of this, it is difficult to provide fully customizable hooks in `bash`. However, Starship does give you limited ability to insert your own functions into the prompt-rendering procedure:
+
+- To run a custom function right before the prompt is drawn, define a new function and then assign its name to `starship_precmd_user_func`. For example, to draw a rocket before the prompt, you would do
+
+```bash
+function blastoff(){
+    echo "🚀"
+}
+starship_precmd_user_func="blastoff"
+```
+
+- To run a custom function right before a command runs, you can use the [`DEBUG` trap mechanism](https://jichu4n.com/posts/debug-trap-and-prompt_command-in-bash/). However, you **must** trap the DEBUG signal *before* initializing Starship! Starship can preserve the value of the DEBUG trap, but if the trap is overwritten after starship starts up, some functionality will break.
+
+```bash
+function blastoff(){
+    echo "🚀"
+}
+trap blastoff DEBUG     # Trap DEBUG *before* running starship
+eval $(starship init bash)
+```
+
+## Change Window Title
+
+Some shell prompts will automatically change the window title for you (e.g. to reflect your working directory). Fish even does it by default. Starship does not do this, but it's fairly straightforward to add this functionality to `bash` or `zsh`.
+
+First, define a window title change function (identical in bash and zsh):
+
+```bash
+function set_win_title(){
+    echo -ne "\033]0; YOUR_WINDOW_TITLE_HERE \007"
+}
+```
+
+You can use variables to customize this title (`$USER`, `$HOSTNAME`, and `$PWD` are popular choices).
+
+In `bash`, set this function to be the precmd starship function:
+
+```bash
+starship_precmd_user_func="set_win_title"
+```
+
+In `zsh`, add this to the `precmd_functions` array:
+
+```bash
+precmd_functions+=(set_win_title)
+```
+
+If you like the result, add these lines to your shell configuration file (`~/.bashrc` or `~/.zshrc`) to make it permanent.
+
+For example, if you want to display your current directory in your terminal tab title, add the following snippet to your `~/.bashrc` or `~/.zshrc`:
+
+```bash
+function set_win_title(){
+    echo -ne "\033]0; $(basename $PWD) \007"
+}
+starship_precmd_user_func="set_win_title"
+```
+
+## Style Strings
+
+Style strings are a list of words, separated by whitespace. The words are not case sensitive (i.e. `bold` and `BoLd` are considered the same string). Each word can be one of the following:
+
+  - `bold`
+  - `underline`
+  - `dimmed`
+  - `bg:<color>`
+  - `fg:<color>`
+  - `<color>`
+  - `none`
+
+where `<color>` is a color specifier (discussed below). `fg:<color>` and `<color>` currently do the same thing , though this may change in the future. The order of words in the string does not matter.
+
+The `none` token overrides all other tokens in a string if it is not part of a `bg:` specifier, so that e.g. `fg:red none fg:blue` will still create a string with no styling. `bg:none`  sets the background to the default color so `fg:red bg:none` is equivalent to `red` or `fg:red` and `bg:green fg:red bg:none` is also equivalent to `fg:red` or `red`. It may become an error to use `none` in conjunction with other tokens in the future.
+
+A color specifier can be one of the following:
+
+ - One of the standard terminal colors: `black`, `red`, `green`, `blue`, `yellow`, `purple`, `cyan`, `white`. You can optionally prefix these with `bright-` to get the bright version (e.g. `bright-white`).
+ - A `#` followed by a six-digit hexadecimal number. This specifies an [RGB color hex code](https://www.w3schools.com/colors/colors_hexadecimal.asp).
+ - A number between 0-255. This specifies an [8-bit ANSI Color Code](https://i.stack.imgur.com/KTSQa.png).
+
+If multiple colors are specified for foreground/background, the last one in the string will take priority.

docs/pl-PL/faq/README.md

@@ -0,0 +1,96 @@
+# FAQ
+
+## What is the configuration used in the demo GIF?
+
+- **Terminal Emulator**: [iTerm2](https://iterm2.com/)
+  - **Theme**: Minimal
+  - **Color Scheme**: [Snazzy](https://github.com/sindresorhus/iterm2-snazzy)
+  - **Font**: [FiraCode Nerd Font](https://www.nerdfonts.com/font-downloads)
+- **Shell**: [Fish Shell](https://fishshell.com/)
+  - **Configuration**: [matchai's Dotfiles](https://github.com/matchai/dotfiles/blob/b6c6a701d0af8d145a8370288c00bb9f0648b5c2/.config/fish/config.fish)
+  - **Prompt**: [Starship](https://starship.rs/)
+
+## How do I get command completion as shown in the demo GIF?
+
+Completion support, or autocomplete, is provided by your shell of choice. In the case of the demo, the demo was done with [Fish Shell](https://fishshell.com/), which provides completions by default. If you use Z Shell (zsh), I'd suggest taking a look at [zsh-autosuggestions](https://github.com/zsh-users/zsh-autosuggestions).
+
+## 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. Why isn't my preferred shell supported?
+
+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:
+
+```sh
+# 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](https://github.com/starship/starship/blob/master/src/init/starship.bash) built into Starship is slightly more complex to allow for advanced features like the [Command Duration module](https://starship.rs/config/#command-duration) 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:
+
+```sh
+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`:
+
+```sh
+curl -fsSL https://starship.rs/install.sh | bash -s -- --platform unknown-linux-musl
+```
+
+## I see symbols I don't understand or expect, what do they mean?
+
+If you see symbols that you don't recognise you can use `starship explain` to explain the currently showing modules.
+
+## 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](https://www.tecmint.com/set-system-locales-in-linux/).
+- 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](https://www.google.com/get/noto/help/emoji/) is a popular choice.
+- You are using a [Nerd Font](https://www.nerdfonts.com/).
+
+To test your system, run the following commands in a terminal:
+
+```sh
+echo -e "\xf0\x9f\x90\x8d"
+echo -e "\xee\x82\xa0"
+```
+
+The first line should produce a [snake emoji](https://emojipedia.org/snake/), while the second should produce a [powerline branch symbol (e0a0)](https://github.com/ryanoasis/powerline-extra-symbols#glyphs).
+
+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!](https://github.com/starship/starship/issues/new/choose)
+
+## 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.
+1. 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:
+
+```sh
+# Locate and delete the starship binary
+rm "$(which starship)"
+```

docs/pl-PL/guide/README.md

@@ -0,0 +1,311 @@
+<p align="center">
+  <img
+    width="400"
+    src="https://raw.githubusercontent.com/starship/starship/master/media/logo.png"
+    alt="Starship – Cross-shell prompt"
+ />
+</p>
+
+<p align="center">
+  <a href="https://github.com/starship/starship/actions"
+    ><img
+      src="https://img.shields.io/github/workflow/status/starship/starship/Main workflow/master?label=workflow&style=flat-square"
+      alt="GitHub Actions workflow status"
+ /></a>
+  <a href="https://crates.io/crates/starship"
+    ><img
+      src="https://img.shields.io/crates/v/starship?style=flat-square"
+      alt="Crates.io version"
+ /></a>
+  <a href="https://repology.org/project/starship/versions"
+    ><img
+      src="https://img.shields.io/repology/repositories/starship?label=in%20repositories&style=flat-square"
+      alt="Packaging status" /></a
+><br />
+  <a href="https://discord.gg/starship"
+    ><img
+      src="https://img.shields.io/discord/567163873606500352?label=discord&logoColor=white&style=flat-square"
+      alt="Chat on Discord"
+ /></a>
+  <a href="https://twitter.com/StarshipPrompt"
+    ><img
+      src="https://img.shields.io/badge/twitter-@StarshipPrompt-1DA1F3?style=flat-square"
+      alt="Follow @StarshipPrompt on Twitter"
+ /></a>
+</p>
+
+<p align="center">
+  <a href="https://starship.rs">Website</a>
+  ·
+  <a href="#🚀-installation">Installation</a>
+  ·
+  <a href="https://starship.rs/config/">Configuration</a>
+</p>
+
+<p align="center">
+  <a href="https://github.com/starship/starship/blob/master/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-us.png"
+      alt="English"
+ /></a>
+  &nbsp;
+  <a
+    href="https://github.com/starship/starship/blob/master/docs/ja-JP/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-jp.png"
+      alt="日本語"
+ /></a>
+  &nbsp;
+  <a
+    href="https://github.com/starship/starship/blob/master/docs/zh-TW/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-tw.png"
+      alt="繁體中文"
+ /></a>
+  &nbsp;
+  <a
+    href="https://github.com/starship/starship/blob/master/docs/ru-RU/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-ru.png"
+      alt="Русский"
+ /></a>
+  &nbsp;
+  <a
+    href="https://github.com/starship/starship/blob/master/docs/de-DE/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-de.png"
+      alt="Deutsch"
+ /></a>
+  &nbsp;
+  <a
+    href="https://github.com/starship/starship/blob/master/docs/zh-CN/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-cn.png"
+      alt="简体中文"
+ /></a>
+  &nbsp;
+  <a 
+    href="https://github.com/starship/starship/blob/master/docs/es-ES/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-es.png"
+      alt="Español"
+ /></a>
+  &nbsp;
+  <a 
+    href="https://github.com/starship/starship/blob/master/docs/fr-FR/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-fr.png"
+      alt="Français"
+ /></a>
+  &nbsp;
+  <a 
+    href="https://github.com/starship/starship/blob/master/docs/vi-VN/guide/README.md"
+    ><img
+      height="20"
+      src="https://raw.githubusercontent.com/starship/starship/master/media/flag-vn.png"
+      alt="Tiếng Việt"
+ /></a>
+</p>
+
+<h1></h1>
+
+<img
+  src="https://raw.githubusercontent.com/starship/starship/master/media/demo.gif"
+  alt="Starship with iTerm2 and the Snazzy theme"
+  width="50%"
+  align="right"
+ />
+
+**The minimal, blazing-fast, and infinitely customizable prompt for any shell!**
+
+- **Fast:** it's fast – _really really_ fast! 🚀
+- **Customizable:** configure every aspect of your prompt.
+- **Universal:** works on any shell, on any operating system.
+- **Intelligent:** shows relevant information at a glance.
+- **Feature rich:** support for all your favorite tools.
+- **Easy:** quick to install – start using it in minutes.
+
+<p align="center">
+<a href="https://starship.rs/config/"><strong>Explore the Starship docs&nbsp;&nbsp;▶</strong></a>
+</p>
+
+<a name="🚀-installation"></a>
+
+## 🚀 Installation
+
+### Prerequisites
+
+- A [Nerd Font](https://www.nerdfonts.com/) installed and enabled in your terminal (for example, try the [Fira Code Nerd Font](https://www.nerdfonts.com/font-downloads)).
+
+### Getting Started
+
+**Note**: due to the proliferation of different platforms, only a subset of supported platforms are shown below. Can't see yours? Have a look at the [extra platform instructions](https://starship.rs/installing/).
+
+1. Install the **starship** binary:
+
+
+   #### Install Latest Version
+
+
+   ##### From prebuilt binary, with Shell:
+
+   ```sh
+   curl -fsSL https://starship.rs/install.sh | bash
+   ```
+
+
+   #### Install via Package Manager
+
+
+   ##### Example: [Homebrew](https://brew.sh/):
+
+   ```sh
+   brew install starship
+   ```
+
+
+   ##### With [Scoop](https://scoop.sh):
+
+   ```powershell
+   scoop install starship
+   ```
+
+2. Add the init script to your shell's config file:
+
+
+   #### Bash
+
+   Add the following to the end of `~/.bashrc`:
+
+   ```sh
+   # ~/.bashrc
+
+   eval "$(starship init bash)"
+   ```
+
+
+   #### Fish
+
+   Add the following to the end of `~/.config/fish/config.fish`:
+
+   ```sh
+   # ~/.config/fish/config.fish
+
+   starship init fish | source
+   ```
+
+
+   #### Zsh
+
+   Add the following to the end of `~/.zshrc`:
+
+   ```sh
+   # ~/.zshrc
+
+   eval "$(starship init zsh)"
+   ```
+
+
+   #### PowerShell
+
+   Add the following to the end of `Microsoft.PowerShell_profile.ps1`. You can check the location of this file by querying the `$PROFILE` variable in PowerShell. Typically the path is `~\Documents\PowerShell\Microsoft.PowerShell_profile.ps1` or `~/.config/powershell/Microsoft.PowerShell_profile.ps1` on -Nix.
+
+   ```powershell
+   Invoke-Expression (&starship init powershell)
+   ```
+
+
+   #### Ion
+
+   Add the following to the end of `~/.config/ion/initrc`:
+
+   ```sh
+   # ~/.config/ion/initrc
+
+   eval $(starship init ion)
+   ```
+
+
+   #### Elvish
+
+   **Warning** Only elvish v0.15 or higher is supported. Add the following to the end of `~/.elvish/rc.elv`:
+
+   ```sh
+   # ~/.elvish/rc.elv
+
+   eval (starship init elvish)
+   ```
+
+
+   #### Tcsh
+
+   Add the following to the end of `~/.tcshrc`:
+
+   ```sh
+   # ~/.tcshrc
+
+   eval `starship init tcsh`
+   ```
+
+## 🤝 Contributing
+
+We are always looking for contributors of **all skill levels**! If you're looking to ease your way into the project, try out a [good first issue](https://github.com/starship/starship/labels/🌱%20good%20first%20issue).
+
+If you are fluent in a non-English language, we greatly appreciate any help keeping our docs translated and up-to-date in other languages. If you would like to help, translations can be contributed on the [Starship Crowdin](https://translate.starship.rs/).
+
+If you are interested in helping contribute to starship, please take a look at our [Contributing Guide](https://github.com/starship/starship/blob/master/CONTRIBUTING.md). Also, feel free to drop into our [Discord server](https://discord.gg/8Jzqu3T) and say hi. 👋
+
+### Code Contributors
+
+This project exists thanks to all the people who contribute. [[Contribute](https://github.com/starship/starship/blob/master/CONTRIBUTING.md)].
+<a href="https://github.com/starship/starship/graphs/contributors"><img src="https://opencollective.com/starship/contributors.svg?width=890&button=false" /></a>
+
+### Financial Contributors
+
+Become a financial contributor and help us sustain our community. [[Contribute](https://opencollective.com/starship/contribute)]
+
+#### Individuals
+
+<a href="https://opencollective.com/starship"><img src="https://opencollective.com/starship/individuals.svg?width=890"></a>
+
+#### Organizations
+
+Support this project with your organization. Your logo will show up here with a link to your website. [[Contribute](https://opencollective.com/starship/contribute)]
+
+<a href="https://opencollective.com/starship/organization/0/website"><img src="https://opencollective.com/starship/organization/0/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/1/website"><img src="https://opencollective.com/starship/organization/1/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/2/website"><img src="https://opencollective.com/starship/organization/2/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/3/website"><img src="https://opencollective.com/starship/organization/3/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/4/website"><img src="https://opencollective.com/starship/organization/4/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/5/website"><img src="https://opencollective.com/starship/organization/5/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/6/website"><img src="https://opencollective.com/starship/organization/6/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/7/website"><img src="https://opencollective.com/starship/organization/7/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/8/website"><img src="https://opencollective.com/starship/organization/8/avatar.svg"></a>
+<a href="https://opencollective.com/starship/organization/9/website"><img src="https://opencollective.com/starship/organization/9/avatar.svg"></a>
+
+## 💭 Inspired By
+
+Please check out these previous works that helped inspire the creation of starship. 🙏
+
+- **[denysdovhan/spaceship-prompt](https://github.com/denysdovhan/spaceship-prompt)** - A ZSH prompt for astronauts.
+
+- **[denysdovhan/robbyrussell-node](https://github.com/denysdovhan/robbyrussell-node)** - Cross-shell robbyrussell theme written in JavaScript.
+
+- **[reujab/silver](https://github.com/reujab/silver)** - A cross-shell customizable powerline-like prompt with icons.
+
+<p align="center">
+    <br>
+    <img width="100" src="https://raw.githubusercontent.com/starship/starship/master/media/icon.png" alt="Starship rocket icon">
+</p>
+
+## 📝 License
+
+Copyright © 2019-present, [Starship Contributors](https://github.com/starship/starship/graphs/contributors).<br /> This project is [ISC](https://github.com/starship/starship/blob/master/LICENSE) licensed.

docs/pl-PL/installing/README.md

@@ -0,0 +1,84 @@
+# 🚀 Advanced Installation
+
+To install starship, you need to do two things:
+
+1. Get the **starship** binary onto your computer
+1. Tell your shell to use the starship binary as its prompt by modifying its init scripts
+
+For most users, the instructions on [the main page](/guide/#🚀-installation) will work great. However, for some more specialized platforms, different instructions are needed.
+
+There are so many platforms out there that they didn't fit into the main README.md file, so here are some installation instructions for other platforms from the community. Is yours not here? Please do add it here if you figure it out!
+
+## [Chocolatey](https://chocolatey.org)
+
+### Prerequisites
+
+Head over to the [Chocolatey installation page](https://chocolatey.org/install) and follow the instructions to install Chocolatey.
+
+### Installation
+
+```powershell
+choco install starship
+```
+
+## [termux](https://termux.com)
+
+### Prerequisites
+
+```sh
+pkg install getconf
+```
+
+### Installation
+
+```sh
+curl -fsSL https://starship.rs/install.sh | bash -s -- -b /data/data/com.termux/files/usr/bin
+```
+
+## [Nix](https://nixos.wiki/wiki/Nix)
+
+### Getting the Binary
+
+#### Imperatively
+
+```sh
+nix-env -iA nixos.starship
+```
+
+#### Declarative, single user, via [home-manager](home-manager)
+
+Enable the `programs.starship` module in your `home.nix` file, and add your settings
+
+```nix
+{
+  programs.starship = {
+    enable = true;
+    enableZshIntegration = true;
+    # Configuration written to ~/.config/starship.toml
+    settings = {
+      # add_newline = false;
+
+      # character = {
+      #   success_symbol = "[➜](bold green)";
+      #   error_symbol = "[➜](bold red)";
+      # };
+
+      # package.disabled = true;
+    };
+  };
+}
+```
+
+then run
+
+```sh
+home-manager switch
+```
+
+#### Declarative, system-wide, with NixOS
+
+Add `pkgs.starship` to `environment.systemPackages` in your `configuration.nix`, then run
+
+```sh
+sudo nixos-rebuild switch
+```

docs/pl-PL/migrating-to-0.45.0/README.md

@@ -0,0 +1,267 @@
+# Migrating to v0.45.0
+
+Starship v0.45.0 is a release containing breaking changes, in preparation for the big v1.0.0. We have made some major changes around how configuration is done on the prompt, to allow for a greater degree of customization.
+
+This guide is intended to walk you through the breaking changes.
+
+## `prompt_order` has been replaced by a root-level `format`
+
+Previously to v0.45.0, `prompt_order` would accept an array of module names in the order which they should be rendered by Starship.
+
+Starship v0.45.0 instead accepts a `format` value, allowing for customization of the prompt outside of the modules themselves.
+
+**Example pre-v0.45.0 configuration**
+
+```toml
+prompt_order = [
+  "username",
+  "hostname",
+  "directory",
+  "git_branch",
+  "git_commit",
+  "git_state",
+  "git_status",
+  "cmd_duration",
+  "custom",
+  "line_break",
+  "jobs",
+  "battery",
+  "time",
+  "character",
+]
+```
+
+**Example v0.45.0 configuration**
+
+```toml
+format = """\
+  $username\
+  $hostname\
+  $directory\
+  $git_branch\
+  $git_commit\
+  $git_state\
+  $git_status\
+  $cmd_duration\
+  $custom\
+  $line_break\
+  $jobs\
+  $battery\
+  $time\
+  $character\
+  """
+```
+
+## Module `prefix` and `suffix` have been replaced by `format`
+
+Previously to v0.45.0, some modules would accept `prefix` and/or `suffix` in order to stylize the way that modules are rendered.
+
+Starship v0.45.0 instead accepts a `format` value, allowing for further customization of how modules are rendered. Instead of defining a prefix and suffix for the context-based variables, the variables can now be substituted from within a format string, which represents the module's output.
+
+**Example pre-v0.45.0 configuration**
+
+```toml
+[cmd_duration]
+prefix = "took "
+```
+
+**Example v0.45.0 configuration**
+
+```toml
+[cmd_duration]
+# $duration – The command duration (e.g. "15s")
+# $style    – The default style of the module (e.g. "bold yellow")
+format = "took [$duration]($style) "
+```
+
+### Affected Modules
+
+#### Character
+
+| Removed Property        | Replacement      |
+| ----------------------- | ---------------- |
+| `symbol`                | `success_symbol` |
+| `use_symbol_for_status` | `error_symbol`   |
+| `style_success`         | `success_symbol` |
+| `style_failure`         | `error_symbol`   |
+
+**Changes to the Default Configuration**
+
+```diff
+[character]
+-- symbol = "❯"
+-- error_symbol = "✖"
+-- use_symbol_for_status = true
+-- vicmd_symbol = "❮"
+++ success_symbol = "[❯](bold green)"
+++ error_symbol = "[❯](bold red)"
+++ vicmd_symbol = "[❮](bold green)"
+```
+
+Previously, the `use_symbol_for_status` property was used to configure the prompt to show the `error_symbol` when the last command resulted in a non-zero status code.
+
+With the release of v0.45.0, we now always use `error_symbol` after non-zero status codes, unifying `use_symbol_for_status` and `error_symbol` properties.
+
+To configure the prompt to use the older `use_symbol_for_status = true` configuration, add the following to your config file:
+
+```toml
+[character]
+error_symbol = "[✖](bold red)"
+```
+
+*Note:* The `character` element automatically adds a space after, so unlike the other `format` strings, we specifically do not add one in the above examples.
+
+#### Command Duration
+
+| Removed Property | Replacement |
+| ---------------- | ----------- |
+| `prefix`         | `format`    |
+
+**Changes to the Default Configuration**
+
+```diff
+[cmd_duration]
+-- prefix = "took "
+++ format = "took [$duration]($style) "
+```
+
+#### Directory
+
+| Removed Property | Replacement |
+| ---------------- | ----------- |
+| `prefix`         | `format`    |
+
+**Changes to the Default Configuration**
+
+```diff
+[directory]
+-- prefix = "in "
+++ format = "[$path]($style)[$read_only]($read_only_style) "
+```
+
+#### Environment Variable
+
+| Removed Property | Replacement |
+| ---------------- | ----------- |
+| `prefix`         | `format`    |
+| `suffix`         | `format`    |
+
+**Changes to the Default Configuration**
+
+```diff
+[env_var]
+-- prefix = ""
+-- suffix = ""
+++ format = "with [$env_value]($style) "
+```
+
+#### Git Commit
+
+| Removed Property | Replacement |
+| ---------------- | ----------- |
+| `prefix`         | `format`    |
+| `suffix`         | `format`    |
+
+**Changes to the Default Configuration**
+
+```diff
+[git_commit]
+-- prefix = "("
+-- suffix = ")"
+++ format = '[\($hash\)]($style) '
+```
+
+#### Git Status
+
+| Removed Property  | Replacement |
+| ----------------- | ----------- |
+| `prefix`          | `format`    |
+| `suffix`          | `format`    |
+| `show_sync_count` | `format`    |
+
+**Changes to the Default Configuration**
+
+```diff
+[git_status]
+-- prefix = "["
+-- suffix = "]"
+-- show_sync_count = false
+++ format = '([\[$all_status$ahead_behind\]]($style) )'
+```
+
+Previously, the `show_sync_count` property was used to configure the prompt to show the number of commits the branch was ahead or behind the remote branch.
+
+With the release of v0.45.0, this has been replaced with three separate properties, `ahead`, `behind`, and `diverged`.
+
+To configure the prompt to use the older `show_sync_count = true` configuration, set the following to your config file:
+
+```toml
+[git_status]
+ahead = "⇡${count}"
+diverged = "⇕⇡${ahead_count}⇣${behind_count}"
+behind = "⇣${count}"
+```
+
+#### Hostname
+
+| Removed Property | Replacement |
+| ---------------- | ----------- |
+| `prefix`         | `format`    |
+| `suffix`         | `format`    |
+
+**Changes to the Default Configuration**
+
+```diff
+[hostname]
+-- prefix = ""
+-- suffix = ""
+++ format = "[$hostname]($style) in "
+```
+
+#### Singularity
+
+| Removed Property | Replacement |
+| ---------------- | ----------- |
+| `label`          | `format`    |
+| `prefix`         | `format`    |
+| `suffix`         | `format`    |
+
+**Changes to the Default Configuration**
+
+```diff
+[singularity]
+-- prefix = ""
+-- suffix = ""
+++ format = '[$symbol\[$env\]]($style) '
+```
+
+#### Time
+
+| Removed Property | Replacement   |
+| ---------------- | ------------- |
+| `format`         | `time_format` |
+
+**Changes to the Default Configuration**
+
+```diff
+[time]
+-- format = "🕙[ %T ]"
+++ time_format = "%T"
+++ format = "at 🕙[$time]($style) "
+```
+
+#### Custom Commands
+
+| Removed Property | Replacement |
+| ---------------- | ----------- |
+| `prefix`         | `format`    |
+| `suffix`         | `format`    |
+
+**Changes to the Default Configuration**
+
+```diff
+[custom.example]
+-- prefix = ""
+-- suffix = ""
+++ format = "[$symbol$output]($style) "
+```

docs/pl-PL/presets/README.md

@@ -0,0 +1,92 @@
+# Presets
+
+Here is a collection of community-submitted configuration presets for Starship. If you have a preset to share, please [submit a PR](https://github.com/starship/starship/edit/master/docs/presets/README.md) updating this file! 😊
+
+## Nerd Font Symbols
+
+This preset doesn't change anything except for the symbols used for each module. If emojis aren't your thing, this might catch your eye!
+
+![Screenshot of Nerd Font Symbols preset](/presets/nerd-font-symbols.png)
+
+### Prerequisites
+
+- A [Nerd Font](https://www.nerdfonts.com/) installed and enabled in your terminal (the example uses Fira Code Nerd Font)
+
+### Configuration
+
+```toml
+[aws]
+symbol = "  "
+
+[conda]
+symbol = " "
+
+[dart]
+symbol = " "
+
+[directory]
+read_only = " "
+
+[docker]
+symbol = " "
+
+[elixir]
+symbol = " "
+
+[elm]
+symbol = " "
+
+[git_branch]
+symbol = " "
+
+[golang]
+symbol = " "
+
+[haskell]
+symbol = " "
+
+[hg_branch]
+symbol = " "
+
+[java]
+symbol = " "
+
+[julia]
+symbol = " "
+
+[memory_usage]
+symbol = " "
+
+[nim]
+symbol = " "
+
+[nix_shell]
+symbol = " "
+
+[nodejs]
+symbol = " "
+
+[package]
+symbol = " "
+
+[perl]
+symbol = " "
+
+[php]
+symbol = " "
+
+[python]
+symbol = " "
+
+[ruby]
+symbol = " "
+
+[rust]
+symbol = " "
+
+[scala]
+symbol = " "
+
+[swift]
+symbol = "ﯣ "
+```

docs/presets/README.md

@@ -86,6 +86,9 @@ symbol = " "
 [rust]
 symbol = " "
 
+[scala]
+symbol = " "
+
 [swift]
 symbol = "ﯣ "
 ```

docs/pt-BR/README.md

@@ -110,3 +110,27 @@ description: O Starship é o prompt minimalista, extremamente rápido e extremam
 
    eval $(starship init ion)
    ```
+
+   #### Elvish
+
+   ::: warning Only elvish v0.15 or higher is supported. :::
+
+   Add the following to the end of `~/.elvish/rc.elv`:
+
+   ```sh
+   # ~/.elvish/rc.elv
+
+   eval (starship init elvish)
+   ```
+
+
+   #### Tcsh
+
+   Add the following to the end of `~/.tcshrc`:
+
+   ```sh
+   # ~/.tcshrc
+
+   eval `starship init tcsh`
+   ```
+

docs/pt-BR/advanced-config/README.md

@@ -82,7 +82,7 @@ Style strings are a list of words, separated by whitespace. The words are not ca
 
 where `<color>` is a color specifier (discussed below). `fg:<color>` and `<color>` currently do the same thing , though this may change in the future. The order of words in the string does not matter.
 
-The `none` token overrides all other tokens in a string, so that e.g. `fg:red none fg:blue` will still create a string with no styling. It may become an error to use `none` in conjunction with other tokens in the future.
+The `none` token overrides all other tokens in a string if it is not part of a `bg:` specifier, so that e.g. `fg:red none fg:blue` will still create a string with no styling. `bg:none`  sets the background to the default color so `fg:red bg:none` is equivalent to `red` or `fg:red` and `bg:green fg:red bg:none` is also equivalent to `fg:red` or `red`. It may become an error to use `none` in conjunction with other tokens in the future.
 
 A color specifier can be one of the following: