-
Notifications
You must be signed in to change notification settings - Fork 514
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
Invalid unicode characters for VPN #437
Comments
Hi there, Actually they are supposed to be like that. At the beginning powerline fonts were required, but for some time now, we're using Nerd Fonts. This is also part of the requirements list in the README.md Requirements Section: Lines 91 to 95 in 717688b
You can use OverrideFor some segments you can override things like symbols and separators, e.g. if you are happy with the overall appearance of your tmux-powerline/segments/vpn.sh Lines 11 to 25 in 717688b
which you should also find in your ~/.config/tmux-powerline/config.sh.default (details on how to (re-)generate the default file are available in the README.md Config-File Section)
|
Ah, that makes sense then. I had just assumed that more would have been broken if I didn't have the fonts installed. Thanks for the help and information! |
In
segments/vpn.sh
, invalid Unicode characters are used for the following env vars:TMUX_POWERLINE_SEG_VPN_SYMBOL=" "
TMUX_POWERLINE_SEG_VPN_DISPLAY_SEPARATOR=""
Apparently the value for
TMUX_POWERLINE_SEG_VPN_SYMBOL
is U+F183E andTMUX_POWERLINE_SEG_VPN_DISPLAY_SEPARATOR
is U+F0FDF which both live in the Unicode "SUPPLEMENTARY_PRIVATE_USE_AREA_A
".It seems that #383 added this VPN functionality and the screenshot in that issue shows properly rendered characters, but I'm assuming that's because they have some additional font pack installed.
I suggest setting the affected environment variables to the following:
TMUX_POWERLINE_SEG_VPN_SYMBOL="🔒"
TMUX_POWERLINE_SEG_VPN_DISPLAY_SEPARATOR="/"
If sounds reasonable, I can create a PR with the changes.
The text was updated successfully, but these errors were encountered: