Skip to content

Commit

Permalink
docs(i18n): new Crowdin updates (starship#3460)
Browse files Browse the repository at this point in the history
  • Loading branch information
matchai authored and Perniciosius committed Feb 21, 2022
1 parent a790793 commit b34e1ec
Show file tree
Hide file tree
Showing 128 changed files with 7,870 additions and 5,505 deletions.
8 changes: 4 additions & 4 deletions docs/ar-SA/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -119,7 +119,7 @@ description: Starship is the minimal, blazing fast, and extremely customizable p

#### Elvish

::: warning Only elvish v0.17 or higher is supported. :::
::: 鬲丨匕賷乇 賷丿毓賲 賮賯胤 elvish v0.17 兀賵 兀毓賱賶. :::

兀囟賮 賲丕 賷賱賷 廿賱賶 賳賴丕賷丞 `~/.elvish/rc.elv`:

Expand Down Expand Up @@ -147,9 +147,9 @@ description: Starship is the minimal, blazing fast, and extremely customizable p

```toml
startup = [
"mkdir ~/.cache/starship",
"starship init nu | save ~/.cache/starship/init.nu",
"source ~/.cache/starship/init.nu"
"mkdir ~/.cache/starship",
"starship init nu | save ~/.cache/starship/init.nu",
"source ~/.cache/starship/init.nu",
]
prompt = "starship_prompt"
```
Expand Down
34 changes: 18 additions & 16 deletions docs/ar-SA/advanced-config/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -45,14 +45,16 @@ function blastoff(){
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.
- 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
set -o functrace
eval $(starship init bash)
set +o functrace
```

## Custom pre-prompt and pre-execution Commands in PowerShell
Expand Down Expand Up @@ -161,9 +163,9 @@ Note: `continuation_prompt` should be set to a literal string without any variab

Note: Continuation prompts are only available in the following shells:

- `bash`
- `zsh`
- `PowerShell`
- `bash`
- `zsh`
- `PowerShell`

### 賲孬丕賱

Expand All @@ -178,24 +180,24 @@ continuation_prompt = "鈻垛柖"

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`
- `italic`
- `underline`
- `dimmed`
- `inverted`
- `bg:<color>`
- `fg:<color>`
- `<color>`
- `none`
- `bold`
- `italic`
- `underline`
- `dimmed`
- `inverted`
- `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. `inverted` swaps the background and foreground colors. 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).
- 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.
Loading

0 comments on commit b34e1ec

Please sign in to comment.