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
[Archlinux] No powerline symbols in urxvt with tmux #684
Comments
What terminal are you using? |
Oh, i forgot to provide that information. It is This are the options used for compiling: This is the PKBUILD for urxvt from AUR Archlinux [1], as you can see the [1] https://aur.archlinux.org/packages/rx/rxvt-unicode-patched/PKGBUILD |
It works for me... |
@otommod what patched fonts are you using? same urxvt version? same OS? |
The one you use. I run |
I run it like you said and it is much better now, but there are some signs that I think that aren't recognized: This is what i have in my .Xresources. Can you please post what setting you have in your .Xresources so I can try to set them? |
Well, I don't use urxvt so I don't have anything in my .Xresources file. I also don't get the soft separators (the one's that aren't getting displayed) too. It's that I don't have any segment with soft separators in tmux, so I noticed this just now that I run vim. |
@otommod What terminal emulator are you using? |
I'm using st[1]. It's lightweight, has full xft and fontconfig support, 24bit colors. It lacks a scroll buffer though, so you will have to use tmux or screen for that. |
I failed in setting up |
@nasenatmer I found your thread in my earlier searches. I've tried the xfce-terminal but the result i the same with the one from here. I also find some issues on this project referring to the issue with the powerline on urxvt. I will try to use what @otommod suggested. Thank you for your help. |
Same issue here, except I have three systems with nearly identical Arch configs (installed using a setup script that installs all the same packages and copies in my configs). Only one of the three systems is giving this behavior: the other two work. For the life of me I cannot figure out the difference. I have the same fonts installed, the same URXVT compile and config, etc. |
UPDATE: Solved, at least for me. The difference for me was the failing system did not have a default locale set in /etc/locale.conf. Forcing a UTF8 locale fixed this issue. Those with the same problem should try something like |
Closing this issue for being outdated, at least partially resolved and highly dependent on user configuration. (Marking as INVALID due to the latter: errors in user system configuration are not powerline issues, even though configuration changes are being made for powerline.) |
I'm very sorry for necro'ing this issue, but I'm just leaving this here because this is still high up in the search ranks for this particular problem. It doesn't pertain to Powerline specifically, but it might help out some users none the less. This is not a Powerline issue So, apart from having your locale set properly (an obvious one), most of the Urxvt AUR packages I've come across (specifically In the PKGBUILD under Change
As long as your terminal emulator is compiled without unicode rendering, no amount of configuration will make it display unicode characters. They're being considered 'unnecessary features', but they add negligible overhead to the size of the installed package (~100KB). Hope this helps! Sincerely, a fellow terminal lover |
Thanks @ti-mo, that's the most useful thing to come out of this issue. I've since switched to Termite and am quite happy with it, but just confirmed that does indeed solve that particular URXVT issue on one system that wasn't fixed by just the locale fix. |
Hey @alerque , happy that solved it for you too! Made a PR to add this to the docs, so hopefully it's a thing of the past for good. |
@ti-mo Thanks man, you saved me from wasting another day on trying to get this right in Xterm!!! Definitely owe you a beer ( or 6!) |
I'm on
I'm seeing squares where I should be seeing symbols in my oh-my-zsh line ie. |
@kfrz I'm getting the same issue. unicode3 and frills are enabled but I'm getting rectangles instead of arrows. Arch linux, i3 and urxvt |
I found a solution that worked for me. I just had to install the fonts from here. https://github.com/powerline/fonts |
I am having this same problem. The closest i have come to solving it is that my i3 window manager is launching the applications with its default encoding set to C. Which does not have the powerline symbols. My regular environment is set to utf8. This means that if I launch urxvt from another terminal application and define the font, it will contain the powerline symbols. I am not sure how to change the default encoding for i3 to utf8. |
@kparikh1 Based on what I know i3 has nothing to do with defining locale, it will use whatever locale it was launched with. You need to configure whatever runs i3. |
At least, I am using i3 and I do not have the issue. But I am running that “manually” from |
@hanss314 I can confirm, on Debian Stretch, installing powerline python3-powerline and fonts-powerline only install fallback PowerlineSymbols.otf font. While it is working for some terminals, it does not for urxvt, even compiled with all the needed flags. You have to install at least one of github powerline patched fonts and select it in you ~/.Xresources, ie.: |
I'll post the .Xresources here, https://github.com/Awan/cfg.git or https://gitlab.com/Abdullah/cfg.git |
Hello.
I've installed the powerline under archlinux using the recommended package that it is indicated in the documentation [1].
After the install I've added to my ~/.tmux.conf the fallowing line:
source '/usr/share/tmux/powerline.conf'
The required patched fond are installed from [2] and
fc-list
reports that it is aware of them.I tried restarting X as instructed in to the documentation but the result is the same:
How can I solve this?
Thank you.
[1] https://aur.archlinux.org/packages/python-powerline-git/
[2] https://aur.archlinux.org/packages/ttf-dejavusansmono-powerline-git/
Want to back this issue? Place a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: