Support configuring separate symbols for main status and pipe status

[Nemo157]

Feature Request

Is your feature request related to a problem? Please describe.

When using pipestatus = true it's nice to have the status appear only when the overall pipe failed. After the change in #3750 you must have success_symbol set to blank to get this behaviour, but within the pipe status section there is no symbol to show the successful sub-processes.

(More discussion, and a simple test case in #3746 (comment))

Describe the solution you'd like

Allow configuring a separate success_pipe symbol that is used within the pipe status section, so the desired behaviour can be achieved using something like success_symbol = "", success_pipe = "✔"

Describe alternatives you've considered

[IzhakJakov]

@Nemo157
Thank you for opening this issue, I'll try fixing it as soon as I get some free time. I am working full time and nowadays studying for a certification as well.

[IzhakJakov]

format = """
($status )$character
"""

[character]
success_symbol = "$❯"
error_symbol = "[$❯](red)"
vicmd_symbol = "[$❯](yellow)"

[status]
disabled = false
symbol = "X"
success_symbol = "Y"
format = "[$symbol]($style)"
pipestatus_separator = " | "
pipestatus_format = "\\[ $pipestatus \\] = [$symbol]($style)"
map_symbol = true
pipestatus = true

Actual

$❯ Y > true | true

[ Y | Y ] = Y >

$❯ true | false

[ Y | X ] = X >

$❯ false | true

[ X | Y ] = Y >

Expected:

$❯ Y > true | true

[IzhakJakov]

@Nemo157 I might be blocked (hopefully just for a short time) by this issue:

❯ cargo run --features config-schema -- config-schema > .github/config-schema.json
    Updating crates.io index
error: failed to select a version for the requirement `libgit2-sys = "^0.13.3"`
candidate versions found which didn't match: 0.13.2+1.4.2, 0.13.1+1.4.2, 0.13.0+1.4.1, ...
location searched: crates.io index
required by package `git2 v0.14.3`
    ... which satisfies dependency `git2 = "^0.14.2"` (locked to 0.14.3) of package `starship v1.6.3 (/Volumes/CaseSensitive/repositories/tmpo/starship)`

I'll try to work around this if I can. Not today though.

[chipbuster]

@IzhakJakov Could you run cargo --version for me and post the output? When you have time, not necessarily immediately.

[IzhakJakov]

❯ cargo version
cargo 1.59.0

[DerRockWolf]

This would additionally, if success_symbol isn't set, also solve a problem where the pipestatus result is 0, if:
false | true will give this prompt: [❌1 |0 ] =>

In this case I would expect something like this [❌1 |0 ] => ✅