tyler.durden
/
powerline
mirror of https://github.com/powerline/powerline.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Do not bother with testing or setting POWERLINE_CONFIG_COMMAND 

Instead just test whether using $POWERLINE_CONFIG_COMMAND succeeds and if it 
does not run just `powerline-config tmux setup`. Problem is that tests in vterm 
fail *not* because sleeping time is too short, but because `powerline-config 
tmux setup` for some reason is not launched at all. I am not sure whether this 
construct is going to fix things.

Also ref #875. I am very unsure this commit will fix the issue, but since I do 
not know what is the reason for this issue at all… who knows.
This commit is contained in:
ZyX 2015-02-07 11:13:16 +03:00
parent e280313b0f
commit d5d138f83d
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
powerline/bindings/tmux/powerline.conf
View File

@ -1,2 +1,2 @@
if-shell 'test -z "$POWERLINE_CONFIG_COMMAND"' 'set-environment -g POWERLINE_CONFIG_COMMAND powerline-config; run-shell "env \"\$POWERLINE_CONFIG_COMMAND\" tmux setup"' 'run-shell "env \"\$POWERLINE_CONFIG_COMMAND\" tmux setup"'
if-shell 'env "$POWERLINE_CONFIG_COMMAND" tmux setup' '' 'run-shell "powerline-config tmux setup"'
# vim: ft=tmux