Skip to content
This repository has been archived by the owner on Apr 24, 2020. It is now read-only.

Something between tag 0.6.4 and tag 0.6.5 is causing the history prompt to break on remote server #969

Closed
bhayden53 opened this issue Aug 24, 2018 · 3 comments

Comments

@bhayden53
Copy link

bhayden53 commented Aug 24, 2018

I have been pulling my hair out over a weird issue with the history prompt that I started seeing after a fresh install of powerlevel9k. I have tested it over several of the powerline fonts and see the same thing.

These are my prompt elements:
POWERLEVEL9K_LEFT_PROMPT_ELEMENTS=(context dir anaconda vcs)
POWERLEVEL9K_RIGHT_PROMPT_ELEMENTS=(status root_indicator background_jobs history time)

On tag 0.6.4, I see this:
historybug0 6 4

On 0.6.5 I see this:
historybug0 6 5

Requested details:
-zsh version: zsh 5.0.2 (x86_64-redhat-linux-gnu)
-Have tested with and without oh-my-zsh, which I normally use. Above screenshots without oh-my-zsh installed.
-P9K was installed by cloning the repo, adding source ~/powerlevel9k/powerlevel9k.zsh-theme to my ~.zshrc, and then to debug I started switching tags and checking behavior.
-I use iterm2, and in this case I am ssh'ed into a remote server.

-Behavior persists across powerline fonts, but the font in the screenshots is Source Code Pro for Powerline
-$POWERLEVEL9K_MODE is not set in my environment.
-$P9k/debug/font-issues.zsh is empty
-there are some blank icons in get_icon_names, but nothing that looks out of the ordinary.

@dritter
Copy link
Member

dritter commented Sep 6, 2018

Hi @drhay53 ,
You are using a quite old ZSH version that is not supported by P9K any more. Could you update your Shell and try again?

@bhayden53
Copy link
Author

My mistake, I did not notice the minimum requirements for ZSH on the wiki. Unfortunately I don't have control over this on the server, and so I will have to stick with 0.6.4 until something changes.

@dritter
Copy link
Member

dritter commented Sep 6, 2018

There is still a thing you could do: The problem appears with certain colors only and the default history segment uses grey50 as background color. So, if you set POWERLEVEL9K_HISTORY_BACKGROUND='244' the problem should disappear.

@dritter dritter closed this as completed Nov 12, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants