…t only if icon is unavailable

This happens if a user switches from a subdirectory of $HOME
back to the home folder and truncation strategy is "truncate
folders from left". Then the folder is displayed as .../~

PR: Powerlevel9k#773

`$pipestatus` is returning all zeros when using `[[  ]]` expressions
that are false.

This works around it by using `$status` (A.K.A. `$?`) when `$pipestatus`
has only 1 items.

Fixes Powerlevel9k#749

…o display prompt_rbenv if rbenv_version_name is the same as rbenv_global

…SHOW variable description

see those files and look for `rvm`

+ https://github.com/bhilburn/powerlevel9k/blob/master/CHANGELOG.md
+ https://github.com/bhilburn/powerlevel9k/blob/master/powerlevel9k.zsh-theme

Fix table formatting in README

add rvm to README

Fix Brightness Table in README

workaround for ZSH status behavior

Fixed home abbreviation not being exclusive with circular navigation

…always-displays-#777

Rbenv prompt option always displays Powerlevel9k#777

Hides the battery segment if percentage hits 100%

Variable now holds an integer, if your battery status is greater or equal to this integer the
segment will be hidden

Fix test for rust segment

…name

Update default public ip file name

This fixes Powerlevel9k#841

Conflicts were:
- README.md: Two commits targeted the brightness table. Powerlevel9k#781 from
14. April 2018 on master and Powerlevel9k#684 from 05. December 2017 on next.
- powerlevel9k.zsh-theme: Two commits targeted the rbenv segment. Both
achieve the same thing: To show the Ruby version number always. Powerlevel9k#795 on
next from 14. April 2018 and Powerlevel9k#610 on master from 28. September 2017. I
went with Powerlevel9k#795 here as this - although being newer - is the one on
master, and that should be more stable.

… staging_065

Conflicts were:
- functions/vcs.zsh: Two commits avoided wrapper behaviour. Powerlevel9k#685
in grep, Powerlevel9k#797 in git.

Conflicts were:
- functions/icons.zsh: The Java Segment was added on master, but on next
were added various Segments with icons in the meantime.
- powerlevel9k.zsh-theme: Java Segment was added on master, Dropbox
Segment was added on next.

Conflicts were:
- powerlevel9k.zsh-theme and test/segments/rust_version.spec:
rust_version Segment changed (Powerlevel9k#641) on master and colors got
names (Powerlevel9k#703) on next.

Conflicts were:
- test/segments/rust_version.spec and powerlevel9k.zsh-theme. Powerlevel9k#826
removes grep from parsing the rust version on next; Powerlevel9k#703 changes color
names.

… into staging_065

…ment' into staging_065

Conflicts were:
- test/segments/command_execution_time.spec and
test/segments/go_version.spec: All conflicts come from renaming color
names on next (Powerlevel9k#703) and adding a whitespace to the Visual Identifier
(Powerlevel9k#854) on master.

- Fix the variable name for the VCS shorten strategy.
- Add a heading for VCS truncation.

ZSH displays the right prompt indented one space from the right
margin. This can be tweaked with ZLE_RPROMPT_INDENT=0, but that
makes display problems very likely and I don't recommend it. But
all is not lost.

The %E prompt format does continue the current background color
through that last indent space. So it can *look* like our prompt
goes right up to the margin, if:
1) We remove the trailing space from the last segment, and
2) We add %E before clearing the background color

…ng_065