bash-it prompt themes - wrap-around glitches

[yang]

On Mac, I'm seeing the cursor and input characters overlap with the powerline status display once text exceeds a certain length. It has something to do with the wrap-around, since maximizing the iTerm such that the line doesn't spill does not experience the same problem.

I do not experience these problems when unsetting BASH_IT_THEME and instead setting a custom PS1 that also produces a long-enough line.

[nwinkler]

Looks similar to #1125 to me...

[yang]

Maybe, though I didn't need to resize windows to run into this.

…

On Wed, Jul 18, 2018, 2:52 AM Nils Winkler ***@***.***> wrote: Looks similar to #1125 <#1125> to me... — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1207 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAb2dLNuUUS4AH9_3lemf1yAb1vj4j8ks5uHts3gaJpZM4VBrhU> .

[bulldozier]

The root cause is 2-byte unicode characters, which Powerline uses for spaces and triangles, getting treated as 2 printable characters instead of 1. To fix this, make sure the locale is set to something that supports unicode such as en_US.UTF-8. In particular, the default glibc locale is "C" which predates unicode and does not handle 2-byte unicode characters correctly. See this man page for more info.

[nwinkler]

Thanks - do you have a concrete setting that people could apply, or that we could add to the documentation?

[bulldozier]

Our use model was a bit different since we are running in Docker. Our fix was the following:

In Dockerfile:
-ENV LANG=en_US.UTF-8
+ENV LANG=en_US.utf8
+sed -i 's/UTF-8/utf8/' /etc/yum.conf

Then we ran "locale -a" and "locale" to verify that en_US.utf8 was there. When we used the capital letter form (UTF-8), it was getting set to "C" which caused the bad wrapping.

[yang]

Any tips on how to debug this? I tried again recently, but still is an issue for me for the past few years:

[gaelicWizard]

Any tips on how to debug this? I tried again recently, but still is an issue for me for the past few years:

@yang, LANG should be "en_US.UTF-8". I have no idea on earth why it would ever be set to end with lowercase "utf8" as that's not a valid encoding name anywhere that I'm aware of. The name of the encoding that locale understands is "UTF-8" so end with that.

(There's actually files with those names somewhere under /usr, that need to be matched exactly. Running locale -a will show you all the valid choices on your system; anything not on the list will fail.)

[gaelicWizard]

Any tips on how to debug this? I tried again recently, but still is an issue for me for the past few years:

@yang, LANG should be "en_US.UTF-8". I have no idea on earth why it would ever be set to end with lowercase "utf8" as that's not a valid encoding name anywhere that I'm aware of. The name of the encoding that locale understands is "UTF-8" so end with that.

(There's actually files with those names somewhere under /usr, that need to be matched exactly. Running locale -a will show you all the valid choices on your system; anything not on the list will fail.)

Looking at your screenshot again: if you have any of the $LC_* variables set, then $LANG is ignored. Don't set those without very specific reason.

[yang]

@gaelicWizard Just to clarify, "en_US.UTF-8" is what it was originally - the above screenshot just shows me trying to change it from that to what was mentioned further up this thread (to no avail).

[yang]

The only LC_ env var that's set for me is LC_TERMINAL=iTerm2 (set by iTerm2)

[gaelicWizard]

@yang, could you run these commands and post your results?

set | grep LC_
unset "${!LC_@}"
export LANG="en_US.UTF-8"
locale
LC_CTYPE=UTF-8 locale
type -p locale iconv

You've caught my curiosity, so I'll try to track this down for you! 😃

[bulldozier]

As per https://perlgeek.de/en/article/set-up-a-clean-utf8-environment: Most of the time it works to set all of these to the same value. Instead of setting all LC_ variables separately, you can set the LC_ALL. If you use bash as your shell, you can put these lines in your ~/.bashrc and ~/.profile files: export LC_ALL=en_US.UTF-8 export LANG=en_US.UTF-8 export LANGUAGE=en_US.UTF-8

…

On Wed, Sep 15, 2021 at 10:59 AM Yang Zhang ***@***.***> wrote: The only LC_ env var that's set for me is LC_TERMINAL=iTerm2 (set by iTerm2) — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1207 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABYLY5HO3ZXHMJ2BLJORL7LUCDNJVANCNFSM4FIGXBKA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.