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

Use `env` for running $POWERLINE_CONFIG_COMMAND 

This way we are making sure that this variable is always treated as a single
path to executable which is not so in case of `eval`.
This commit is contained in:
ZyX 2015-01-16 22:50:18 +03:00
parent faef4585b2
commit c43bd06bd6
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 "eval \$POWERLINE_CONFIG_COMMAND tmux setup"' 'run-shell "eval \$POWERLINE_CONFIG_COMMAND tmux setup"'
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"'
# vim: ft=tmux