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

hitigon · 2013-06-24T02:28:19Z

Like line 29. Please fix it. Thank you.

wombat2k · 2013-06-24T18:07:39Z

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

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

stianeikeland · 2013-06-24T18:16:02Z

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 · 2013-06-24T23:07:16Z

@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 · 2013-06-25T01:38:37Z

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

it-ony · 2013-06-25T12:21:23Z

Works for me as well. Thanks

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

jmatcuk · 2013-06-25T13:30:07Z

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 · 2013-06-26T05:53:55Z

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

stianeikeland · 2013-06-26T10:54:48Z

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 · 2013-06-26T11:45:40Z

Same here

chrw · 2013-06-26T20:34:29Z

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

wildjcrt · 2013-06-28T02:27:24Z

Met this after upgraded. Thanks @it-ony

stianeikeland · 2013-06-28T07:59:28Z

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

gdetrez · 2013-06-28T08:26:07Z

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 · 2013-06-28T08:44:00Z

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.

quit iterm
deleted all powerline fonts
cleared font cache: sudo atsutil databases -remove
added new font
reboot

chrw · 2013-06-28T11:22:02Z

"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 · 2013-06-28T22:04:09Z

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

ArtFeel · 2013-06-30T18:24:42Z

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 · 2013-06-30T23:41:58Z

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;

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

adben · 2013-07-01T07:19:53Z

@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 · 2013-07-01T07:51:32Z

@adben no, i'm using Terminal.app

rixx · 2013-07-01T08:44:35Z

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 · 2013-07-10T17:15:14Z

Rixx's fixx worked like a charm.

hasanIqbalAnik · 2013-07-31T07:08:31Z

it-ony 's command worked for me.

jdan · 2013-10-09T16:25:54Z

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 · 2013-12-08T21:28:14Z

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 · 2013-12-19T00:33:26Z

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

mrbfrank · 2014-01-28T00:15:38Z

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

pierreozoux · 2014-01-28T18:29:21Z

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 · 2014-01-28T22:45:29Z

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.

pradeepchaudharisc · 2017-01-27T18:13:38Z

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

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

djsd123 · 2017-01-27T23:10:40Z

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

pradeepchaudharisc · 2017-01-27T23:12:25Z

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

A few invalid symbols in 'agnoster.zsh-theme' : ohmyzsh#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 · 2017-06-22T19:49:44Z

@DanielGGordon thanks worked for me!!

ismailhkose · 2017-07-05T23:08:38Z

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

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 · 2017-07-05T23:11:45Z

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

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

ismailhkose · 2017-07-06T19:58:41Z

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

piducancore · 2017-10-12T04:54:19Z

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

danigosa · 2017-10-16T05:54:04Z

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 · 2017-11-02T00:37:22Z

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

ghost · 2017-11-17T15:27:03Z

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 · 2017-11-24T09:46:15Z

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.

erikjhordan-rey · 2017-12-02T02:16:10Z

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 · 2018-01-09T14:41:43Z

thanks @erikcaffrey, that did the trick for me.

erikjhordan-rey · 2018-01-09T16:37:38Z

@griffincox great!

Oliverwong369 · 2018-01-31T09:28:40Z

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 · 2018-05-06T18:45:59Z

Hello guys, my problem is the following:

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:

euf · 2018-06-07T12:06:04Z

@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

Hyped-247 · 2018-11-05T20:51:05Z

Ok, so here is how I solved it.

Make sure to select the power line font that you can get from cloning this. See the first circle in the picture.
And once you change the font, play around with the colors until you get the desired result. See the second circle in the picture.

gaddyya · 2019-02-03T09:37:06Z

https://medium.com/vunamhung/disable-marks-in-iterm2-63f2d7340cb6

GuganVignesh · 2019-02-13T09:28:43Z

For Mac Terminal :

This need the Powerline fonts installed for the Mac, check here : https://github.com/powerline/fonts

Then if you find the colors to be little not suitable you can change in preferences > display > text > ANSI Colors (customise based on your vision)

After installation and customisation do not forget to restart the terminal, so that changes take effect on your terminal

adrianmihalko · 2019-02-15T17:31:39Z

I installed the suggested fins, but it is not working.

ruslanguns · 2019-03-18T15:36:17Z

I fixed it by changing my default font to DejaVu for e.g.

mcornella · 2019-03-25T18:15:07Z

One solution: #1906 (comment)
Summary: install Powerline fonts and set one of the fonts in your terminal emulator. If it doesn't work try another font.

mrbfrank mentioned this issue Jan 28, 2014

bugfix incorrect SEGMENT_SEPARATOR character in agnoster.zsh-theme #2476

Closed

pradeephrish mentioned this issue Jan 27, 2017

Update README.MD to fix invalid characters issue #5822

Closed

surajdevesan mentioned this issue May 24, 2017

character formatting is changed agnoster/agnoster-zsh-theme#38

Closed

This was referenced Aug 19, 2018

powerline special symbol doesn't work correctly for agnoster #6530

Closed

Display abnormally for theme agnoster #6467

Closed

ohmyzsh locked as resolved and limited conversation to collaborators Mar 25, 2019

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

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

Comments

hitigon commented Jun 24, 2013

wombat2k commented Jun 24, 2013

stianeikeland commented Jun 24, 2013

hitigon commented Jun 24, 2013

damianball commented Jun 25, 2013

it-ony commented Jun 25, 2013

jmatcuk commented Jun 25, 2013

mariofink commented Jun 26, 2013

stianeikeland commented Jun 26, 2013

schickling commented Jun 26, 2013

chrw commented Jun 26, 2013

wildjcrt commented Jun 28, 2013

stianeikeland commented Jun 28, 2013

gdetrez commented Jun 28, 2013

stianeikeland commented Jun 28, 2013

chrw commented Jun 28, 2013

wwwdata commented Jun 28, 2013

ArtFeel commented Jun 30, 2013

adben commented Jun 30, 2013

adben commented Jul 1, 2013

ArtFeel commented Jul 1, 2013

rixx commented Jul 1, 2013

sbirksted commented Jul 10, 2013

hasanIqbalAnik commented Jul 31, 2013

jdan commented Oct 9, 2013

miro commented Dec 8, 2013

dnath commented Dec 19, 2013

mrbfrank commented Jan 28, 2014

pierreozoux commented Jan 28, 2014

mrbfrank commented Jan 28, 2014

pradeepchaudharisc commented Jan 27, 2017 • edited Loading

djsd123 commented Jan 27, 2017

pradeepchaudharisc commented Jan 27, 2017

juandiego26 commented Jun 22, 2017

ismailhkose commented Jul 5, 2017 • edited Loading

ismailhkose commented Jul 5, 2017

ismailhkose commented Jul 6, 2017

piducancore commented Oct 12, 2017

danigosa commented Oct 16, 2017

willguxy commented Nov 2, 2017

ghost commented Nov 17, 2017

karstengresch commented Nov 24, 2017

erikjhordan-rey commented Dec 2, 2017

griffincox commented Jan 9, 2018

erikjhordan-rey commented Jan 9, 2018

Oliverwong369 commented Jan 31, 2018

javirln commented May 6, 2018

euf commented Jun 7, 2018

Hyped-247 commented Nov 5, 2018

gaddyya commented Feb 3, 2019

GuganVignesh commented Feb 13, 2019 • edited Loading

adrianmihalko commented Feb 15, 2019

ruslanguns commented Mar 18, 2019 • edited Loading

mcornella commented Mar 25, 2019

pradeepchaudharisc commented Jan 27, 2017 •

edited

Loading

ismailhkose commented Jul 5, 2017 •

edited

Loading

GuganVignesh commented Feb 13, 2019 •

edited

Loading

ruslanguns commented Mar 18, 2019 •

edited

Loading