GithubHelp home page GithubHelp logo

powerlevel9k / powerlevel9k Goto Github PK

View Code? Open in Web Editor NEW
13.4K 217.0 951.0 4.41 MB

Powerlevel9k was a tool for building a beautiful and highly functional CLI, customized for you. P9k had a substantial impact on CLI UX, and its legacy is now continued by P10k.

Home Page: https://github.com/romkatv/powerlevel10k

License: MIT License

Ruby 2.00% Shell 96.27% Dockerfile 1.73%
zsh powerline-fonts terminal terminal-themes tools eye-candy

powerlevel9k's Introduction

Powerlevel9k is deprecated and now unmaintained. Please use Powerlevel10k!


Build Status Join the chat at https://gitter.im/bhilburn/powerlevel9k

Powerlevel9k is a theme for ZSH which uses Powerline Fonts. It can be used with vanilla ZSH or ZSH frameworks such as Oh-My-Zsh, Prezto, Antigen, and many others.

Get more out of your terminal. Be a badass. Impress everyone in 'Screenshot Your Desktop' threads. Use powerlevel9k.

You can check out some other users' configurations in our wiki: Show Off Your Config.

There are a number of Powerline ZSH themes available, now. The developers of this theme focus on four primary goals:

  1. Give users a great out-of-the-box configuration with no additional configuration required.
  2. Make customization easy for users who do want to tweak their prompt.
  3. Provide useful segments that you can enable to make your prompt even more effective and helpful. We have prompt segments for everything from unit test coverage to your AWS instance.
  4. Optimize the code for execution speed as much as possible. A snappy terminal is a happy terminal.

Powerlevel9k can be used to create both very useful and beautiful terminal environments:

Table of Contents

  1. Installation
  2. Customization
    1. Stylizing Your Prompt
    2. Customizing Prompt Segments
    3. Available Prompt Segments
  3. Troubleshooting

Be sure to also check out the Wiki!

Installation

There are two installation steps to go from a vanilla terminal to a PL9k terminal. Once you are done, you can optionally customize your prompt.

Installation Instructions

  1. Install the Powerlevel9k Theme
  2. Install Powerline Fonts

No configuration is necessary post-installation if you like the default settings, but there are plenty of segment customization options available if you are interested.

Prompt Customization

Be sure to check out the wiki page on the additional prompt customization options, including color and icon settings: Stylizing Your Prompt

Customizing Prompt Segments

Customizing your prompt is easy! Select the segments you want to have displayed, and then assign them to either the left or right prompt by adding the following variables to your ~/.zshrc.

Variable Default Value Description
POWERLEVEL9K_LEFT_PROMPT_ELEMENTS (context dir vcs) Segment list for left prompt
POWERLEVEL9K_RIGHT_PROMPT_ELEMENTS (status root_indicator background_jobs history time) Segment list for right prompt

The table above shows the default values, so if you wanted to set these variables manually, you would put the following in your ~/.zshrc:

POWERLEVEL9K_LEFT_PROMPT_ELEMENTS=(context dir vcs)
POWERLEVEL9K_RIGHT_PROMPT_ELEMENTS=(status root_indicator background_jobs history time)

Available Prompt Segments

The segments that are currently available are:

System Status Segments:

  • background_jobs - Indicator for background jobs.
  • battery - Current battery status.
  • context - Your username and host, conditionalized based on $USER and SSH status.
  • date - System date.
  • dir - Your current working directory.
  • dir_writable - Displays a lock icon, if you do not have write permissions on the current folder.
  • disk_usage - Disk usage of your current partition.
  • history - The command number for the current line.
  • host - Your current host name
  • ip - Shows the current IP address.
  • vpn_ip - Shows the current VPN IP address.
  • public_ip - Shows your public IP address.
  • load - Your machine's load averages.
  • os_icon - Display a nice little icon, depending on your operating system.
  • ram - Show free RAM.
  • root_indicator - An indicator if the user has superuser status.
  • status - The return code of the previous command.
  • swap - Prints the current swap size.
  • time - System time.
  • user - Your current username
  • vi_mode- Your prompt's Vi editing mode (NORMAL|INSERT).
  • ssh - Indicates whether or not you are in an SSH session.

Development Environment Segments:

  • vcs - Information about this git or hg repository (if you are in one).

Language Segments:

  • GoLang Segments:
    • go_version - Show the current GO version.
  • Javascript / Node.js Segments:
    • node_version - Show the version number of the installed Node.js.
    • nodeenv - nodeenv prompt for displaying node version and environment name.
    • nvm - Show the version of Node that is currently active, if it differs from the version used by NVM
  • PHP Segments:
    • php_version - Show the current PHP version.
    • laravel_version - Show the current Laravel version.
    • symfony2_tests - Show a ratio of test classes vs code classes for Symfony2.
    • symfony2_version - Show the current Symfony2 version, if you are in a Symfony2-Project dir.
  • Python Segments:
    • virtualenv - Your Python VirtualEnv.
    • anaconda - Your active Anaconda environment.
    • pyenv - Your active python version as reported by the first word of pyenv version. Note that the segment is not displayed if that word is system i.e. the segment is inactive if you are using system python.
  • Ruby Segments:
    • chruby - Ruby environment information using chruby (if one is active).
    • rbenv - Ruby environment information using rbenv (if one is active).
    • rspec_stats - Show a ratio of test classes vs code classes for RSpec.
    • rvm - Ruby environment information using $GEM_HOME and $MY_RUBY_HOME (if one is active).
  • Rust Segments:
    • rust_version - Display the current rust version and logo.
  • Swift Segments:
    • swift_version - Show the version number of the installed Swift.
  • Java Segments:
    • java_version - Show the current Java version.

Cloud Segments:

  • AWS Segments:
    • aws - The current AWS profile, if active.
    • aws_eb_env - The current Elastic Beanstalk Environment.
  • docker_machine - The current Docker Machine.
  • kubecontext - The current context of your kubectl configuration.
  • dropbox - Indicates Dropbox directory and syncing status using dropbox-cli

Other:

  • custom_command - Create a custom segment to display the output of an arbitrary command.
  • command_execution_time - Display the time the current command took to execute.
  • todo - Shows the number of tasks in your todo.txt tasks file.
  • detect_virt - Virtualization detection with systemd
  • newline - Continues the prompt on a new line.
  • openfoam - Shows the currently sourced OpenFOAM environment.

anaconda

This segment shows your active anaconda environment. It relies on either the CONDA_ENV_PATH or the CONDA_PREFIX (depending on the conda version) environment variable to be set which happens when you properly source activate an environment.

Special configuration variables:

Variable Default Value Description
POWERLEVEL9K_ANACONDA_LEFT_DELIMITER "(" The left delimiter just before the environment name.
POWERLEVEL9K_ANACONDA_RIGHT_DELIMITER ")" The right delimiter just after the environment name.

Additionally the following segment specific parameters can be used to customize it: POWERLEVEL9K_PYTHON_ICON, POWERLEVEL9K_ANACONDA_BACKGROUND, and POWERLEVEL9K_ANACONDA_FOREGROUND.

aws

If you would like to display the current AWS profile, add the aws segment to one of the prompts, and define AWS_DEFAULT_PROFILE in your ~/.zshrc:

Variable Default Value Description
AWS_DEFAULT_PROFILE None Your AWS profile name
background_jobs
Variable Default Value Description
POWERLEVEL9K_BACKGROUND_JOBS_VERBOSE true If there is more than one background job, this segment will show the number of jobs. Set this to false to turn this feature off.
POWERLEVEL9K_BACKGROUND_JOBS_VERBOSE_ALWAYS false Always show the jobs count (even if it's zero).
battery

The default settings for this segment will display your current battery status (fails gracefully on systems without a battery). It is supported on both OSX and Linux (note that it requires acpi on Linux).

Variable Default Value Description
POWERLEVEL9K_BATTERY_CHARGING "yellow" Color to indicate a charging battery.
POWERLEVEL9K_BATTERY_CHARGED "green" Color to indicate a charged battery.
POWERLEVEL9K_BATTERY_DISCONNECTED $DEFAULT_COLOR Color to indicate absence of battery.
POWERLEVEL9K_BATTERY_LOW_THRESHOLD 10 Threshold to consider battery level critical.
POWERLEVEL9K_BATTERY_LOW_COLOR "red" Color to indicate critically low charge level.
POWERLEVEL9K_BATTERY_VERBOSE true Display time remaining next to battery level.
POWERLEVEL9K_BATTERY_HIDE_ABOVE_THRESHOLD unset Threshold from which the battery segment should not be displayed.

Note that you can modify the _FOREGROUND color without affecting the icon color.

You can also change the battery icon automatically depending on the battery level. This will override the default battery icon. In order to do this, you need to define the POWERLEVEL9k_BATTERY_STAGES variable.

Variable Default Value Description
POWERLEVEL9K_BATTERY_STAGES Unset A string or array, which each index indicates a charge level.

Powerlevel9k will use each index of the string or array as a stage to indicate battery charge level, progressing from left to right. You can provide any number of stages. The setting below, for example, provides 8 stages for Powerlevel9k to use.

POWERLEVEL9K_BATTERY_STAGES="▁▂▃▄▅▆▇█"

If you require extra spacing after the icon, you will have to set it as an array, since spaces in the string will be used as one of the stages and you will get a missing icon. To do this, declare the variable as follows:

POWERLEVEL9K_BATTERY_STAGES=($'\u2581 ' $'\u2582 ' $'\u2583 ' $'\u2584 ' $'\u2585 ' $'\u2586 ' $'\u2587 ' $'\u2588 ')

Using the array syntax, you can create stages comprised of multiple characters. The below setting provides 40 battery stages.

POWERLEVEL9K_BATTERY_STAGES=(
   $'▏    ▏' $'▎    ▏' $'▍    ▏' $'▌    ▏' $'▋    ▏' $'▊    ▏' $'▉    ▏' $'█    ▏'
   $'█▏   ▏' $'█▎   ▏' $'█▍   ▏' $'█▌   ▏' $'█▋   ▏' $'█▊   ▏' $'█▉   ▏' $'██   ▏'
   $'██   ▏' $'██▎  ▏' $'██▍  ▏' $'██▌  ▏' $'██▋  ▏' $'██▊  ▏' $'██▉  ▏' $'███  ▏'
   $'███  ▏' $'███▎ ▏' $'███▍ ▏' $'███▌ ▏' $'███▋ ▏' $'███▊ ▏' $'███▉ ▏' $'████ ▏'
   $'████ ▏' $'████▎▏' $'████▍▏' $'████▌▏' $'████▋▏' $'████▊▏' $'████▉▏' $'█████▏' )

You can also change the background of the segment automatically depending on the battery level. This will override the following variables: POWERLEVEL9K_BATTERY_CHARGING, POWERLEVEL9K_BATTERY_CHARGED, POWERLEVEL9K_BATTERY_DISCONNECTED, and POWERLEVEL9K_BATTERY_LOW_COLOR. In order to do this, define a color array, from low to high, as shown below:

POWERLEVEL9K_BATTERY_LEVEL_BACKGROUND=(red1 orangered1 darkorange orange1 gold1 yellow1 yellow2 greenyellow chartreuse1 chartreuse2 green1)

As with the battery stages, you can use any number of colors and Powerlevel9k will automatically use all of them appropriately.

Some example settings:

Brightness Possible Array
Bright Colors (red1 orangered1 darkorange orange1 gold1 yellow1 yellow2 greenyellow chartreuse1 chartreuse2 green1)
Normal Colors (red3 darkorange3 darkgoldenrod gold3 yellow3 chartreuse2 mediumspringgreen green3 green3 green4 darkgreen)
Subdued Colors (darkred orange4 yellow4 yellow4 chartreuse3 green3 green4 darkgreen)
chruby

This segment shows the version of Ruby being used when using chruby to change your current Ruby stack.

It uses $RUBY_ENGINE and $RUBY_VERSION as set by chruby.

Variable Default Value Description
POWERLEVEL9K_CHRUBY_SHOW_ENGINE true Show the currently selected Ruby engine (e.g. ruby, jruby, rbx, etc)
POWERLEVEL9K_CHRUBY_SHOW_VERSION true Shows the currently selected engine's version (e.g. 2.5.1)
command_execution_time

Display the time the previous command took to execute if the time is above POWERLEVEL9K_COMMAND_EXECUTION_TIME_THRESHOLD. The time is formatted to be "human readable", and so scales the units based on the length of execution time. If you want more precision, just set the POWERLEVEL9K_COMMAND_EXECUTION_TIME_PRECISION field.

Variable Default Value Description
POWERLEVEL9K_COMMAND_EXECUTION_TIME_THRESHOLD 3 Threshold above which to print this segment. Can be set to 0 to always print.
POWERLEVEL9K_COMMAND_EXECUTION_TIME_PRECISION 2 Number of digits to use in the fractional part of the time value.
custom_command

The custom_... segment allows you to turn the output of a custom command into a prompt segment. As an example, if you wanted to create a custom segment to display your WiFi signal strength, you might define a custom segment called custom_wifi_signal like this:

POWERLEVEL9K_LEFT_PROMPT_ELEMENTS=(context time battery dir vcs virtualenv custom_wifi_signal)
POWERLEVEL9K_CUSTOM_WIFI_SIGNAL="echo signal: \$(nmcli device wifi | grep yes | awk '{print \$8}')"
POWERLEVEL9K_CUSTOM_WIFI_SIGNAL_BACKGROUND="blue"
POWERLEVEL9K_CUSTOM_WIFI_SIGNAL_FOREGROUND="yellow"

If you prefer, you can also define the function in your .zshrc rather than putting it in-line with the variable export, as shown above. Just don't forget to invoke your function from your segment! Example code that achieves the same result as the above:

zsh_wifi_signal(){
    local signal=$(nmcli device wifi | grep yes | awk '{print $8}')
    local color='%F{yellow}'
    [[ $signal -gt 75 ]] && color='%F{green}'
    [[ $signal -lt 50 ]] && color='%F{red}'
    echo -n "%{$color%}\uf230  $signal%{%f%}" # \uf230 is 
}

POWERLEVEL9K_CUSTOM_WIFI_SIGNAL="zsh_wifi_signal"
POWERLEVEL9K_LEFT_PROMPT_ELEMENTS=(context time battery dir vcs virtualenv custom_wifi_signal)

The command, above, gives you the wireless signal segment shown below:

signal

You can define as many custom segments as you wish. If you think you have a segment that others would find useful, please consider upstreaming it to the main theme distribution so that everyone can use it!

context

The context segment (user@host string) is conditional. By default, it will only print if you are not your 'normal' user (including if you are root), or if you are SSH'd to a remote host. SUDO and REMOTE_SUDO states are also available to show whether the current user or remote user has superuser privileges.

To use this feature, make sure the context segment is enabled in your prompt elements (it is by default), and define a DEFAULT_USER in your ~/.zshrc.

You can customize the context segment. For example, you can make it to print the full hostname by setting

POWERLEVEL9K_CONTEXT_TEMPLATE="%n@`hostname -f`"

You can set the POWERLEVEL9K_CONTEXT_HOST_DEPTH variable to change how the hostname is displayed. See ZSH Manual for details. The default is set to %m which will show the hostname up to the first ‘.’ You can set it to %{N}m where N is an integer to show that many segments of system hostname. Setting N to a negative integer will show that many segments from the end of the hostname.

Variable Default Value Description
DEFAULT_USER None Username to consider a "default context" (you can also set $USER).
POWERLEVEL9K_ALWAYS_SHOW_CONTEXT false Always show this segment, including $USER and hostname.
POWERLEVEL9K_ALWAYS_SHOW_USER false Always show the username, but conditionalize the hostname.
POWERLEVEL9K_CONTEXT_TEMPLATE %n@%m Default context prompt (username@machine). Refer to the ZSH Documentation for all possible expansions, including deeper host depths.

This segment can have different states. They might help you to visualize your different privileges. Read more about styling with states here.

State Meaning
DEFAULT You are a normal user
ROOT You are the root user
SUDO You are using elevated rights
REMOTE_SUDO You are SSH'ed into the machine and have elevated rights
REMOTE You are SSH'ed into the machine
date

The date segment shows the current system date.

Variable Default Value Description
POWERLEVEL9K_DATE_FORMAT %D{%d.%m.%y} ZSH time format to use in this segment.
dir

The dir segment shows the current working directory. When using the "Awesome Powerline" fonts, there are additional glyphs, as well:

Compatible Powerline Awesome Powerline Situation
None None At the root of your home folder
None None Within a subfolder of your home directory
None None Outside of your home folder
None None Within the /etc directory

To turn off these icons you could set these variables to an empty string.

POWERLEVEL9K_HOME_ICON=''
POWERLEVEL9K_HOME_SUB_ICON=''
POWERLEVEL9K_FOLDER_ICON=''
POWERLEVEL9K_ETC_ICON=''

You can limit the output to a certain length by truncating long paths. Customizations available are:

Variable Default Value Description
POWERLEVEL9K_DIR_PATH_ABSOLUTE None If set to true, will use absolute paths instead of home folder abbreviation ~
POWERLEVEL9K_SHORTEN_DIR_LENGTH 2 If your shorten strategy, below, is entire directories, this field determines how many directories to leave at the end. If your shorten strategy is by character count, this field determines how many characters to allow per directory string.
POWERLEVEL9K_SHORTEN_STRATEGY None How the directory strings should be truncated. See the table below for more informations.
POWERLEVEL9K_SHORTEN_DELIMITER .. Delimiter to use in truncated strings. This can be any string you choose, including an empty string if you wish to have no delimiter.
Strategy Name Description
Default Truncate whole directories from left. How many is defined by POWERLEVEL9K_SHORTEN_DIR_LENGTH
truncate_absolute_chars Truncates an absolute number of characters from the left such that the number of characters that your path displays (with or without POWERLEVEL9K_SHORTEN_DELIMITER) is no more than POWERLEVEL9K_SHORTEN_DIR_LENGTH + the length of POWERLEVEL9K_SHORTEN_DELIMITER
truncate_middle Truncates the middle part of a folder. E.g. you are in a folder named ~/MySuperProjects/AwesomeFiles/BoringOffice, then it will truncated to ~/MyS..cts/Awe..les/BoringOffice, if POWERLEVEL9K_SHORTEN_DIR_LENGTH=3 is also set (controls the amount of characters to be left).
truncate_from_right Just leaves the beginning of a folder name untouched. E.g. your folders will be truncated like so: /ro../Pr../office. How many characters will be untouched is controlled by POWERLEVEL9K_SHORTEN_DIR_LENGTH.
truncate_absolute Truncates everything exept the last few characters in the path. E.g. if you are in a folder named ~/Projects/powerlevel9k and you have set POWERLEVEL9K_SHORTEN_DIR_LENGTH=3, you will get ..l9k.
truncate_to_last Truncates everything before the last folder in the path.
truncate_to_first_and_last Truncate middle directories from the path. How many directories will be untouched is controlled by POWERLEVEL9K_SHORTEN_DIR_LENGTH. E.g. if you are in a folder named ~/Projects/powerlevel9k and you have set POWERLEVEL9K_SHORTEN_DIR_LENGTH=1, you will get ~/../powerlevel9k.
truncate_to_unique Parse all parent path components and truncate them to the shortest unique length. If you copy & paste the result to a shell, after hitting TAB it should expand to the original path unambiguously.
truncate_with_package_name Search for a package.json or composer.json and prints the name field to abbreviate the directory path. The precedence and/or files could be set by POWERLEVEL9K_DIR_PACKAGE_FILES=(package.json composer.json). If you have jq installed, it will dramatically improve the speed of this strategy.
truncate_with_folder_marker Search for a file that is specified by POWERLEVEL9K_SHORTEN_FOLDER_MARKER and truncate everything before that (if found, otherwise stop on $HOME and ROOT).

For example, if you wanted the truncation behavior of the fish shell, which truncates /usr/share/plasma to /u/s/plasma, you would use the following:

POWERLEVEL9K_SHORTEN_DIR_LENGTH=1
POWERLEVEL9K_SHORTEN_DELIMITER=""
POWERLEVEL9K_SHORTEN_STRATEGY="truncate_from_right"

In each case you have to specify the length you want to shorten the directory to. So in some cases POWERLEVEL9K_SHORTEN_DIR_LENGTH means characters, in others whole directories.

The truncate_with_package_name strategy gives your directory path relative to the root of your project. For example, if you have a project inside $HOME/projects/my-project with a package.json that looks like:

{
  "name": "my-cool-project"
}

The path shown would be my-cool-project. If you navigate to $HOME/projects/my-project/src, then the path shown would be my-cool-project/src. Please note that this currently looks for .git directory to determine the root of the project.

If you want to customize the directory separator, you could set:

# Double quotes are important here!
POWERLEVEL9K_DIR_PATH_SEPARATOR="%F{red} $(print_icon 'LEFT_SUBSEGMENT_SEPARATOR') %F{black}"

To omit the first character (usually a slash that gets replaced if you set POWERLEVEL9K_DIR_PATH_SEPARATOR), you could set POWERLEVEL9K_DIR_OMIT_FIRST_CHARACTER=true.

You can also customize the leading tilde character when you are in $HOME using:

# Double quotes are important here!
POWERLEVEL9K_HOME_FOLDER_ABBREVIATION="%F{red} $(print_icon 'HOME_ICON') %F{black}"

You can also configure the dir segment to show when you are in a directory without write permissions, using the variable below.

Variable Default Value Description
POWERLEVEL9K_DIR_SHOW_WRITABLE false If set to true and you are in a directory that you do not have write permissions for, this segment will display a lock icon and enter the NOT_WRITABLE state (which can be customized per our usual process). Note that this functionality is also available in a separate segment, dir_writable.

If you want to customize the last directory of the path, you can now set POWERLEVEL9K_DIR_PATH_HIGHLIGHT_FOREGROUND to a custom color and/or POWERLEVEL9K_DIR_PATH_HIGHLIGHT_BOLD=true to display that part in bold.

You can also color the separator separately by setting the color using POWERLEVEL9K_DIR_PATH_SEPARATOR_FOREGROUND.

disk_usage

The disk_usage segment will show the usage level of the partition that your current working directory resides in. It can be configured with the following variables.

Variable Default Value Description
POWERLEVEL9K_DISK_USAGE_ONLY_WARNING false Hide the segment except when usage levels have hit warning or critical levels.
POWERLEVEL9K_DISK_USAGE_WARNING_LEVEL 90 The usage level that triggers a warning state.
POWERLEVEL9K_DISK_USAGE_CRITICAL_LEVEL 95 The usage level that triggers a critical state.
host

The host segment will print the hostname.

You can set the POWERLEVEL9K_HOST_TEMPLATE variable to change how the hostname is displayed. See (ZSH Manual)[http://zsh.sourceforge.net/Doc/Release/Prompt-Expansion.html#Login-information] for details. The default is set to %m which will show the hostname up to the first .. You can set it to %{N}m where N is an integer to show that many segments of system hostname. Setting N to a negative integer will show that many segments from the end of the hostname.

POWERLEVEL9K_HOST_TEMPLATE="%2m"

By default, LOCAL hosts will show the host icon and remote hosts will show the SSH icon. You can override them by setting

POWERLEVEL9K_HOST_ICON="\uF109 "
POWERLEVEL9K_SSH_ICON="\uF489 "
ip

This segment tries to examine all currently used network interfaces and prints the first address it finds. In the case that this is not the right NIC, you can specify the correct network interface by setting:

Variable Default Value Description
POWERLEVEL9K_IP_INTERFACE None The NIC for which you wish to display the IP address. Example: eth0.
vpn_ip

This segment tries to extract the VPN related IP addresses from nmcli, based on the NIC type:

Variable Default Value Description
POWERLEVEL9K_VPN_IP_INTERFACE tun The VPN interface.
public_ip

This segment will display your public IP address. There are several methods of obtaining this information and by default it will try all of them starting with the most efficient. You can also specify which method you would like it to use. The methods available are dig using opendns, curl, or wget. The host used for wget and curl is http://ident.me by default but can be set to another host if you prefer.

If you activate a VPN, the icon for this segment will change to the defined VPN icon.

The public_ip segment will attempt to update your public IP address every 5 minutes by default(also configurable by the user). If you lose connection your cached IP address will be displayed until your timeout expires at which point every time your prompt is generated a new attempt will be made. Until an IP is successfully pulled the value of $POWERLEVEL9K_PUBLIC_IP_NONE will be displayed for this segment. If this value is empty(the default)and $POWERLEVEL9K_PUBLIC_IP_FILE is empty the segment will not be displayed.

Variable Default Value Description
POWERLEVEL9K_PUBLIC_IP_FILE '/tmp/p9k_public_ip' This is the file your public IP is cached in.
POWERLEVEL9K_PUBLIC_IP_HOST 'http://ident.me' This is the default host to get your public IP.
POWERLEVEL9K_PUBLIC_IP_TIMEOUT 300 The amount of time in seconds between refreshing your cached IP.
POWERLEVEL9K_PUBLIC_IP_METHODS (dig curl wget) These methods in that order are used to refresh your IP.
POWERLEVEL9K_PUBLIC_IP_NONE None The string displayed when an IP was not obtained
load

Displays one of your load averages with appropriate state coloring. The thresholds are:

  • 0.7 * NUM_CORES <: critical
  • 0.5 * NUM_CORES <: warning
  • less: normal
Variable Default Value Description
POWERLEVEL9K_LOAD_WHICH 5 Which average to show. Possible values: 1, 5 or 15
newline

Puts a newline in your prompt so you can continue using segments on the next line. This allows you to use segments on both lines, unlike POWERLEVEL9K_PROMPT_ON_NEWLINE, which simply separates segments from the prompt itself.

This only works on the left side. On the right side it does nothing.

nodeenv

Shows the currently used nodeenv. To avoid Nodeenvs activate command from interfering with Powerlevel9k, you should set NODE_VIRTUAL_ENV_DISABLE_PROMPT=1 in your ~/.zshrc.

rbenv

This segment shows the version of Ruby being used when using rbenv to change your current Ruby stack.

It figures out the version being used by taking the output of the rbenv version-name command.

  • If rbenv is not in $PATH, nothing will be shown.
  • By default, if the current local Ruby version is the same as the global Ruby version, nothing will be shown. See the configuration variable, below, to modify this behavior.
Variable Default Value Description
POWERLEVEL9K_RBENV_PROMPT_ALWAYS_SHOW false Set to true if you wish to show the rbenv segment even if the current Ruby version is the same as the global Ruby version
pyenv

This segment shows the version of Python being used when using pyenv to change your current Python stack.

The PYENV_VERSION environment variable will be used if specified. Otherwise it figures out the version being used by taking the output of the pyenv version-name command.

  • If pyenv is not in $PATH, nothing will be shown.
  • If the current Python version is the same as the global Python version, nothing will be shown.
Variable Default Value Description
POWERLEVEL9K_PYENV_PROMPT_ALWAYS_SHOW false Set to true if you wish to show the pyenv segment even if the current Python version is the same as the global Python version
rspec_stats

See Unit Test Ratios, below.

status

This segment shows the return code of the last command.

Variable Default Value Description
POWERLEVEL9K_STATUS_CROSS false Set to true if you wish not to show the error code when the last command returned an error and optionally hide this segment when the last command completed successfully by setting POWERLEVEL9K_STATUS_OK to false.
POWERLEVEL9K_STATUS_OK true Set to true if you wish to show this segment when the last command completed successfully, false to hide it.
POWERLEVEL9K_STATUS_SHOW_PIPESTATUS true Set to true if you wish to show the exit status for all piped commands.
POWERLEVEL9K_STATUS_HIDE_SIGNAME false Set to true return the raw exit code (1-255). When set to false, values over 128 are shown as SIGNAME(-n) (e.g. KILL(-9))
ram
Variable Default Value Description
POWERLEVEL9K_RAM_ELEMENTS Both Specify ram_free or swap_used to only show one or the other rather than both.
symfony2_tests

See Unit Test Ratios, below.

time
Variable Default Value Description
POWERLEVEL9K_TIME_FORMAT 'H:M:S' ZSH time format to use in this segment.

As an example, if you wanted a reversed time format, you would use this:

# Reversed time format
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}"
user

The user segment will print the username.

You can also override the icons by setting:

POWERLEVEL9K_USER_ICON="\uF415" # 
POWERLEVEL9K_ROOT_ICON="#"
POWERLEVEL9K_SUDO_ICON=$'\uF09C' # 
Variable Default Value Description
DEFAULT_USER None Username to consider a "default context".
POWERLEVEL9K_ALWAYS_SHOW_USER false Always print this segment.
POWERLEVEL9K_USER_TEMPLATE %n Default username prompt. Refer to the ZSH Documentation for all possible expansions
vcs

By default, the vcs segment will provide quite a bit of information. Further customization is provided via:

Variable Default Value Description
POWERLEVEL9K_HIDE_BRANCH_ICON false Set to true to hide the branch icon from the segment.
POWERLEVEL9K_SHOW_CHANGESET false Set to true to display the hash / changeset in the segment.
POWERLEVEL9K_CHANGESET_HASH_LENGTH 12 How many characters of the hash / changeset to display in the segment.
POWERLEVEL9K_VCS_SHOW_SUBMODULE_DIRTY true Set to false to not reflect submodule status in the top-level repository prompt.
POWERLEVEL9K_VCS_HIDE_TAGS false Set to true to stop tags being displayed in the segment.
POWERLEVEL9K_VCS_GIT_HOOKS (vcs-detect-changes git-untracked git-aheadbehind git-stash git-remotebranch git-tagname) Layout of the segment for git repositories.
POWERLEVEL9K_VCS_HG_HOOKS (vcs-detect-changes) Layout of the segment for Mercurial repositories.
POWERLEVEL9K_VCS_SVN_HOOKS (vcs-detect-changes svn-detect-changes) Layout of the segment for SVN repositories.
POWERLEVEL9K_VCS_ACTIONFORMAT_FOREGROUND red The color of the foreground font during actions (e.g., REBASE).
vcs symbols

The vcs segment uses various symbols to tell you the state of your repository. These symbols depend on your installed font and selected POWERLEVEL9K_MODE from the Installation section above.

Compatible Powerline Awesome Powerline Explanation
↑4 ↑4 icon_outgoing4 Number of commits your repository is ahead of your remote branch
↓5 ↓5 icon_incoming5 Number of commits your repository is behind of your remote branch
⍟3 ⍟3 icon_stash3 Number of stashes, here 3.
icon_unstaged There are unstaged changes in your working copy
icon_staged There are staged changes in your working copy
? ? icon_untracked There are files in your working copy, that are unknown to your repository
icon_remote_tracking_branch The name of your branch differs from its tracking branch.
icon_bookmark A mercurial bookmark is active.
@ icon_branch_powerline Branch Icon
None None icon_commit2c3705 The current commit hash. Here "2c3705"
None None icon_git Repository is a git repository
None None icon_mercurial Repository is a Mercurial repository
vcs truncation

You can limit the branch name to a certain length by truncating long names. Customizations available are:

Variable Default Value Description
POWERLEVEL9K_VCS_SHORTEN_LENGTH None This field determines how many characters to show.
POWERLEVEL9K_VCS_SHORTEN_MIN_LENGTH None This field determines minimum branch length. Branch name will be truncated if its length greater than this field.
POWERLEVEL9K_VCS_SHORTEN_STRATEGY None This field determines how branch name should be truncated. See the table below for more information.
POWERLEVEL9K_SHORTEN_DELIMITER ... Delimiter to use in truncated strings. This can be any string you choose, including an empty string if you wish to have no delimiter.
Strategy Name Description
truncate_middle Truncates the middle part of a branch. E.g. branch name is 1234-super_super_long_branch_name, then it will truncated to 1234-..._name, if POWERLEVEL9K_VCS_SHORTEN_LENGTH=5 is also set (controls the amount of characters to be left).
truncate_from_right Just leaves the beginning of a branch name untouched. E.g. branch name will be truncated like so: 1234-.... How many characters will be untouched is controlled by POWERLEVEL9K_VCS_SHORTEN_LENGTH.

For example, if you want to truncate 1234-super_super_long_branch_name to 1234-.. and don't do it with development:

POWERLEVEL9K_VCS_SHORTEN_LENGTH=4
POWERLEVEL9K_VCS_SHORTEN_MIN_LENGTH=11
POWERLEVEL9K_VCS_SHORTEN_STRATEGY="truncate_from_right"
POWERLEVEL9K_VCS_SHORTEN_DELIMITER=".."
vi_mode

This segment shows ZSH's current input mode. Note that this is only useful if you are using the ZSH Line Editor (VI mode). You can enable this either by .zshrc configuration or using a plugin, like Oh-My-Zsh's vi-mode plugin.

Variable Default Value Description
POWERLEVEL9K_VI_INSERT_MODE_STRING "INSERT" String to display while in 'Insert' mode.
POWERLEVEL9K_VI_COMMAND_MODE_STRING "NORMAL" String to display while in 'Command' mode.

To hide the segment entirely when in INSERT mode, set POWERLEVEL9K_VI_INSERT_MODE_STRING=''

virtualenv

This segment shows your Python VirtualEnv. To avoid VirtualEnvs activate command from interfering with Powerlevel9k, you should set VIRTUAL_ENV_DISABLE_PROMPT=1 in your ~/.zshrc.

Unit Test Ratios

The symfony2_tests and rspec_stats segments both show a ratio of "real" classes vs test classes in your source code. This is just a very simple ratio, and does not show your code coverage or any sophisticated stats. All this does is count your source files and test files, and calculate the ratio between them. Just enough to give you a quick overview about the test situation of the project you are dealing with.

Disabling / Enabling Powerlevel9k

You can disable P9k and return to a very basic prompt at any time simply by calling:

$ prompt_powerlevel9k_teardown

You can then re-enable it by calling:

$ prompt_powerlevel9k_setup

tl; dr

Want to just get a quick start? Check out the Show Off Your Config portion of the wiki to get going.

The Wiki also has a ton of other useful information!

License

Project: MIT

Logo: CC-BY-SA. Source repository: https://github.com/bhilburn/powerlevel9k-logo

powerlevel9k's People

Contributors

alexarawu avatar alexlafroscia avatar anion155 avatar ayyess avatar belak avatar benoitaverty avatar bhilburn avatar darkheir avatar docwhat avatar dritter avatar dualscyther avatar eviltak avatar guixxx avatar iilonmasc avatar jkoelndorfer avatar kayant avatar krischer avatar natemccurdy avatar niklas-heer avatar nmaggioni avatar onaforeignshore avatar rjorgenson avatar rmad17 avatar theminor avatar tippl avatar tritlo avatar v1rgul avatar wadkar avatar ytang avatar zikes avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

powerlevel9k's Issues

Prepare for Release v0.2.0

Announcing Code Freeze for v0.2.0 Release

Hi all -

Thanks for everyone's contributions to powerlevel9k! We have added some significant new features since the v0.1.0 release tag, and I believe now is a good time to prepare for the v0.2.0 release.

The next branch is now frozen except for bug fixes and documentation improvements. If you aren't already using next, please switch over to help us test!

Thanks so much for contributing to this project! It makes a huge difference.

Contributors to-date for v0.2.0:

@dritter
@labianchin
@jkoelndorfer
@giladgo
@christian-schulze
@tusharsrivastava
@natemccurdy
@dsager

Slow loading prompt in some repositories

I just checked out https://github.com/ryanoasis/nerd-fonts because of the discussion I saw in #95. (tl;dr: I'm using urxvt and the fallback method doesn't seem to be an option, nerd-fonts provides patched fonts for Ubuntu mono which I like).

Anyway, the prompt takes somewhere between half a second to a second to load. Even when I remove all the segments, this is the case which is a bit strange. My suspicions are:

  1. Logic for non-rendered segments is still being executed, which is wasteful
  2. Something in the logic for the VCS prompt scales with repository size (nerd-fonts is 1.8GB), which other themes (such as agnoster) do not do.

Will follow up with any findings I might make, but hopefully this helps if anyone else looks into it!

Theme breaks, if locale is "C"

Recently I stumbled upon ohmyzsh/ohmyzsh#4091 which affects powerlevel9k too. I started fixing this problem in my branch dritter/character_protection, but it is harder than I thought..

The right prompt seems to complicate the problem. Maybe you have some good Ideas to fix that. ;)

Steps to reproduce:
Set export LANG=C in your ~/.zshrc, open a new shell and voilá..

Test `next` branch - from stable v0.1.0

The theme has reached a point where most of the core infrastructure is solid, we have a growing user-base, and everything appears stable. As our contributions grow more complex, I think it is time we implement a more refined software flow.

Going forward, the master branch will be for stable code, only. With the exception of small bugfixes, all new feature development should be branched from next. We will occasionally freeze next and take time to make sure that it is, in fact, stable, and ready to merged into master, at which point the process will restart.

Since this is a new workflow, this bug will serve as a tracker for testing the current next branch. As the team grows more familiar with the process, this bug should no longer become necessary.

It would be great if those of you making contributions to the project that don't mind testing out the latest code would continually run next, and file bugs on any issues you find.

Please start basing new development off of next, and let me know if you have any questions!

@dritter, @natemccurdy

Ability to join segments

Since #164 splits the status segment into three segments, anyone who wants to use all three will have two (or more?) additional segment separators, which can take up precious space. Could we make it possible to join segments so that they display as one segment?

Unknown Characters in VCS Segment

We were discussing this previously in a separate bug, and I thought I had narrowed it down to simply a configuration issue, but now I'm not so sure.

I've been using Linux machines exclusively so far. I just now grabbed an MBP and set up OMZ and Powerline on it. It was looking great until I updated my remotes, and git reported that I was behind. I then saw a garbage character instead of the behind commit indicator. When I updated, it went away. See screenshots:

screen shot 2015-08-14 at 8 37 03 am

screen shot 2015-08-14 at 8 43 24 am

This is:

  • OSX Yosemite
  • iTerm2
  • OMZ + Powerline next branch

vi_mode segment not working as KEYMAP parameter no longer being set

Unfortunately the vi_mode segment has stopped functioning after being merged into the next branch, which I've traced back to the KEYMAP parameter no longer being set.

${KEYMAP} should evaluate to one of vicmd|viins|main but is now blank. I'm pretty new to zsh so if anyone has any ideas please chime in. In the meantime I'll do some more troubleshooting.

No warning about change in behavior within the `virtualenv` segment

I noticed while testing #119 that the virtualenv segment seems to be broken. I tried it against master and next, with master working fine but next being broken.

Never mind: it seems that instead of being broken, the condition changed. While it used to check to see if $VIRTUAL_ENV_DISABLE_PROMPT was set, it now checks to see if it is not set to true before rendering the segment, and only renders it if is it not true. There doesn't seem to be any documentation about the change, so this might confuse people that upgrade (like me).

message for dritter

This is silly, but I can't figure out another way to do this.

@dritter - Will you send me an e-mail so I have your address? You can find my e-mail on my Github profile page. Thanks! =)

awesome-patched not working in new sessions

In a session, when configured to awesome-patched and sourced, glyphs are properly displayed. But in the new session i have source again. This is same in both terminal and iTerm

iTerm2

screen shot 2015-10-21 at 12 43 43 am

zshrc

screen shot 2015-10-21 at 12 32 49 am

vi-mode segment

I'm using the vi-mode plugin, and have hacked together a custom segment to indicate the editing mode. Is this something you would consider adding to your theme?

prompt_vi_mode() {
  local mode="${${KEYMAP/vicmd/NORMAL}/(main|viins)/INSERT}"
  if [[ "$mode" == "NORMAL" ]]; then
    $1_prompt_segment "$0" "$DEFAULT_COLOR" "default" "$mode"
  else
    $1_prompt_segment "$0" "$DEFAULT_COLOR" "blue" "$mode"
  fi
}

Configure default segments?

Is it possible to configure the content of the segments (sub-segments)?

For example, I'd like to be able to hide

  • git stash numbers
  • battery percentage

screen shot 2015-12-28 at 10 27 20 pm

Switching `awesome-patched`-mode to nerd-fonts

I recently stumbled upon another font-patching project nerd-fonts which looks quite nice and foremost uses the same codepoints as the original fonts. Using this fonts instead of the awesome-terminal-fonts would improve the code in a sustainable way. We just have to test two font-settings and the users would have a nice overview of the available glyphs (in case they want to override one or another).

It still has some issues with the glyph sizes, but once that is cleaned up, I'll give it a chance. This issue is just to remember me (or to inform anybody who wants to get involved).

Tab completion in PROMPT_ON_NEWLINE draws invalid characters

Bad example, but let's say I want to run 'cat test.py', in my current directory I have: temp, test.py, test.sh...

I type:
cat -- this should select 'cat', the first command of the completion list, but I now see 'ccat' completed for me
te -- shows me [temp, test.py, test.sh], I want test.py, so I type 's' to narrow down the results and again. I now I have 'ccat ts t.'
p -- what I would see at this point is 'cat test.py', but instead I see 'ccat ts t.py'

The command runs as if it were actually 'cat test.py' when executed.

The comments suggest that the implementation of the PROMPT_ON_NEWLINE is ugly, so maybe this is a consequence of the implementation used?

Allow Conditional Segments to Always Be Shown

This is a follow-up from #113

Some segments seem to be helpful in a "server"-like context, and some in a "project"-like one. For example, I work as a web developer and sometimes need to know about the PHP-Version on the server, but on my local machine I just need that information in development project. So if I am outside of that development project (-folder) that segment is not shown.

Maybe we need a variable SHOW_CONDITIONAL_$segment_name, so users can decide if they want to show that segment in a "project"-context or always ("server"-context). In extreme we could let the user decide how that condition looks like (e.g. find -maxdepth 2 -type f -name '*.php' | head -n 1 for a quick lookup of PHP-files).

The bullet-train guys have a similar "project-" approach in some of their segments (like the prompt_virtualenv or prompt_ruby).

I have implemented a first draft in my improve_rvm branch (and only for the ruby_version segment).

/cc @alexlafroscia

VCS Segment doesn't work with Mercurial

I have a fairly non-customized oh-my-zshell setup right now, and noticed the VCS segment isn't picking up any changes in a mercurial directory.

$ echo $VCS_WORKDIR_DIRTY 
>> false

Re-read the source and found the appropriate option, my bad :)!

Although enabling POWERLEVEL9K_SHOW_CHANGESET=true didn't work for me.

Awesome Powerline Fonts dose not worked

this is my .zshrc content:

# Path to your oh-my-zsh installation.
# Path to your oh-my-zsh installation.
export ZSH=/Users/rlanffy/.oh-my-zsh

# Set name of the theme to load.
# Look in ~/.oh-my-zsh/themes/
# Optionally, if you set this to "random", it'll load a random theme each
# time that oh-my-zsh is loaded.
#ZSH_THEME="agnoster"
ZSH_THEME="powerlevel9k/powerlevel9k"
DEFAULT_USER=""
POWERLEVEL9K_MODE='awesome-patched'
#POWERLEVEL9K_MODE='flat'
POWERLEVEL9K_PROMPT_ON_NEWLINE=true
#POWERLEVEL9K_MULTILINE_FIRST_PROMPT_PREFIX="↱"
#POWERLEVEL9K_MULTILINE_SECOND_PROMPT_PREFIX="↳ "

# Uncomment the following line to use case-sensitive completion.
# CASE_SENSITIVE="true"

# Uncomment the following line to use hyphen-insensitive completion. Case
# sensitive completion must be off. _ and - will be interchangeable.
# HYPHEN_INSENSITIVE="true"

I installed pro like how to install as your said.

when the config is POWERLEVEL9K_MODE='awesome-patched' and the terminal is like this:
terminal1

when the config is POWERLEVEL9K_MODE='flat' and the terminal is like this:

terminal2

Improve utility-function loading

Disclaimer: This is by now untested. For now this issue is just a reminder for me (or anybody who is interested in testing this).

Some users load the theme with zgen (like tritlo). This might be a problem, if zgen loads the theme as a function (like prezto does).

So we need a solution to find the file in which a function was defined, to get the base path of our theme. Or we make this configurable by a variable, so users could work around that problem.

precmd:4: command not found: vcs_info_hookadd

Tried enabling the theme but I receive the precmd:4: command not found: vcs_info_hookadd info in the command line and it seems like it tries to display VCS related info no matter if the current folder is a repository or not.

error

Purpose of home icon in dir segment?

Having updated this theme I now get a home icon in front of my dir segment, however this icon persists even when the path is truncated and thus does not include the home directory. I guess my expected behaviour would be the home icon replaces ~, but it seems to be in addition to it and regardless of where you are in the tree?

Color capability warning

In powerlevel9k_init() there's this bunch of code :

Display a warning if the terminal does not support 256 colors

local term_colors
term_colors=$(tput colors)
if (( term_colors < 256 )); then
print -P "%F{red}WARNING!%f Your terminal supports less than 256 colors!"
print -P "You should put: %F{blue}export TERM="xterm-256color"%f in your ~/.zshrc"
fi

Unfortunately, on FreeBSD, "tput colors" is the same as "tput col" and returns the number of columns of the terminal. So, I get this :
$ echo $TERM
xterm-256color
$ tput colors
80
// resizing window
$ tput colors
93

So I get the warning every time I open a new shell... even if the environment is nicely configured.

To get the number of colors, the command is :
$ tput Co
256

I suggest to use the command "echotc Co", which is a zsh builtin, to get the color capabilities of the terminal. That command is much more portable than tput.

Can't change status icon color

Unfortunately, it is not possible to change the color of the fail icon. I tried to set:

POWERLEVEL9K_STATUS_FOREGROUND='white'
POWERLEVEL9K_STATUS_BACKGROUND='red'

The background is now red. However, the fail icon is still red, too.

My current fix is to overwrite the prompt_status() method, as the color of the icon is hardcoded:

[[ "$RETVAL" -ne 0 ]] && symbols+="%{%F{red}%}$(print_icon 'FAIL_ICON')%f"

to

[[ "$RETVAL" -ne 0 ]] && symbols+="%{%F{white}%}$(print_icon 'FAIL_ICON')%f"

VCS Segment: Extra Space During Action State

I noticed this while merging your latest PR, @dritter, but the bug wasn't introduced in your PR. In fact, it's not even relegated to next - it also exists on master.

During a normal workflow, everything looks fine:

screen shot 2015-08-26 at 8 00 58 pm

But look what happens when you are mid-merge:

screen shot 2015-08-26 at 8 01 16 pm

Note the extra space before the branch icon.

And, like I said, this bug actually exists on master, as well:

screen shot 2015-08-26 at 8 06 17 pm

History substring search

When I use this theme the the history substring search plugin does not work. Any ideas why or has anyone seen this problem before?

Thank you

Mercurial does not show changes, without changeset

Just a reminder for me:
If no changeset is shown, and the repository is dirty, no information about the repository state is given (the background color dosn't change to orange).

Problem is, that the performance-boost parses that information directly out of the mercurial files, and the theme does not know about the state.

Removing the following line should fix that problem. Sadly the theme gets slightly slower in mercurial repositories.

zstyle ':vcs_info:*' use-simple true

Unreadable vcs format string in left prompt

Recently I updated the powerlevel9k to latest master branch and I find a small bug in left prompt.
If the vcs repository backend is git-svn, the left prompt will extend with a string 'git-svn' which is very hard to read because it's font color is same as default foreground color.
So I made a small fix to solve the problem, hope it can help others with the same problem.

diff --git a/powerlevel9k.zsh-theme b/powerlevel9k.zsh-theme
index 1b52d03..1fed0d9 100644
--- a/powerlevel9k.zsh-theme
+++ b/powerlevel9k.zsh-theme
@@ -217,7 +217,7 @@ 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:(git|git-svn):
' 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"
@@ -225,7 +225,7 @@ zstyle ':vcs_info:
' actionformats " %b %F{red}| %a%f"
zstyle ':vcs_info:' stagedstr " %F{$VCS_FOREGROUND_COLOR}$VCS_STAGED_ICON%f"
zstyle ':vcs_info:
' unstagedstr " %F{$VCS_FOREGROUND_COLOR}$VCS_UNSTAGED_ICON%f"

-zstyle ':vcs_info:git_+set-message:' hooks vcs-detect-changes git-untracked git-aheadbehind git-stash git-remotebranch git-tagname
+zstyle ':vcs_info:(git|git-svn)
+set-message:' hooks vcs-detect-changes git-untracked git-aheadbehind git-stash git-remotebranch git-tagname
zstyle ':vcs_info:hg
+set-message:_' hooks vcs-detect-changes

For Hg, only show the branch name

Installation of fonts.

I've installed the fonts but my terminal looks like this. (I'm using compatible but it is not very compatible)

image

Setting for newline after result?

Example:
screen shot 2015-12-28 at 1 43 22 pm

I'd prefer to do this without messing with the function internals and injecting a "\n" into something.
Is there/could there be a setting for this?

Thanks.

Port to fish-shell

Hi!

I'm currently considering to port the theme to fish-shell as I think this would be a nice feature. I'm not sure about this intent as the shells differ substantially. But it might be worth the effort.
What do you think?

README: Symbol table wrong about branch icon

Our readme currently shows this in the symbol table:

| @ | icon_branch_powerline | | Branch Icon
| None | None | icon_commit2c3705 | The current commit hash. Here "2c3705"
| None | None | icon_git | Repository is a git repository
| None | None | icon_mercurial | Repository is a Mercurial repository

And the branch icon is supposed to be configurable. I don't think this is quite right, though. What is currently shown there as the branch icon is actually used as the Git and Hg icons, and is always present. The branch icon is different, and not always present.

@dritter

Battery displays incorrect time remaining

In line 272 in the prompt_battery function, there is some attempt at converting the 00:08:47 string that acpi outputs to hours and minutes, but for me, it just outputs an incorrect time, i.e., when acpi says that 00:08:47 is remaining, we get

$ date -u -d @000847 +%k:%M 
0:14

which is not the same as the 0:09 that should be reported.

Prompt is empty - please help

I'm having trouble getting powerlevel9k to work for me, this is the output:
screen shot 2015-06-08 at 12 57 16 am

My .zshrc is:

#!/usr/bin/env zsh

source ~/.dotfiles/non-packaged-repos/antigen/antigen.zsh

antigen use oh-my-zsh

export DEFAULT_USER=simonweil
POWERLEVEL9K_LEFT_PROMPT_ELEMENTS=(context dir vcs status)
POWERLEVEL9K_RIGHT_PROMPT_ELEMENTS=(rbenv virtualenv history time)
antigen theme bhilburn/powerlevel9k powerlevel9k

# Tell antigen that you're done.
antigen apply

When I use antigen theme funky all is fine.

As I'm new to zsh I have no real idea what to do...

f3d2a07 introduces a syntax error?

It has been a while since my last update of this theme. It looks like f3d2a07 introduces a regression:

powerlevel9k.zsh-theme:65: parse error near `|'

This causes the powerline-style markup of the segments to not colorize or show special characters. This issue is present in the current version as well:

powerlevel9k.zsh-theme:232: parse error near `|'

I'll follow up if I find the issue or a fix.

The solution suggested for the terminal color warning is not clear

When starting a terminal with powerlevel9k as the theme, the following warning is issued:

WARNING! Your terminal supports less than 256 colors!
You should put: export TERM="xterm-256color" in your ~/.zshrc

Looking into the theme source, I see the following:

 # Display a warning if the terminal does not support 256 colors
  local term_colors
  term_colors=$(tput colors)
  if (( term_colors < 256 )); then
    print -P "%F{red}WARNING!%f Your terminal supports less than 256 colors!"
    print -P "You should put: %F{blue}export TERM=\"xterm-256color\"%f in your \~\/.zshrc"
  fi

When running tput colors in the terminal I get 8.

I added export TERM="xterm-256color" to my .zshrc and then tput colors returns 256, but the warning is still issued.

I am running Ubuntu 14.04, and the message occurs in all my terminal emulators.

On another machine, where I am running with d75cdf3, I do not see the message (as no check is implemented there).

`dir` segment: Extra space in prefix on `next` branch

On the next branch, there is an extra leading space on the dir segment. Check out the screenshot below, where I'm on the next branch, then checkout master and open a new terminal:

dirsegment

You can see the extra leading space in the first prompt.

virtualenv not displaying

I can't seem to get the virtualenv to display despite setting in .zshrc the line POWERLEVEL9K_RIGHT_PROMPT_ELEMENTS=(virtualenv)

Cygwin integeration

EDIT: Solution was to try many patched fonts. For me, the Deja Vu Sand Mono font worked for everything except the Ruby icon.
The point is that many fonts will not work on Windows. As of now, the font linked above is the only font that seems to work for the majority of Windows users.

Is it possible to get this to work with Cygwin? I followed instructions but I still get empty boxes for symbols. I ran the install.sh script to install fonts, but I can't seem to get any of them to work. I'm running Cygwin inside Cmder (which uses Conemu), and I selected the Meslo LG M for Powerline as my font.

image

I was able to get this completely configured on my Mac (looks pretty awesome!), but not via Cygwin (darn it Windows!)

Icons: The Masterplan

As you requested in #91 , here is the masterplan to get to stable icons. I'll describe it here from the beginning, it may serve as possible explanation for other users.

Documentation

Introduction

This theme uses special icons to look fancy. So we need special fonts to display these special icons correctly. There are two ways to use these fonts:

  1. We can use pre-patched fonts. This is the preferred way for all POWERLEVEL9K_MODEs: default, compatible and awesome-patched.
  2. Every operating system has a mechanism to fallback to the correct fonts. This is a more complicated way to install the fonts, as usually extra software is necessary.

Here I focus on the first (pre-patched) way, because even this is the easier method, some parts must be understood.

Installation

Three parts play a role to display the theme correctly:

  1. The font itself: It must provide the correct glyphs that the theme wants to display.
  2. The terminal emulator: The font must be proper installed in the operating systems font manager and set in your terminal emulator (such as iTerm2, Konsole, Terminal, RxVT, etc.) as font.
  3. The theme: It prints special characters, representing a glyph in your font. As different fonts use (at least for these special characters) different code points, the theme needs to know which set of code points it should use. These sets are represented as POWERLEVEL9K_MODE.
    For the default-mode, you just need a powerline-patched font. For awesome-patched, you need a awesome-patched font.
    Unfortunately, there is no way to detect the used font automatically because the shell doesn't know much about how to render its content.

Masterplan

Far-future plan

As the awesome-terminal-fonts are not the only project which offer a broad range of pre-patched fonts and besides look somewhat inactive, I think the best would be to switch to nerd-fonts. They seem to be more active, have stable codepoints over different stategies, more icons. On the downside, they have some serious issues which need to be fixed first.
The other long-term solution could be to unify the codepoints in the different strategies in the awesome-terminal-fonts project.
Status: Open

Interim solution

awesome-terminal-fonts are currently problematic, as the relocate all codepoints regardless whether this is necessary or not. The result is that the fallback-, patched- and original fonts all have different codepoints. To relieve the pain a bit for our users, we could offer a new POWERLEVEL9K_MODE="awesome-fallback", which is a new set of codepoints in the icons-variable. I would think this could be the codepoints from master...tcbbd:master . This isn't a pretty solution, but the quickest.
Status: Done. See #108

@bhilburn I hope that helped to clear my plan up. ;)

rprompt on same line as lprompt, not one second line

Greetings,

when I set

POWERLEVEL9K_PROMPT_ON_NEWLINE=true

the left prompt appears on the same line as the rprompt, and not the line below (as seen in the image associated with the variable).
rpromptnotonnewline

My config is as follows. My terminal is "terminator", though this also happens on "gnome-terminal"

POWERLEVEL9K_MODE='awesome-fontconfig'
POWERLEVEL9K_LEFT_SEGMENT_SEPARATOR='▶'
POWERLEVEL9K_RIGHT_SEGMENT_SEPARATOR='◀'
POWERLEVEL9K_PROMPT_ON_NEWLINE=true
POWERLEVEL9K_MULTILINE_FIRST_PROMPT_PREFIX=""
POWERLEVEL9K_MULTILINE_SECOND_PROMPT_PREFIX="\e[44m\e[1m\e[33m $ \e[0m\e[34m▶\e[0m "

POWERLEVEL9K_LEFT_PROMPT_ELEMENTS=(context time dir)
POWERLEVEL9K_RIGHT_PROMPT_ELEMENTS=(status vcs)

POWERLEVEL9K_SHORTEN_DIR_LENGTH=3
POWERLEVEL9K_SHORTEN_STRATEGY="truncate_middle"

POWERLEVEL9K_STATUS_VERBOSE=false
POWERLEVEL9K_TIME_FORMAT="%D{%T}"

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.