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

SEGMENT_SEPARATOR #1

Closed
premedios opened this issue Nov 6, 2014 · 22 comments
Closed

SEGMENT_SEPARATOR #1

premedios opened this issue Nov 6, 2014 · 22 comments

Comments

@premedios
Copy link

After installing the cobalt2 zsh theme, my segment separator is not seamless...it's just a black block with a white square.

@wesbos
Copy link
Owner

wesbos commented Nov 6, 2014

screenshot?

@premedios
Copy link
Author

screen shot 2014-11-06 at 22 32 42

@wesbos
Copy link
Owner

wesbos commented Nov 6, 2014

Oh yeah you'll need a patched power line font. I reccomend inconsolata.
I'll try find the links when I'm home.
On Thu, Nov 6, 2014 at 5:29 PM Pedro Remedios [email protected]
wrote:

[image: screen shot 2014-11-06 at 22 32 42]
https://cloud.githubusercontent.com/assets/265363/4945118/55813792-6604-11e4-8fb8-3de7b8f6a8f6.png


Reply to this email directly or view it on GitHub
#1 (comment).

@cardinallijr
Copy link

@premedios
Copy link
Author

It didn't work after install the fonts. Even after I selected the proper powerline font (in this case Inconsolata For Powerline)

@wesbos
Copy link
Owner

wesbos commented Nov 7, 2014

Make sure you have set your terminal client (iterm or terminal) to use that font

@premedios
Copy link
Author

I did

@wesbos
Copy link
Owner

wesbos commented Nov 8, 2014

Not sure then. You have either an issue with iterm not using the right font
or the right font being installed.
On Fri, Nov 7, 2014 at 5:59 PM Pedro Remedios [email protected]
wrote:

I did


Reply to this email directly or view it on GitHub
#1 (comment).

@jcypret
Copy link
Contributor

jcypret commented Dec 2, 2014

I also ran into this. There seems to be some two standards for the unicode symbols used for Powerline.

Name powerline fonts powerline-vim
Version control branch U+E0A0 U+2B60
LN (line) symbol U+E0A1 U+2B61
Closed padlock U+E0A2 U+2B64
Rightwards thick arrowhead U+E0B0 U+2B80
Rightwards arrowhead U+E0B1 U+2B81
Leftwards thick arrowhead U+E0B2 U+2B83
Leftwards arrowhead U+E0B3 U+2B84

Using the fonts downloaded from https://github.com/Lokaltog/powerline-fonts, the theme did not work. I ran into the same issue as @premedios. I had to edit the theme and swap out the version control and right arrow symbols with the powerline fonts unicode.

I have created a fork with the alternate version (https://github.com/jcypret/Cobalt2-iterm). I'm not sure which are the "correct" unicodes.

@dankraus
Copy link

dankraus commented Feb 3, 2015

I was having the same issue. Installed powerline fonts, set the fonts accordingly. I used @jcypret 's fork and worked perfectly. Thanks!

@samuelbran
Copy link

Same issue, @jcypret fork worked perfectly

@wesbos
Copy link
Owner

wesbos commented Apr 5, 2015

@jcypret Ah - sorry I didn't see this earlier. Can you submit a PR?

@jcypret
Copy link
Contributor

jcypret commented Apr 6, 2015

No problem. I have created the pull request #3

@jandetlefsen
Copy link

Still broken for me after following all the steps here, OSX 10.10.3, latest iTerm. Any pointer where to check?

@samuelbran
Copy link

@jandetlefsen did you change both Regular font and Non-ASCII font options for a Powerline font?

@jandetlefsen
Copy link

oh that did the trick, thanks

@jandetlefsen
Copy link

thanks for putting this together, looks fantastic now!

@samuelbran
Copy link

Hell yeah! thanks @wesbos

@aniallator8
Copy link
Contributor

I was having a little problem with this until I found this issue. Maybe add a little note to the readme about changing the font for each type to 'Inconsolata for Powerline' once the powerline fonts have been installed... Happy to do it if need be.

@matplane
Copy link

+1 to @nrutter2000 comment ;)

@wesbos
Copy link
Owner

wesbos commented Apr 13, 2015

@nrutter2000 Yeah that would be great!

@aniallator8
Copy link
Contributor

No worries. I've created pull request #4

wesbos pushed a commit that referenced this issue Apr 13, 2015
@wesbos wesbos closed this as completed Aug 17, 2015
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

9 participants