fish-shell/share/tools/web_config/sample_prompts/classic_status.fish

# name: Classic + Status
# author: David Frascone

function fish_prompt --description "Write out the prompt"
    # Save our status
    set -l last_pipestatus $pipestatus
    set -l last_status $status

    set -l color_cwd
    set -l suffix
    switch "$USER"
        case root toor
            if set -q fish_color_cwd_root
                set color_cwd $fish_color_cwd_root
            else
                set color_cwd $fish_color_cwd
            end
            set suffix '#'
        case '*'
            set color_cwd $fish_color_cwd
            set suffix '>'
    end

    echo -n -s "$USER" @ (prompt_hostname) ' ' (set_color $color_cwd) (prompt_pwd) \
        (__fish_print_pipestatus $last_status " [" "]" "|" (set_color $fish_color_status) (set_color --bold $fish_color_status) $last_pipestatus) \
        (set_color normal) "$suffix "
end
Allow setting the prompt from web_config 2012-09-06 16:30:26 +08:00			`# name: Classic + Status`
			`# author: David Frascone`

# This is a combination of 2 commits. # The first commit's message is: Simplify default fish_prompt No need for the set_color caching now that it's a builtin. Also simplify the 3 classic prompts in fish_config's sample_prompts set. 2014-10-03 05:02:53 +08:00			`function fish_prompt --description "Write out the prompt"`
Allow setting the prompt from web_config 2012-09-06 16:30:26 +08:00			`# Save our status`
update classic_status.fish prompt to include $pipestatus 2019-02-27 02:06:36 +08:00			`set -l last_pipestatus $pipestatus`
prompts: fix pipestatus for jobs prefixed with "not" 6902459566b491e2debb136f43f815965910eeee was an attempt to not print $status twice in the prompt. As a result we print $pipestatus but not $status, which /usually/ is the same as $pipestatus[-1] --- unless the builtin "not" is used, which inverts the $status of a job (it does not alter $pipestatus). As a result, the default prompt prints unexpected status codes: ~ > not false ~ [1]> not true ~ > not true \| true ~ > not false \| false ~ [1\|1]> This commit reintroduces printing of $status after $pipestatus, but only if it is different from $pipestatus[-1]. Additionally, we only print anything at all if the $status is nonzero, to avoid confusing output on `not false \| false` ~ > not false ~ > not true ~ [0] 1> not true \| true ~ [0\|0] 1> not false \| false ~ > I think this is closer to users' expectations for those cases; they should not have to think about this implementation detail of the not-statement. 2020-02-03 15:53:41 +08:00			`set -l last_status $status`
Allow setting the prompt from web_config 2012-09-06 16:30:26 +08:00
# This is a combination of 2 commits. # The first commit's message is: Simplify default fish_prompt No need for the set_color caching now that it's a builtin. Also simplify the 3 classic prompts in fish_config's sample_prompts set. 2014-10-03 05:02:53 +08:00			`set -l color_cwd`
			`set -l suffix`
Quote $USER when used with `switch` or `test` Common in prompts, this would fail if $USER is empty. See #4229. 2017-07-21 01:45:32 +08:00			`switch "$USER"`
lint: fish_indent all sample prompts 2016-11-02 10:19:45 +08:00			`case root toor`
			`if set -q fish_color_cwd_root`
			`set color_cwd $fish_color_cwd_root`
			`else`
			`set color_cwd $fish_color_cwd`
			`end`
			`set suffix '#'`
			`case '*'`
# This is a combination of 2 commits. # The first commit's message is: Simplify default fish_prompt No need for the set_color caching now that it's a builtin. Also simplify the 3 classic prompts in fish_config's sample_prompts set. 2014-10-03 05:02:53 +08:00			`set color_cwd $fish_color_cwd`
lint: fish_indent all sample prompts 2016-11-02 10:19:45 +08:00			`set suffix '>'`
Allow setting the prompt from web_config 2012-09-06 16:30:26 +08:00			`end`

prompt: move status to the right in classic_status sample prompt This is consistent with the other prompts that include status. [ci skip] 2019-12-11 08:06:31 +08:00			`echo -n -s "$USER" @ (prompt_hostname) ' ' (set_color $color_cwd) (prompt_pwd) \`
prompts: fix pipestatus for jobs prefixed with "not" 6902459566b491e2debb136f43f815965910eeee was an attempt to not print $status twice in the prompt. As a result we print $pipestatus but not $status, which /usually/ is the same as $pipestatus[-1] --- unless the builtin "not" is used, which inverts the $status of a job (it does not alter $pipestatus). As a result, the default prompt prints unexpected status codes: ~ > not false ~ [1]> not true ~ > not true \| true ~ > not false \| false ~ [1\|1]> This commit reintroduces printing of $status after $pipestatus, but only if it is different from $pipestatus[-1]. Additionally, we only print anything at all if the $status is nonzero, to avoid confusing output on `not false \| false` ~ > not false ~ > not true ~ [0] 1> not true \| true ~ [0\|0] 1> not false \| false ~ > I think this is closer to users' expectations for those cases; they should not have to think about this implementation detail of the not-statement. 2020-02-03 15:53:41 +08:00			`(__fish_print_pipestatus $last_status " [" "]" "\|" (set_color $fish_color_status) (set_color --bold $fish_color_status) $last_pipestatus) \`
Run fish_indent on all our fish scripts It's now good enough to do so. We don't allow grid-alignment: ```fish complete -c foo -s b -l barnanana -a '(something)' complete -c foo -s z -a '(something)' ``` becomes ```fish complete -c foo -s b -l barnanana -a '(something)' complete -c foo -s z -a '(something)' ``` It's just more trouble than it is worth. The one part I'd change: We align and/or'd parts of an if-condition with the in-block code: ```fish if true and false dosomething end ``` becomes ```fish if true and false dosomething end ``` but it's not used terribly much and if we ever fix it we can just reindent. 2020-01-14 03:34:22 +08:00			`(set_color normal) "$suffix "`
Allow setting the prompt from web_config 2012-09-06 16:30:26 +08:00			`end`