Skip to content
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

Mac OS Sierra support #185

Closed
NicolasRannou opened this issue Aug 9, 2016 · 21 comments
Closed

Mac OS Sierra support #185

NicolasRannou opened this issue Aug 9, 2016 · 21 comments

Comments

@NicolasRannou
Copy link

Does it work on MacOS Sierra?

It is the first time I try powerline and I do not know if I didn't install it properly or if it is a macOS Sierra issue:

screen shot 2016-08-09 at 1 06 39 pm

screen shot 2016-08-09 at 1 06 52 pm

@NicolasRannou
Copy link
Author

We need to set the terminal font to a powerline font.
screen shot 2016-08-09 at 1 16 53 pm

@landsman
Copy link

landsman commented Feb 26, 2017

Oh, thanks for it!
Can you add this to README?
I think That we are not only idiots sole Who will think about this.

@artipfw
Copy link

artipfw commented Mar 3, 2017

any solution?

@jjalonso
Copy link

not working here

@DevAtCN
Copy link

DevAtCN commented Apr 13, 2017

Got same issue here. Just change the font to Droid Sans Mono Awesome and it's working fine.

@daftskunk
Copy link

SarkarSubjhajit's answer worked fine for me! Everyother font from Powerline didn't work.

@jbanulso
Copy link

If this problem appears you should check the option "Use a different font for non-ASCII text", and select a font that works - i.e. any of the Meslo (not Menlo) family.

@ghosty141
Copy link

screen shot 2017-07-17 at 19 08 42

@jbanulso Somehow doesn't work for me. It seems like my terminal is cursed...

@jbanulso
Copy link

@ghosty141 hmm interesting... Have you checked the last part in the README? It says the following:

In some distributions, Terminess Powerline is ignored by default and must be explicitly allowed. A fontconfig file is provided which enables it. Copy this file from the fontconfig directory to your home folder under ~/.config/fontconfig/conf.d (create it if it doesn't exist) and re-run fc-cache -vf.

Maybe that can end the curse :)

@ghosty141
Copy link

@jbanulso I forgot the most important thing when things don't work: Did you try turning it off and on again? It was fixed after a restart, kinda weird since on my hackintosh it worked right away. Anyway, thanks for the help!

@sergioviniciuss
Copy link

After upgrading to high sierra the icons stopped working for me, so the solution I found was to follow the steps provided in here: https://github.com/gabrielelana/awesome-terminal-fonts/wiki/OS-X

I hope it helps if someone else is still having this issue.

@bobby-walle
Copy link

@NicolasRannou word for me.thank you!

@bjoseg
Copy link

bjoseg commented Feb 11, 2018

@SarkarSubhajit works for me! thanks!!

@polpenaloza
Copy link

If you have a pre-determined window arrangement, you will need to re-arrange it again.

TL;DR: create a new arrangement.

@zuxfoucault
Copy link

Do the powerline symbols include in each "font for powerline"? Or I have to download PowerlineSymbols independently?

@testacode
Copy link

Couldn't install them, I won't disable any security on my system to install a font. Isn't there any other solution appart from not using the theme on zsh?

@yairEO
Copy link

yairEO commented May 27, 2019

MacOS won't let me click the button for changing font. clicking does nothing :/

@mandarvaze
Copy link

FWIW, Latest version of iTerm2 (Build 3.3.0beta12) has a setting "Use built-in Powerline Glyphs" (I'm on macOS mojave) - Worked for me.

@raubin
Copy link

raubin commented Aug 20, 2019

@mandarvaze - On 3.3.2 this checkbox is there as well and it worked perfectly. Thank you!

@vjosullivan
Copy link

The iTerm2 now supports Powerline glyphs natively. No need to install any fonts.
iTerm2 > Preferences > Profiles > Text > Use built-in Powerline glyphs

@mikeseal
Copy link

@jbanulso I forgot the most important thing when things don't work: Did you try turning it off and on again? It was fixed after a restart, kinda weird since on my hackintosh it worked right away. Anyway, thanks for the help!

Yep, spent a hour messing around and after trawling a few site I find a reboot is required. I went into a cold sweat as I thought we were back in MS Windows land.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests