You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I was able to install power-line in my current git bash shell on Windows 10. Everything is fine, but there is no python environment in the prompt.
With respect to the default installation steps, I made the following additional ones:
(extra step) I had to add the following lines to ~/.bashrc because the command conda activate <env> was giving an error.
export PYTHONIOENCODING="utf-8"
source ~/miniconda3/etc/profile.d/conda.sh
# Theme
THEME=$HOME/.bash/themes/git_bash_windows_powerline/theme.bash
if [ -f $THEME ]; then
. $THEME
fi
unset THEME
However, if I check the theme.bash I do not find any reference to the python environment, while I can see a reference to it in the linked file https://github.com/Bash-it/bash-it/tree/master/themes/powerline, upon which the theme is based.
Is it possible to display the Python environment, in particular a conda environment, also in this powerline for the git bash?
The text was updated successfully, but these errors were encountered:
Hello, I was able to install power-line in my current git bash shell on Windows 10. Everything is fine, but there is no python environment in the prompt.
With respect to the default installation steps, I made the following additional ones:
~/.bashrc
because the commandconda activate <env>
was giving an error..bash/themes/git_bash_windows_powerline/theme.bash
config.json
in~/.config/powerline-shell/
with this content:My
~/.bashrc
is:However, if I check the
theme.bash
I do not find any reference to the python environment, while I can see a reference to it in the linked filehttps://github.com/Bash-it/bash-it/tree/master/themes/powerline
, upon which the theme is based.Is it possible to display the Python environment, in particular a conda environment, also in this powerline for the git bash?
The text was updated successfully, but these errors were encountered: