New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
powerline #850
Comments
|
If you install via pip you must add the place where pip puts scripts to $PATH. |
|
This is usually $HOME/.local/bin. |
|
Currently my path is as follows: Seems to still be giving me the error from above. Is it because it's trying to reference the script via a direct path that doesn't exist? |
|
Are you sure this is $PATH at the point where powerline script is sourced? If "which powerline" is able to find powerline script everything should work. |
|
I've set it in my |
|
Can you actually check it? 27.03.14, 21:03, "Alexander Trauzzi" notifications@github.com":
Sent from Yandex.Mail for mobile: http://m.ya.ru/ymail |
|
When I open a new terminal and type Also, |
|
Additionally, if I just manually source the powerline bash config for my individual terminal session, I get: Still seems like it's trying to find the ** Is it because |
|
And sorry for the spam, I just put: ...right after the detection to override it to the normal command. Seems to work. It looks like |
|
I do not see a reason for which not to work. More likely PATH setting is modified after sourcing. 28.03.14, 15:14, "Alexander Trauzzi" notifications@github.com":
Sent from Yandex.Mail for mobile: http://m.ya.ru/ymail |
|
As I mentioned. In a terminal where I can run the powerline command, |
|
|
Tilde character must not be in $PATH. Of course detection does not work: according to the standard it has no special meaning, tilde expansion is a shell feature. Though I thought which is built-in (in zsh it is) and uses the exact same code to find executable as shell does. 28.03.14, 15:30, "Alexander Trauzzi" notifications@github.com":
Sent from Yandex.Mail for mobile: http://m.ya.ru/ymail |
|
I had the same issue this is how I was able to get things working. In if [ -d "$HOME/.local/bin" ]; then
PATH="$HOME/.local/bin:$PATH"
fi
export POWERLINE_COMMAND=powerlineHope that might help. System Info |
|
Having this same error in Ubuntu 15.10 Although none of the solutions above fixed this issue. which powerline returns I tried going to this directory, but it doesn't exist |
|
Here's what I did to get things working on Ubuntu 15, using jake$ which powerline-config
~/.local/bin/powerline-configThen, in my export PATH="$HOME/.local/bin:$PATH"
export POWERLINE_COMMAND=powerline
export POWERLINE_CONFIG_COMMAND=powerline-config
powerline-daemon -q
POWERLINE_BASH_CONTINUATION=1
POWERLINE_BASH_SELECT=1
. ~/.local/lib/python2.7/site-packages/powerline/bindings/bash/powerline.sh |
|
@jakies it's work for me. on
|
|
Was having same issue, works for me |
|
Thanks if [ -d "$HOME/.local/bin" ]; then
PATH="$HOME/.local/bin:$PATH"
fi
export POWERLINE_COMMAND=powerlineOn my .bashrc works on my Bash On Windows (Ubuntu) |
|
It doesn't work when install by pip pip install powerline-statusBut work after sudo apt install powerlineFixed on Ubuntu 16.04.1 LTS |
|
hum! |
I'm getting the following message when trying to configure Powerline with Bash on Ubuntu 13.10:
The text was updated successfully, but these errors were encountered: