Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP


Documentation: Make powerline easier to install and more portable #395

pearofducks opened this Issue · 4 comments

3 participants


Tested across 3 different OSes now (including MacOS with only vim installed by homebrew) and this works:

  1. Use a common vim package manager like vim-pathogen or vundle to get this repo into ~/.vim/bundle
  2. Set-up powerline using much easier relative paths

  3. vim: set rtp+=~/.vim/bundle/powerline/powerline/bindings/vim

  4. tmux: source ~/.vim/bundle/powerline/powerline/bindings/tmux/powerline.conf
    • Note the lack of quotes here, that allows for ~ to be used.
  5. zsh:
    • export PATH="$HOME/.vim/bundle/powerline/scripts/:$PATH"
    • . ~/.vim/bundle/powerline/powerline/bindings/zsh/powerline.zsh

Since the big draw (as I could see) for vim-powerline was the ability to get good looking vim on a variety of systems quickly and easily, it makes sense to try to duplicate this ability with powerline. :)


Thx for the ~ tips !


Use standard vim package manager to get this repo into ~/.vim/bundle

These are not standard ones, standard one is GLVS (getlatestvimscripts). With VAM it is as easy as

call vam#ActivateAddons(['powerline'])

You're right, sorry about that, hastily worded. :) I've updated my original post with more verbose language to avoid confusion!


The documentation uses {repository_root} for zsh, tmux and vim. It is not hard to guess that in case of vundle installation {repository_root} is ~/.vim/bundle/powerline. Additionally I do not think supporting non-pip and non-system-package-manager installations is a good idea at all and all what is needed in contained in documentation (note: no update to $PATH is needed due to recent changes in all shell bindings, though they are needed for tmux).

By the way, vim-pathogen is not a package manager. You cannot use it to get powerline repo anywhere because it does not support installing plugins.

@ZyX-I ZyX-I closed this
@ZyX-I ZyX-I removed the doc update label
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.