github-mirror/fish-shell
2
0
Fork 0
mirror of https://github.com/fish-shell/fish-shell.git synced 2024-12-02 16:04:05 +08:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity
4a35248465
fish-shell/share/tools/web_config/sample_prompts/informative.fish

23 lines
1.0 KiB
Fish
Raw Normal View History

Allow setting the prompt from web_config
2012-09-06 16:30:26 +08:00
# name: Informative
# http://michal.karzynski.pl/blog/2009/11/19/my-informative-shell-prompt/
informative.fish: stop caching_set_color, use br* directly No longer uses global vars to cache set_color output, this was from before set_color was a builtin, it is pointless now. This is also a prompt from before we had bright named colors, and it appears it was relying on -o red to get bright red. so use brred, etc.
2019-04-09 16:13:10 +08:00
function fish_prompt --description 'Informative prompt'
Allow setting the prompt from web_config
2012-09-06 16:30:26 +08:00
#Save the return status of the previous command
add `$pipestatus` to informative.fish prompt
2019-02-28 14:37:56 +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
Add a function to check if the user is root. Add a helper function to check if the user is root. This function can be useful for the prompts for example. Modify the prompts made root checked to use the function instead. Add also the support of Administrator like a root user. Fixes: #7031
2020-06-17 23:55:23 +08:00
if fish_is_root_user
printf '%s@%s %s%s%s# ' $USER (prompt_hostname) (set -q fish_color_cwd_root
and set_color $fish_color_cwd_root
or set_color $fish_color_cwd) \
(prompt_pwd) (set_color normal)
else
set -l pipestatus_string (__fish_print_pipestatus $last_status "[" "] " "|" (set_color $fish_color_status) \
(set_color --bold $fish_color_status) $last_pipestatus)
Allow setting the prompt from web_config
2012-09-06 16:30:26 +08:00
Add a function to check if the user is root. Add a helper function to check if the user is root. This function can be useful for the prompts for example. Modify the prompts made root checked to use the function instead. Add also the support of Administrator like a root user. Fixes: #7031
2020-06-17 23:55:23 +08:00
printf '[%s] %s%s@%s %s%s %s%s%s \f\r> ' (date "+%H:%M:%S") (set_color brblue) \
$USER (prompt_hostname) (set_color $fish_color_cwd) $PWD $pipestatus_string \
(set_color normal)
lint: fish_indent all sample prompts
2016-11-02 10:19:45 +08:00
end
Add support for toor account. Currently fish doesn't recognize toor as special. However, it's likely that on BSD systems, fish shell will be used on toor, not on root (toor is an intentionally existing account to use more advanced shell on, like shell).
2014-07-30 17:55:47 +08:00
end
Reference in New Issue Copy Permalink