Skip to content
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

Bash powerline somehow broken after setting zsh as default shell (Manjaro/Arch) #285

Closed
fiechr opened this issue Feb 8, 2021 · 4 comments
Labels

Comments

@fiechr
Copy link

fiechr commented Feb 8, 2021

This may not be a bug at all, but I don't know where to ask...

I've used the package manager to install powerline-go and it worked flawlessly with Bash as default shell for my user account. I'm using the Fira Code Nerd Font and the Plasma Konsole application as well as kitty terminal.

Yesterday I decided to try out zsh (without powerline-go for now) and switch the default shell using chsh. But if I now open a new window with Bash explicitly set as shell (while the default shell still being zsh), I only get this:
powerline-go-issue01

The font is still the same and $TERM is set to xterm-256color. It's the same in Konsole and kitty. Shell looks fine, when I comment the added lines for powerline-go in the .bashrc.

Any ideas what could cause this?

@fiechr fiechr added the bug label Feb 8, 2021
@elig0n
Copy link
Contributor

elig0n commented Feb 27, 2021

try to pass -shell bash in _update_ps1 function in your .bashrc

@fiechr
Copy link
Author

fiechr commented Mar 3, 2021

Thanks!

@fiechr fiechr closed this as completed Mar 3, 2021
@andrzejnovak
Copy link

Could this get pinned/added to README? I've spent way too long trying to reinstall everything several times thinking I was keeping some corrupted files somewhere

@justjanne justjanne pinned this issue Mar 6, 2021
algono added a commit to algono/dotfiles that referenced this issue Jul 11, 2021
@scop
Copy link
Contributor

scop commented Sep 21, 2022

I believe this may have been fixed with #312.

Explicitly setting the shell isn't a bad idea when applicable though, as doing so avoids doing the shell detection repeatedly which might (or not) cause measurable amount of time spent on each run.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants