diff --git a/README.md b/README.md index 662a6cc3..7e302ab1 100644 --- a/README.md +++ b/README.md @@ -50,6 +50,7 @@ this theme focus on three primary goals: - [Special Segment Colors](#special-segment-colors) - [Troubleshooting](#troubleshooting) - [Gaps Between Segments](#gaps-between-segments) + - [Segment Colors are Wrong](#segment-colors-are-wrong) - [Meta](#meta) - [Kudos](#kudos) - [Developing](#developing) @@ -276,10 +277,17 @@ to a certain length: #### The 'time' segment By default the time is show in 'H:M:S' format. If you want to change it, -just set another format in your `~/.zshrc`: +just set another format in your `~/.zshrc`. As an example, this is a reversed +time format: # Reversed time format - POWERLEVEL9K_TIME_FORMAT='%D{%S:%M:%H}' + POWERLEVEL9K_TIME_FORMAT='%D{%S:%M:%H}' + +If you are using an "Awesome Powerline Font", you can add a time symbol to this +segment, as well: + + # Output time, date, and a symbol from the "Awesome Powerline Font" set + POWERLEVEL9K_TIME_FORMAT="%D{%H:%M:%S \uE868 %d.%m.%y}" #### Unit Test Ratios @@ -436,6 +444,15 @@ Thankfully, this is easy to fix. This happens if you have successfully installed Powerline fonts, but did not make a Powerline font the default font in your terminal emulator (e.g., 'terminator', 'gnome-terminal', 'konsole', etc.,). +#### Segment Colors are Wrong + +If the color display within your terminal seems off, it's possible you are using +a reduced color set. You can check this by invoking `echotc Co` in your +terminal, which should yield `256`. If you see something different, try setting +`xterm-256color` in your `~/.zshrc`: + + TERM=xterm-256color + ### Meta #### Kudos diff --git a/powerlevel9k.zsh-theme b/powerlevel9k.zsh-theme index 55fbb017..d7c2346a 100644 --- a/powerlevel9k.zsh-theme +++ b/powerlevel9k.zsh-theme @@ -26,7 +26,7 @@ # export DEFAULT_USER= # # Customize the format of the time segment. Example of reverse format: -# POWERLEVEL9K_TIME_FORMAT='%D{%S:%M:%H}' +# POWERLEVEL9K_TIME_FORMAT='%D{%S:%M:%H}' # # Show the hash/changeset string in the `vcs` segment: # POWERLEVEL9K_SHOW_CHANGESET=true @@ -232,8 +232,8 @@ zstyle ':vcs_info:*' enable git hg zstyle ':vcs_info:*' check-for-changes true VCS_DEFAULT_FORMAT="$VCS_CHANGESET_PREFIX%F{$VCS_FOREGROUND_COLOR}%b%c%u%m%f" -zstyle ':vcs_info:git:*' formats "%F{$VCS_FOREGROUND_COLOR}$VCS_GIT_ICON%f$VCS_DEFAULT_FORMAT" -zstyle ':vcs_info:hg:*' formats "%F{$VCS_FOREGROUND_COLOR}$VCS_HG_ICON%f$VCS_DEFAULT_FORMAT" +zstyle ':vcs_info:git:*' formats "%F{$VCS_FOREGROUND_COLOR}$VCS_GIT_ICON%f$VCS_DEFAULT_FORMAT" +zstyle ':vcs_info:hg:*' formats "%F{$VCS_FOREGROUND_COLOR}$VCS_HG_ICON%f$VCS_DEFAULT_FORMAT" zstyle ':vcs_info:*' actionformats " %b %F{red}| %a%f" @@ -268,7 +268,7 @@ fi # The latter three can be omitted, left_prompt_segment() { # Overwrite given background-color by user defined variable for this segment. - # We get as first Parameter the function name, which called this function. + # We get as first Parameter the function name, which called this function. # From the given function name, we strip the "prompt_"-prefix and uppercase it. # This is, prefixed with "POWERLEVEL9K_" and suffixed with either "_BACKGROUND" # of "_FOREGROUND", our variable name. So each new Segment should automatically @@ -442,7 +442,7 @@ CURRENT_BG='NONE' # AWS Profile prompt_aws() { local aws_profile="$AWS_DEFAULT_PROFILE" - if [[ -n "$aws_profile" ]]; + if [[ -n "$aws_profile" ]]; then $1_prompt_segment "$0" red white "$AWS_ICON $aws_profile" fi @@ -502,7 +502,7 @@ prompt_longstatus() { prompt_node_version() { local nvm_prompt=$(node -v 2>/dev/null) [[ -z "${nvm_prompt}" ]] && return - NODE_ICON=$'\u2B22' # ⬢ + NODE_ICON=$'\u2B22' # ⬢ $1_prompt_segment "$0" "green" "white" "${nvm_prompt:1} $NODE_ICON" } @@ -673,7 +673,6 @@ $POWERLEVEL9K_MULTILINE_SECOND_PROMPT_PREFIX" RPROMPT_SUFFIX='' fi RPROMPT=$RPROMPT_PREFIX"%{%f%b%k%}"'$(build_right_prompt)'"%{$reset_color%}"$RPROMPT_SUFFIX - } powerlevel9k_init "$@"