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

Use `env` to run $POWERLINE_CONFIG_COMMAND in fish 

Reasoning: everywhere else $POWERLINE_CONFIG_COMMAND specifies one command, not 
command with arguments. But with eval this is changed. `env` will receive this 
variable as one argument, so the meaning is consistent again.
This commit is contained in:
ZyX 2015-01-06 16:17:51 +03:00
parent b17d03e688
commit 2a2da9d43f
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
powerline/bindings/fish/powerline-setup.fish
View File

@ -29,9 +29,9 @@ function powerline-setup
end
end
if eval $POWERLINE_CONFIG_COMMAND shell --shell=fish uses prompt
if env $POWERLINE_CONFIG_COMMAND shell --shell=fish uses prompt
if test -z "$POWERLINE_COMMAND"
set -g POWERLINE_COMMAND (eval $POWERLINE_CONFIG_COMMAND shell command)
set -g POWERLINE_COMMAND (env $POWERLINE_CONFIG_COMMAND shell command)
end
function --on-variable fish_bind_mode _powerline_bind_mode
set -g -x _POWERLINE_MODE $fish_bind_mode
@ -81,7 +81,7 @@ function powerline-setup
_powerline_set_default_mode
_powerline_update
end
if eval $POWERLINE_CONFIG_COMMAND shell --shell=fish uses tmux
if env $POWERLINE_CONFIG_COMMAND shell --shell=fish uses tmux
if test -n "$TMUX"
if tmux refresh -S ^/dev/null
function _powerline_tmux_setenv