Open darek-mydlarz opened 2 years ago
With p10k running kubie ctx
spawns a new shell, which is a very good idea, but seems to dismiss the shells configuration, which is a bad idea, and starts p10k configure dialog for me. My hope was that
prompt:
disable: true
would address that. It didn't. If that was the intension I'd be very glad to have this one fixed.
Facing a same issue here. Zsh + p10k
When I start a new shell with kubie ctx
and prompt disable, the prompt on the new shell is a bloat of strings like
${$((_p9k_on_expand()))+}${_p9k__raw_msg-}${_p9k__raw_msg::=}${(e)_p9k_t[7]}${_p9k__1-${${:-${_p9k__d::=0}${_p9k__rprompt::=${_p9k__1r-${${:-${_p9k__bg::=NONE}${_p9k__i::=0}${_p9k__sss::=}}+}${${:-${P9K_CONTENT::=}${_p9k__n::=}${${${_p9k__bg:-0}:#NONE}:-${_p9k__n::=8}}${_p9k__n:=${${(M)${:-x$_p9k__bg}:#x(236|236)}:+10}}${_p9k__n:=11}${_p9k__c::="${P9K_CONTENT}"}${_p9k}}${_p9k__e::=${${_p9k__1r:+00}:-${${():-$_p9k__c1}[-1]}0}}}+}${${_p9k__e:#00}:+${_p9k_t[$_p9k__n]/<_p9k__w>/$_p9k__w}${_p9k__c}${${:-${_p9k__w::= }${_p9k__sss::= }${_p9k__i::=1}${_p9k__bg::=236}}+}}${${:-"${${():-0}:#0}"}:+${${:-${P9K_CONTENT::=""}${_p9k__n::=}${${${_p9k__bg:-0}:#NONE}:-${_p9k__n::=12}}${_p9k__n:=${${(M)${:-x$_p9k__bg}:#x(236|236)}:+14}}${_p9k__n:=15}}${_p9k__e::=${${_p9k__1rbackground_jobs+00}:-${${():-$_p9k__c1}[-1]}1}}}+}${${_p9k__e:#00}:+${_p9k_t[$_p9k__n]/<_p9k__w>/$_p9k__w}${_p9k__c}${${(M)_p9k__e:#11}:+ }$_p9k__v${${:-${_p9k__w::= } [...]
Hello!
Despite disabling prompt information in the
~/.kube/kubie.yaml
file, the information is still printed to the console. I have reloaded the shell.I want to get rid of those last line printed which has appeared after installing kubie on my machine.
I use MacOS with ZSH + Oh-My-ZSH.