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

A few invalid symbols in 'agnoster.zsh-theme' #1906

Closed
hitigon opened this Issue Jun 24, 2013 · 105 comments

Comments

Projects
None yet
@hitigon

hitigon commented Jun 24, 2013

Like line 29. Please fix it. Thank you.

@wombat2k

This comment has been minimized.

Show comment
Hide comment
@wombat2k

wombat2k Jun 24, 2013

Just to be clear, this is what it now looks like in iTerm 2:

screen shot 2013-06-24 at 2 05 44 pm

I suppose it could be normal, but it seems like an odd choice

wombat2k commented Jun 24, 2013

Just to be clear, this is what it now looks like in iTerm 2:

screen shot 2013-06-24 at 2 05 44 pm

I suppose it could be normal, but it seems like an odd choice

@stianeikeland

This comment has been minimized.

Show comment
Hide comment
@stianeikeland

stianeikeland Jun 24, 2013

Commit 97849bd seems to be the cause, reverting agnoster.theme to d6a36b1 fixes it for me.

It looks like they have updated the font upstream. A bit annoying, but hopefully grabbing a updated powerline font will fix it.

stianeikeland commented Jun 24, 2013

Commit 97849bd seems to be the cause, reverting agnoster.theme to d6a36b1 fixes it for me.

It looks like they have updated the font upstream. A bit annoying, but hopefully grabbing a updated powerline font will fix it.

@hitigon

This comment has been minimized.

Show comment
Hide comment
@hitigon

hitigon Jun 24, 2013

@wombat2k Thanks
@stianeikeland You are right. I just replaced the symbol on line 29 with the old one, but others are ignored since I do not use hg.

hitigon commented Jun 24, 2013

@wombat2k Thanks
@stianeikeland You are right. I just replaced the symbol on line 29 with the old one, but others are ignored since I do not use hg.

@damianball

This comment has been minimized.

Show comment
Hide comment
@damianball

damianball Jun 25, 2013

I am also seeing this issue. Reverting to d6a36b1 fixes it for me as well. I guess I'll look for an updated powerline font as @stianeikeland suggests... or build one.

Update: I just noticed there are still issues in vim

iTerm2: Build 1.0.0.20130622
Mac OS X: 10.8.4 Build 12E55

screen shot 2013-06-24 at 6 45 48 pm

damianball commented Jun 25, 2013

I am also seeing this issue. Reverting to d6a36b1 fixes it for me as well. I guess I'll look for an updated powerline font as @stianeikeland suggests... or build one.

Update: I just noticed there are still issues in vim

iTerm2: Build 1.0.0.20130622
Mac OS X: 10.8.4 Build 12E55

screen shot 2013-06-24 at 6 45 48 pm

@it-ony

This comment has been minimized.

Show comment
Hide comment
@it-ony

it-ony Jun 25, 2013

Works for me as well. Thanks

cd ~/.oh-my-zsh/themes/
git checkout  d6a36b1 agnoster.zsh-theme

it-ony commented Jun 25, 2013

Works for me as well. Thanks

cd ~/.oh-my-zsh/themes/
git checkout  d6a36b1 agnoster.zsh-theme
@jmatcuk

This comment has been minimized.

Show comment
Hide comment
@jmatcuk

jmatcuk Jun 25, 2013

I had the same issue with the fonts and simply edited the theme to re-insert the special characters. Is there a new Powerline font that resolves this issue?

jmatcuk commented Jun 25, 2013

I had the same issue with the fonts and simply edited the theme to re-insert the special characters. Is there a new Powerline font that resolves this issue?

@mariofink

This comment has been minimized.

Show comment
Hide comment
@mariofink

mariofink Jun 26, 2013

Thanks @it-ony. Works perfectly as a short-time fix.

mariofink commented Jun 26, 2013

Thanks @it-ony. Works perfectly as a short-time fix.

@stianeikeland

This comment has been minimized.

Show comment
Hide comment
@stianeikeland

stianeikeland Jun 26, 2013

I tried the newest readily made fonts from https://github.com/Lokaltog/powerline-fonts , but no dice.
Anyone tried to patching fonts themselves using https://github.com/Lokaltog/powerline ?

stianeikeland commented Jun 26, 2013

I tried the newest readily made fonts from https://github.com/Lokaltog/powerline-fonts , but no dice.
Anyone tried to patching fonts themselves using https://github.com/Lokaltog/powerline ?

@schickling

This comment has been minimized.

Show comment
Hide comment
@schickling

schickling commented Jun 26, 2013

Same here

@chrw

This comment has been minimized.

Show comment
Hide comment
@chrw

chrw Jun 26, 2013

Contributor

Same issue here. Reverting to d6a36b1 fixed the problem for now.

Contributor

chrw commented Jun 26, 2013

Same issue here. Reverting to d6a36b1 fixed the problem for now.

@wildjcrt

This comment has been minimized.

Show comment
Hide comment
@wildjcrt

wildjcrt Jun 28, 2013

Met this after upgraded. Thanks @it-ony

wildjcrt commented Jun 28, 2013

Met this after upgraded. Thanks @it-ony

@stianeikeland

This comment has been minimized.

Show comment
Hide comment
@stianeikeland

stianeikeland Jun 28, 2013

Maybe @gdetrez ( 97849bd ) can help us shed some light on this?

stianeikeland commented Jun 28, 2013

Maybe @gdetrez ( 97849bd ) can help us shed some light on this?

@gdetrez

This comment has been minimized.

Show comment
Hide comment
@gdetrez

gdetrez Jun 28, 2013

Contributor

Hi, sorry for the inconvenience 😕

I checked the fonts at https://github.com/Lokaltog/powerline-fonts and they should work with the new characters.
Apparently, if you are using iTerm, you need to set the patched font as both the 'Regular Font' and the 'Non-ASCII Font' and maybe clear your font cache. See #1872 (comment)

Contributor

gdetrez commented Jun 28, 2013

Hi, sorry for the inconvenience 😕

I checked the fonts at https://github.com/Lokaltog/powerline-fonts and they should work with the new characters.
Apparently, if you are using iTerm, you need to set the patched font as both the 'Regular Font' and the 'Non-ASCII Font' and maybe clear your font cache. See #1872 (comment)

@stianeikeland

This comment has been minimized.

Show comment
Hide comment
@stianeikeland

stianeikeland Jun 28, 2013

Thank you for the pointers :)
I was able to make it work with the new font here now following the steps in #1872, but also had to do a full reboot before it rendered the powerline symbols for some strange reason.

  1. quit iterm
  2. deleted all powerline fonts
  3. cleared font cache: sudo atsutil databases -remove
  4. added new font
  5. reboot

stianeikeland commented Jun 28, 2013

Thank you for the pointers :)
I was able to make it work with the new font here now following the steps in #1872, but also had to do a full reboot before it rendered the powerline symbols for some strange reason.

  1. quit iterm
  2. deleted all powerline fonts
  3. cleared font cache: sudo atsutil databases -remove
  4. added new font
  5. reboot
@chrw

This comment has been minimized.

Show comment
Hide comment
@chrw

chrw Jun 28, 2013

Contributor

"DejaVu Sans Mono for Powerline" from https://github.com/Lokaltog/powerline-fonts worked for me! Thanks!
I'm using Ubuntu Linux 12.04 with GNOME Terminal.

EDIT: On my Mac using iTerm I used the "Menlo Regular for Powerline" font from the same repository. Worked too. Thanks.

Contributor

chrw commented Jun 28, 2013

"DejaVu Sans Mono for Powerline" from https://github.com/Lokaltog/powerline-fonts worked for me! Thanks!
I'm using Ubuntu Linux 12.04 with GNOME Terminal.

EDIT: On my Mac using iTerm I used the "Menlo Regular for Powerline" font from the same repository. Worked too. Thanks.

@wwwdata

This comment has been minimized.

Show comment
Hide comment
@wwwdata

wwwdata Jun 28, 2013

installing a new font worked for me fine. Used the same as @christianwolff

wwwdata commented Jun 28, 2013

installing a new font worked for me fine. Used the same as @christianwolff

@ArtFeel

This comment has been minimized.

Show comment
Hide comment
@ArtFeel

ArtFeel Jun 30, 2013

New «Menlo Regular for Powerline» from https://github.com/Lokaltog/powerline-fonts works good, but not so perfect as old font. Looks like symbols height become greater than height of the line.

ArtFeel commented Jun 30, 2013

New «Menlo Regular for Powerline» from https://github.com/Lokaltog/powerline-fonts works good, but not so perfect as old font. Looks like symbols height become greater than height of the line.

@adben

This comment has been minimized.

Show comment
Hide comment
@adben

adben Jun 30, 2013

Contributor

This issue is a bit annoying, already tried the steps at #1872 and rebooting as @stianeikeland suggested, this is the result with the new version of menlo;
schermafbeelding 2013-07-01 om 01 35 22

There is something else I can try before reverting to d6a36b1 ?

Contributor

adben commented Jun 30, 2013

This issue is a bit annoying, already tried the steps at #1872 and rebooting as @stianeikeland suggested, this is the result with the new version of menlo;
schermafbeelding 2013-07-01 om 01 35 22

There is something else I can try before reverting to d6a36b1 ?

@adben

This comment has been minimized.

Show comment
Hide comment
@adben

adben Jul 1, 2013

Contributor

@ArtFeel if you are using iTerm2 (Build 1.0.0.20130624) the configuration for the symbols is taken from your 'Non-ascii Font' configuration, try matching that configuration(size) with the one declared on the 'Regular Font'

Contributor

adben commented Jul 1, 2013

@ArtFeel if you are using iTerm2 (Build 1.0.0.20130624) the configuration for the symbols is taken from your 'Non-ascii Font' configuration, try matching that configuration(size) with the one declared on the 'Regular Font'

@ArtFeel

This comment has been minimized.

Show comment
Hide comment
@ArtFeel

ArtFeel Jul 1, 2013

@adben no, i'm using Terminal.app

ArtFeel commented Jul 1, 2013

@adben no, i'm using Terminal.app

@rixx

This comment has been minimized.

Show comment
Hide comment
@rixx

rixx Jul 1, 2013

I upgraded today, had the same issue and fixed it by updating the agnoster theme file to this version: https://gist.github.com/agnoster/3712874

Restarted zsh and everything was fine again.

rixx commented Jul 1, 2013

I upgraded today, had the same issue and fixed it by updating the agnoster theme file to this version: https://gist.github.com/agnoster/3712874

Restarted zsh and everything was fine again.

@sbirksted

This comment has been minimized.

Show comment
Hide comment
@sbirksted

sbirksted Jul 10, 2013

Rixx's fixx worked like a charm.

sbirksted commented Jul 10, 2013

Rixx's fixx worked like a charm.

@hasanIqbalAnik

This comment has been minimized.

Show comment
Hide comment
@hasanIqbalAnik

hasanIqbalAnik Jul 31, 2013

it-ony 's command worked for me.

hasanIqbalAnik commented Jul 31, 2013

it-ony 's command worked for me.

@jdan

This comment has been minimized.

Show comment
Hide comment
@jdan

jdan Oct 9, 2013

Thank you @gdetrez! Been pulling my hair out for the last hour - turns out I still had Monaco selected as a Non-ASCII font.

jdan commented Oct 9, 2013

Thank you @gdetrez! Been pulling my hair out for the last hour - turns out I still had Monaco selected as a Non-ASCII font.

@miro

This comment has been minimized.

Show comment
Hide comment
@miro

miro Dec 8, 2013

With the instructions provided on oh-my-zsh theme page to the agnoster-theme this is still an issue. Reverted to the d6a36b1 -version and it works.

miro commented Dec 8, 2013

With the instructions provided on oh-my-zsh theme page to the agnoster-theme this is still an issue. Reverted to the d6a36b1 -version and it works.

@dnath

This comment has been minimized.

Show comment
Hide comment
@dnath

dnath Dec 19, 2013

Same here ... reverting to d6a36b1 works like a charm.

dnath commented Dec 19, 2013

Same here ... reverting to d6a36b1 works like a charm.

@mrbfrank

This comment has been minimized.

Show comment
Hide comment
@mrbfrank

mrbfrank Jan 28, 2014

Contributor

I updated the config to this version, works great:
https://gist.github.com/agnoster/3712874#file-agnoster-zsh-theme

Contributor

mrbfrank commented Jan 28, 2014

I updated the config to this version, works great:
https://gist.github.com/agnoster/3712874#file-agnoster-zsh-theme

@pierreozoux

This comment has been minimized.

Show comment
Hide comment
@pierreozoux

pierreozoux Jan 28, 2014

Hi, what is the point of the situation?

I would like to update oh-my-sh, but with this "workaround", I can't.

Should we make a pull request? Or anyone has an idea to make this working without workaround?

pierreozoux commented Jan 28, 2014

Hi, what is the point of the situation?

I would like to update oh-my-sh, but with this "workaround", I can't.

Should we make a pull request? Or anyone has an idea to make this working without workaround?

@mrbfrank

This comment has been minimized.

Show comment
Hide comment
@mrbfrank

mrbfrank Jan 28, 2014

Contributor

I created a pull request: #2476
Rather than copying the config from agnoster's Gist, I simply corrected the SEGMENT_SEPARATOR character in our latest version. If you see any other invalid characters please notify, thanks.

Contributor

mrbfrank commented Jan 28, 2014

I created a pull request: #2476
Rather than copying the config from agnoster's Gist, I simply corrected the SEGMENT_SEPARATOR character in our latest version. If you see any other invalid characters please notify, thanks.

@mrbfrank

This comment has been minimized.

Show comment
Hide comment
@mrbfrank

mrbfrank Jan 28, 2014

Contributor

Hmm.. actually I am wrong to create this pull request, although it may fix for us on OSX using patched fonts it does not comply with the latest standards for powerline. I would hate to break this for other users using a correctly patched font, read the comments here: 97849bd

Contributor

mrbfrank commented Jan 28, 2014

Hmm.. actually I am wrong to create this pull request, although it may fix for us on OSX using patched fonts it does not comply with the latest standards for powerline. I would hate to break this for other users using a correctly patched font, read the comments here: 97849bd

@mrbfrank

This comment has been minimized.

Show comment
Hide comment
@mrbfrank

mrbfrank Jan 28, 2014

Contributor

OK I solved this on OSX. Just use one of the latest patched fonts: https://github.com/Lokaltog/powerline-fonts. I will update the URL in the theme comments to avoid future confusion, it was pointing to older powerline patched fonts that are deprecated as of this change: powerline/powerline@53fbfe1 which is described here: powerline/powerline#4. Also found the branch character needed to be updated in the theme config.

Contributor

mrbfrank commented Jan 28, 2014

OK I solved this on OSX. Just use one of the latest patched fonts: https://github.com/Lokaltog/powerline-fonts. I will update the URL in the theme comments to avoid future confusion, it was pointing to older powerline patched fonts that are deprecated as of this change: powerline/powerline@53fbfe1 which is described here: powerline/powerline#4. Also found the branch character needed to be updated in the theme config.

@mrbfrank

This comment has been minimized.

Show comment
Hide comment
@mrbfrank

mrbfrank Jan 29, 2014

Contributor

There are more improvements to be made, for instance see this comment: ef8e3a6#commitcomment-3076424, Also the '±' or '●' character does not appear for unstaged changes. I would like to see this theme cleaned up to match agnoster's original design & retain all contributed functionality.

Contributor

mrbfrank commented Jan 29, 2014

There are more improvements to be made, for instance see this comment: ef8e3a6#commitcomment-3076424, Also the '±' or '●' character does not appear for unstaged changes. I would like to see this theme cleaned up to match agnoster's original design & retain all contributed functionality.

@mrbfrank

This comment has been minimized.

Show comment
Hide comment
@mrbfrank

mrbfrank Jan 29, 2014

Contributor

Fixed ef8e3a6#commitcomment-3076424 in my latest commit. This is what it looks like now:
screen shot 2014-01-29 at 6 35 39 pm

Contributor

mrbfrank commented Jan 29, 2014

Fixed ef8e3a6#commitcomment-3076424 in my latest commit. This is what it looks like now:
screen shot 2014-01-29 at 6 35 39 pm

@pierreozoux

This comment has been minimized.

Show comment
Hide comment
@pierreozoux

pierreozoux Mar 5, 2014

@hitigon, can you confirm that #2479 solve the issue for you also. If it does, please close this one (as the other will be merged).

pierreozoux commented Mar 5, 2014

@hitigon, can you confirm that #2479 solve the issue for you also. If it does, please close this one (as the other will be merged).

@hitigon hitigon closed this Mar 6, 2014

@mrbfrank

This comment has been minimized.

Show comment
Hide comment
@mrbfrank

mrbfrank Mar 6, 2014

Contributor

@pierreozoux thanks for moving this forward. Does this mean the pull request is approved for merge?

Contributor

mrbfrank commented Mar 6, 2014

@pierreozoux thanks for moving this forward. Does this mean the pull request is approved for merge?

@pierreozoux

This comment has been minimized.

Show comment
Hide comment
@pierreozoux

pierreozoux Mar 7, 2014

@mrbfrank This is the pull request : #2479
It is not yet merged.

pierreozoux commented Mar 7, 2014

@mrbfrank This is the pull request : #2479
It is not yet merged.

@chucklor

This comment has been minimized.

Show comment
Hide comment
@chucklor

chucklor Sep 27, 2016

I have tried double click and FontBook to install the fonts. And yes, I'v unchecked the "Use different font for non-ASCII" box.

chucklor commented Sep 27, 2016

I have tried double click and FontBook to install the fonts. And yes, I'v unchecked the "Use different font for non-ASCII" box.

@ChavaSobreyra

This comment has been minimized.

Show comment
Hide comment
@ChavaSobreyra

ChavaSobreyra Sep 28, 2016

@chucklor It seems the font still isn't selected/applied correctly. Which powerline font are you using? Maybe provide a screenshot of your ITerm2 -> Preferences -> Profiles -> Text options?

Other suggestions:

ChavaSobreyra commented Sep 28, 2016

@chucklor It seems the font still isn't selected/applied correctly. Which powerline font are you using? Maybe provide a screenshot of your ITerm2 -> Preferences -> Profiles -> Text options?

Other suggestions:

@chucklor

This comment has been minimized.

Show comment
Hide comment
@chucklor

chucklor Sep 28, 2016

Here's my screen shot.
screen shot 2016-09-28 at 11 39 48 am

chucklor commented Sep 28, 2016

Here's my screen shot.
screen shot 2016-09-28 at 11 39 48 am

@chucklor

This comment has been minimized.

Show comment
Hide comment
@chucklor

chucklor Oct 5, 2016

Any suggestion?

chucklor commented Oct 5, 2016

Any suggestion?

@wwwdata

This comment has been minimized.

Show comment
Hide comment
@wwwdata

wwwdata Oct 5, 2016

I had this problem as well. I think a year ago I had to upgrade to a new powerline font. How up to date are your fonts? As already mentioned look into the repo that was linked.

I reinstalled my mac last week and everything is working with the newest Hack font. Maybe try that font and if it works for you it must be an outdated powerline font on your computer. http://sourcefoundry.org/hack/

wwwdata commented Oct 5, 2016

I had this problem as well. I think a year ago I had to upgrade to a new powerline font. How up to date are your fonts? As already mentioned look into the repo that was linked.

I reinstalled my mac last week and everything is working with the newest Hack font. Maybe try that font and if it works for you it must be an outdated powerline font on your computer. http://sourcefoundry.org/hack/

@kode54

This comment has been minimized.

Show comment
Hide comment
@kode54

kode54 Oct 8, 2016

Was a reboot or log out and log in cycle mandatory after installing the fonts? I just installed the latest Powerline fonts repository, which I notice no longer includes Menlo for Powerline, I assume because of copyright concerns. And those two characters are both still missing character blocks, even after manually cycling through the various fonts.

kode54 commented Oct 8, 2016

Was a reboot or log out and log in cycle mandatory after installing the fonts? I just installed the latest Powerline fonts repository, which I notice no longer includes Menlo for Powerline, I assume because of copyright concerns. And those two characters are both still missing character blocks, even after manually cycling through the various fonts.

@kode54

This comment has been minimized.

Show comment
Hide comment
@kode54

kode54 Oct 8, 2016

Found the problem: The Wiki for Themes still links to:

https://github.com/powerline/fonts

Which seems to have pre-2012 mapping fonts, at least when I just git cloned it.

https://github.com/Lokaltog/powerline-fonts, however, works.

kode54 commented Oct 8, 2016

Found the problem: The Wiki for Themes still links to:

https://github.com/powerline/fonts

Which seems to have pre-2012 mapping fonts, at least when I just git cloned it.

https://github.com/Lokaltog/powerline-fonts, however, works.

@mcornella

This comment has been minimized.

Show comment
Hide comment
@mcornella

mcornella Oct 8, 2016

Collaborator

@kode54 Lokaltog/powerline-fonts redirects to powerline/fonts. If you're trying to use Menlo just use Meslo which is open source.

Collaborator

mcornella commented Oct 8, 2016

@kode54 Lokaltog/powerline-fonts redirects to powerline/fonts. If you're trying to use Menlo just use Meslo which is open source.

@lpredova

This comment has been minimized.

Show comment
Hide comment
@lpredova

lpredova Oct 8, 2016

Just had this issue, installing this:
https://github.com/powerline/fonts

with this font in iTerm2 settings
image

and unchecking option

image

Made it work . Cheers.

lpredova commented Oct 8, 2016

Just had this issue, installing this:
https://github.com/powerline/fonts

with this font in iTerm2 settings
image

and unchecking option

image

Made it work . Cheers.

@chrishough

This comment has been minimized.

Show comment
Hide comment
@chrishough

chrishough Nov 13, 2016

A strong recommendation I have to get around this is move to https://github.com/tonsky/FiraCode

chrishough commented Nov 13, 2016

A strong recommendation I have to get around this is move to https://github.com/tonsky/FiraCode

@schmunk42

This comment has been minimized.

Show comment
Hide comment
@schmunk42

schmunk42 Dec 8, 2016

I had the wrong encoding here ...

bildschirmfoto 2016-12-08 um 14 37 59

Maybe it helps someone else with a similar issue, I had i.e. no broken fonts or whatever. Can't remember if I did change that accidentally or it was due to an update.

schmunk42 commented Dec 8, 2016

I had the wrong encoding here ...

bildschirmfoto 2016-12-08 um 14 37 59

Maybe it helps someone else with a similar issue, I had i.e. no broken fonts or whatever. Can't remember if I did change that accidentally or it was due to an update.

@kevinquillen

This comment has been minimized.

Show comment
Hide comment
@kevinquillen

kevinquillen Dec 10, 2016

lpredova's suggestion worked for me.

kevinquillen commented Dec 10, 2016

lpredova's suggestion worked for me.

@fleed

This comment has been minimized.

Show comment
Hide comment
@fleed

fleed Jan 11, 2017

The there is working well for me in iTerm2, but I'm having issues with terminal. Any suggestion to fix it terminal too?

terminal_issue

fleed commented Jan 11, 2017

The there is working well for me in iTerm2, but I'm having issues with terminal. Any suggestion to fix it terminal too?

terminal_issue

@mlopezcoria

This comment has been minimized.

Show comment
Hide comment
@mlopezcoria

mlopezcoria Jan 23, 2017

I've got the same issue on Linux mint 18. I'm using Gnome Terminal and I've installed PowerLine Fonts from here https://github.com/powerline/fonts

powerline_issue

Oh, sorry. I had to change the font. It worked with Ubuntu Mono derivative Powerline Regular font.

mlopezcoria commented Jan 23, 2017

I've got the same issue on Linux mint 18. I'm using Gnome Terminal and I've installed PowerLine Fonts from here https://github.com/powerline/fonts

powerline_issue

Oh, sorry. I had to change the font. It worked with Ubuntu Mono derivative Powerline Regular font.

@pradeepchaudharisc

This comment has been minimized.

Show comment
Hide comment
@pradeepchaudharisc

pradeepchaudharisc Jan 27, 2017

It's 2017 and I still see the same issue. I think we should open this and fix it right.

--> Fix, If you land here again, Steps to Fix

  1. git clone https://github.com/powerline/fonts
  2. cd fonts
  3. ./install.sh from terminal / command line
  4. Open iTerm2->Preferences->Profiles->Change Font-> 12pt Meslo LG S DZ Regular for Powerline

pradeepchaudharisc commented Jan 27, 2017

It's 2017 and I still see the same issue. I think we should open this and fix it right.

--> Fix, If you land here again, Steps to Fix

  1. git clone https://github.com/powerline/fonts
  2. cd fonts
  3. ./install.sh from terminal / command line
  4. Open iTerm2->Preferences->Profiles->Change Font-> 12pt Meslo LG S DZ Regular for Powerline
@djsd123

This comment has been minimized.

Show comment
Hide comment
@djsd123

djsd123 Jan 27, 2017

@pradeepchaudharisc Or at least add some steps to the README.md 👍

djsd123 commented Jan 27, 2017

@pradeepchaudharisc Or at least add some steps to the README.md 👍

@pradeepchaudharisc

This comment has been minimized.

Show comment
Hide comment
@pradeepchaudharisc

pradeepchaudharisc Jan 27, 2017

@djsd123 I will send pull request soon 👯‍♂️

pradeepchaudharisc commented Jan 27, 2017

@djsd123 I will send pull request soon 👯‍♂️

pradeephrish added a commit to pradeephrish/oh-my-zsh that referenced this issue Jan 27, 2017

Update README.MD to fix invalid characters issue
A few invalid symbols in 'agnoster.zsh-theme' :
robbyrussell#1906 (comment)

this issue got introduced in 2013 and people are still confused and don't know right way to fix it.
It would be awesome if we can put this in README.md

Thanks & Regards,
Pradeep
@juandiego26

This comment has been minimized.

Show comment
Hide comment
@juandiego26

juandiego26 Jun 22, 2017

@DanielGGordon thanks worked for me!!

juandiego26 commented Jun 22, 2017

@DanielGGordon thanks worked for me!!

@ismailhkose

This comment has been minimized.

Show comment
Hide comment
@ismailhkose

ismailhkose Jul 5, 2017

I followed the all instructions at Ubuntu 16.04 for agnoster theme, but they didnt work. I am seeing invalid symbols

image

https://gist.github.com/agnoster/3712874
https://powerline.readthedocs.io/en/latest/installation/linux.html#font-installation
https://github.com/agnoster/agnoster-zsh-theme#agnosterzsh-theme
https://github.com/powerline/fonts instructions.

I installed patched powerline fonts and solarized theme.

Any comment?

ismailhkose commented Jul 5, 2017

I followed the all instructions at Ubuntu 16.04 for agnoster theme, but they didnt work. I am seeing invalid symbols

image

https://gist.github.com/agnoster/3712874
https://powerline.readthedocs.io/en/latest/installation/linux.html#font-installation
https://github.com/agnoster/agnoster-zsh-theme#agnosterzsh-theme
https://github.com/powerline/fonts instructions.

I installed patched powerline fonts and solarized theme.

Any comment?

@ismailhkose

This comment has been minimized.

Show comment
Hide comment
@ismailhkose

ismailhkose Jul 5, 2017

echo "\ue0b0 \u00b1 \ue0a0 \u27a6 \u2718 \u26a1 \u2699"

image

I dont not see all character in the following picture
https://gist.githubusercontent.com/agnoster/3712874/raw/characters.png
image

ismailhkose commented Jul 5, 2017

echo "\ue0b0 \u00b1 \ue0a0 \u27a6 \u2718 \u26a1 \u2699"

image

I dont not see all character in the following picture
https://gist.githubusercontent.com/agnoster/3712874/raw/characters.png
image

@ismailhkose

This comment has been minimized.

Show comment
Hide comment
@ismailhkose

ismailhkose Jul 6, 2017

I noticed that It was cygwin displaying issue. It was working in Ubuntu.
When I install powerline fonts to Windows, the problem was solved.

ismailhkose commented Jul 6, 2017

I noticed that It was cygwin displaying issue. It was working in Ubuntu.
When I install powerline fonts to Windows, the problem was solved.

huang47 added a commit to huang47/dotfiles that referenced this issue Sep 25, 2017

@primaveraentalca

This comment has been minimized.

Show comment
Hide comment
@primaveraentalca

primaveraentalca Oct 12, 2017

I was having this issue on Debian 9 with rxvt-unicode.
This answer helped me.
I'm using Hack font (fonts-hack-ttf package on debian) on my .Xresources:
URxvt.font: xft:Hack:size=8

primaveraentalca commented Oct 12, 2017

I was having this issue on Debian 9 with rxvt-unicode.
This answer helped me.
I'm using Hack font (fonts-hack-ttf package on debian) on my .Xresources:
URxvt.font: xft:Hack:size=8

@danigosa

This comment has been minimized.

Show comment
Hide comment
@danigosa

danigosa Oct 16, 2017

For those poor bastards like me that had activated iTerm2's options antialised and non-Ascii fonts, appart from using powerline fonts, uncheck them!

danigosa commented Oct 16, 2017

For those poor bastards like me that had activated iTerm2's options antialised and non-Ascii fonts, appart from using powerline fonts, uncheck them!

@willguxy

This comment has been minimized.

Show comment
Hide comment
@willguxy

willguxy Nov 2, 2017

(re)installing powerline fonts and change fonts in profile worked for me
https://github.com/powerline/fonts

willguxy commented Nov 2, 2017

(re)installing powerline fonts and change fonts in profile worked for me
https://github.com/powerline/fonts

@djamal-d

This comment has been minimized.

Show comment
Hide comment
@djamal-d

djamal-d Nov 17, 2017

If you are on macOS Sierra/ High Sierra you'll probably need this : http://powerline.readthedocs.io/en/master/installation/osx.html

Thank me later.

djamal-d commented Nov 17, 2017

If you are on macOS Sierra/ High Sierra you'll probably need this : http://powerline.readthedocs.io/en/master/installation/osx.html

Thank me later.

@karstengresch

This comment has been minimized.

Show comment
Hide comment
@karstengresch

karstengresch Nov 24, 2017

lpredovas and - regarding the steps I followed - pradeepchaudharisc worked for me on iTerm2 but
only for new tabs.

I.e. already opened tabs did not change which made me a bit crazy for a while.

karstengresch commented Nov 24, 2017

lpredovas and - regarding the steps I followed - pradeepchaudharisc worked for me on iTerm2 but
only for new tabs.

I.e. already opened tabs did not change which made me a bit crazy for a while.

@erikcaffrey

This comment has been minimized.

Show comment
Hide comment
@erikcaffrey

erikcaffrey Dec 2, 2017

if you are using macOS Sierra/ High Sierra, The problem can be solved installing https://github.com/powerline/fonts, so choose Meslo for Powerline.

erikcaffrey commented Dec 2, 2017

if you are using macOS Sierra/ High Sierra, The problem can be solved installing https://github.com/powerline/fonts, so choose Meslo for Powerline.

@griffincox

This comment has been minimized.

Show comment
Hide comment
@griffincox

griffincox Jan 9, 2018

thanks @erikcaffrey, that did the trick for me.

griffincox commented Jan 9, 2018

thanks @erikcaffrey, that did the trick for me.

@erikcaffrey

This comment has been minimized.

Show comment
Hide comment

erikcaffrey commented Jan 9, 2018

@griffincox great!

@Oliverwong369

This comment has been minimized.

Show comment
Hide comment
@Oliverwong369

Oliverwong369 Jan 31, 2018

iTerm2 users need to set both the Regular font and the Non-ASCII Font in "iTerm > Preferences > Profiles > Text" to use a patched font ( Non-ASCII Font seems to cause the problem )

BTW iTerm2 looks better by binding Zsh with powerline plugin.

Preference:
https://github.com/powerline/fonts
https://powerline.readthedocs.io/en/latest/usage/shell-prompts.html#zsh-prompt

Oliverwong369 commented Jan 31, 2018

iTerm2 users need to set both the Regular font and the Non-ASCII Font in "iTerm > Preferences > Profiles > Text" to use a patched font ( Non-ASCII Font seems to cause the problem )

BTW iTerm2 looks better by binding Zsh with powerline plugin.

Preference:
https://github.com/powerline/fonts
https://powerline.readthedocs.io/en/latest/usage/shell-prompts.html#zsh-prompt

@Javirln

This comment has been minimized.

Show comment
Hide comment
@Javirln

Javirln May 6, 2018

Hello guys, my problem is the following:
screen shot 2018-05-06 at 20 42 20
I cannot get rid of that little arrow at the beginning of the prompt. I have the latest version of agnoster and oh-my-zsh and my profile settings are the following:
screen shot 2018-05-06 at 20 45 36

Javirln commented May 6, 2018

Hello guys, my problem is the following:
screen shot 2018-05-06 at 20 42 20
I cannot get rid of that little arrow at the beginning of the prompt. I have the latest version of agnoster and oh-my-zsh and my profile settings are the following:
screen shot 2018-05-06 at 20 45 36

@euf

This comment has been minimized.

Show comment
Hide comment
@euf

euf Jun 7, 2018

@Javirln Hello, this little arrow is an indicator of the iTerm2 "Shell Integration" feature.

When shell integration is enabled, iTerm2 automatically adds a mark at each command prompt. Marks are indicated visually by a small blue triangle in the left margin.

See https://www.iterm2.com/documentation-shell-integration.html

euf commented Jun 7, 2018

@Javirln Hello, this little arrow is an indicator of the iTerm2 "Shell Integration" feature.

When shell integration is enabled, iTerm2 automatically adds a mark at each command prompt. Marks are indicated visually by a small blue triangle in the left margin.

See https://www.iterm2.com/documentation-shell-integration.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment