@WyRe You mentioned that if you DO source powerlevel9k, then LC_CTYPE is not set. What happens if you DON'T source powerlevel9k? Is LC_CTYPE set in this case?
they say this is not normal
If you are talking about LC_CTYPE environment variable, it's absolutely normal and very common for it to not be defined whether you are in a TTY or not. Unless you explicitly set LC_CTYPE somewhere (most people don't do this), it won't be defined.
@WyRe
With p10k I have not this issue
Thanks, this is useful to know. Curious, why do you care about p9k then?
And people in #archlinux freenode channel do say this is wrong
What exactly do they say is wrong? It's definitely not wrong nor unexpected to have undefined LC_CTYPE. It is, in fact, undefined on archlinux by default. It's easy to test. Let's spin up arch and see what we get.
% docker run -it --rm archlinux/base bash
[root@c2ef4adaec6c /]# echo ${LC_CTYPE:-not set}
not set
[root@c2ef4adaec6c /]# echo ${LANG:-not set}
en_US.UTF-8
[root@c2ef4adaec6c /]# locale
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=As you can see, LANG is defined while LC_CTYPE isn't. I keep it this way and I suspect that most users do the same.
However, what archlinux does is moot. If powerlevel9k is unsetting LC_CTYPE, it's a bug in powerlevel9k because it's obviously not supposed to change environment variables. You can easily verify this by typing zsh -f, then echo $LC_CTYPE, source path/to/powerlevel9k.zsh-theme and another echo $LC_CTYPE.
@WyRe
well, I don't know too much about env vars, but yes, they say something like LC_CTYPE is not explicitly set but it takes its value from LANG
If they mean LC_CTYPE category of locale, this is obviously true (not just on archlinux but everywhere).
the point is ... when I use p9k in a tty the 'locale' output shows a LC_CTYPE empty
So the environment variable LC_CTYPE does not get unset by powerlevel9k but LC_CTYPE category of locale does? Can you verify it by typing the following, one command at a time?
zsh -flocale | grep LC_CTYPEsource path/to/powerlevel9k.zsh-themelocale | grep LC_CTYPE
If (2) and (4) produce different output, open a bug against powerlevel9k. It's unlikely to get any attention but it shouldn't affect you because you know about the existence of powerlevel10k, which, according to your earlier comment, doesn't have this bug.
@romkatv when I do your steps (2) and (4) does produce the same output, but if I do
- Comment
sourceline inside.zshrc - Go to tty3, login and
locale | grep LC_CTYPE source path/to/powerlevel9k.zsh-themelocale | grep LC_CTYPE
then I get a different output in (2) and (4); in fact the output in (4) is empty.
@mikek2
Is there a way to copy the contents of the zsh terminal with it coming out cleanly?
There is, but it's not easy. If you want your prompt to look decent once you copy-paste it, you need to restrict the choice of glyphs to those found in most fonts. Absolutely avoid glyphs with code points from Private Use Area (from U+E000 to U+F8FF) as those are by definition font-specific and non-portable. The triangles in your prompt (U+E0B0) fall within Private Use Area, so they turn into question marks or some other weird thing when viewed with most fonts. Also try to limit the use of emojis. For example, ⚙ (Gear Emoji, U+2699) that's used by Powerlevel9k as a "compatible" (a.k.a. portable) glyph is missing from many modern terminal fonts.
@Thutm There are several additional options in p10k for pyenv. This might work for you:
POWERLEVEL9K_PYENV_SOURCES=(shell local)
POWERLEVEL9K_PYENV_PROMPT_ALWAYS_SHOW=true
POWERLEVEL9K_PYENV_SHOW_SYSTEM=trueThis will display the output of pyenv version-name if and only if there is .python-version in the current directory or above, or PYENV_VERSION is set.
