Open laksh95 opened 7 years ago
same issue here.
See this thread: https://github.com/powerline/fonts/issues/
Does switching to DejaVu Sans Mono for Powerline
work?
No switching to DejaVu is also not working.
I'm on High Sierra also. I'm not using iTerm2, but the built in terminal for MacOS. So I would recommend trying to see if it works. It would help confirm the fonts are working across systems.
I've also installed iTerm2. I've used a couple of the Powerline fonts. (When picking a font you can search for powerline to see them all). They do work on the second window I've opened. Do the characters show up when you open iTerm2 in a new window or tab?
I was having a similar issue, where the icons were not displaying after I update to High Sierra.
I had to redo the steps in here: https://github.com/gabrielelana/awesome-terminal-fonts/wiki/OS-X now it's working like a charm! :D
It works well on macOS 10.12, the icons are broken after update to High Sierra, as @sergioviniciuss said, you need to reset some font settings https://github.com/gabrielelana/awesome-terminal-fonts/wiki/OS-X. Furthermore, I used SourceCodePro+Powerline+Awesome Regular, you could find here https://github.com/gabrielelana/awesome-terminal-fonts/tree/patching-strategy/patched
FYI I got it to work properly in iTerm 3.2.8 after setting "Use ligatures". Otherwise the "arrows" would still not display despite all other non-ascii characters being correct.
On iterm 3.3.3 got powerline to work by selecting Use built-in Powerline glyphs
If you're running into this issue after upgrading to macOS Catalina, update the permissions on your sudo chmod 775 ~/Library/Fonts/*/. That's what finally fixed this for me.
Hi, I updated folder ~/Library/Fonts and continue the error. Someone to help?
@laksh95 @luizromariofilho any chance you’re using the powerlevel10k theme but didn’t run the p10k configure
script? I had the same issue and nothing worked for me until I found out I hadn’t run it yet.
Hi, I resolved following this tutorial. https://gist.github.com/kevin-smets/8568070
Hi all, I was having a similar issue attempting to use Cobalt2. It all came together when I switched my previously randomly created profile to the default one and it all shows now. Screenshot below for reference:
Worked like charm! iTerm helps a lot in these matters!
On iterm 3.3.3 got powerline to work by selecting Use built-in Powerline glyphs
That worked for me, tks!
FIXED! I had to switch my ZSH_THEME to something other than powerlevel10K, quick iTerm2. Relaunch and switch back to powserlevel10k at which time it asked me to install MesloLGS NF font. Once the new font was installed I restarted iTerm2 once more and the issue was solved. Your .zshrc file is located here for mac ~/
Apparently if you are already using Powerlevel10k, you can manually trigger the config by typing: p10k configure And one of the first questions is to install/update the MesloLGS NF font. Install and update the font and relaunch iTerm and the problem should be resolved.
If for some reason you are unable to launch the configuration mentioned above, you may not have the Powerlevel10k theme installed, in which case you can grab from here: https://github.com/romkatv/powerlevel10k
It's by far my favorite zsh theme!
The thing that worked for me was to configuring powerlevel10k by using the command "p10k configure" and downloading the fonts all over again.
I have setup on-my-zsh, iterm2 and recently I decided to install powerlevel9k theme. Previously it was agnoster. So I cloned the powerlevel9k theme from github and edited the ~/.zshrc file to select it. I previously had installed powerline/fonts and they were working with agnoster. But now they aren't working. I updated oh-my-zsh and re-installed powerline/fonts. I am not a professional but I would really appreciate if somebody could walk me through this process to rectify this issue.
UPDATE: So I setup iterm2, oh-my-zsh on 2012 MBP running MacOS Sierra. I installed pwerlvel9k theme and it worked like a charm. I didn't have to do anything extra. I just followed the instructions and it worked. Any idea why is not working for me? I am running 2017 MBP MacOS High Sierra.