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

Powerline fonts in terminal incorrect #7116

Closed
jchannon opened this Issue Jun 2, 2016 · 19 comments

Comments

Projects
None yet
@jchannon

jchannon commented Jun 2, 2016

  • VSCode Version: 1.2.0-insiders
  • OS Version: OSX

Steps to Reproduce:

  1. Open Code from terminal
  2. Open integrated terminal
  3. See fonts are broken
  4. This may be some Powerline font issue in tty but seems to work ok in Atom integrated terminal ok
  5. Picture below shows code, bottom terminal is what it should look like
    screen shot 2016-06-02 at 07 24 53
@Tyriar

This comment has been minimized.

Show comment
Hide comment
@Tyriar

Tyriar Jun 2, 2016

Member

@jchannon I haven't used these before. Do I install from https://github.com/powerline/fonts and then use some special characters in my prompt?

Member

Tyriar commented Jun 2, 2016

@jchannon I haven't used these before. Do I install from https://github.com/powerline/fonts and then use some special characters in my prompt?

@jchannon

This comment has been minimized.

Show comment
Hide comment
@jchannon

jchannon Jun 2, 2016

Nope just use those fonts, install OH MY ZSH and then maybe set the theme
to be something like here:
https://coderwall.com/p/sun7za/mac-os-x-oh-my-zsh-theme-on-iterm2

On 2 June 2016 at 08:23, Daniel Imms notifications@github.com wrote:

@jchannon https://github.com/jchannon I haven't used these before. Do I
install from https://github.com/powerline/fonts and then use some special
characters in my prompt?


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#7116 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AAGapsnbtsqn89HTPu7Vgbt514PEogGDks5qHoTZgaJpZM4IsPeG
.

jchannon commented Jun 2, 2016

Nope just use those fonts, install OH MY ZSH and then maybe set the theme
to be something like here:
https://coderwall.com/p/sun7za/mac-os-x-oh-my-zsh-theme-on-iterm2

On 2 June 2016 at 08:23, Daniel Imms notifications@github.com wrote:

@jchannon https://github.com/jchannon I haven't used these before. Do I
install from https://github.com/powerline/fonts and then use some special
characters in my prompt?


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#7116 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AAGapsnbtsqn89HTPu7Vgbt514PEogGDks5qHoTZgaJpZM4IsPeG
.

@Tyriar Tyriar removed the needs more info label Jun 2, 2016

@ibratoev

This comment has been minimized.

Show comment
Hide comment
@ibratoev

ibratoev Jun 7, 2016

This might be caused by lack of proper locale. See #7301 for workaround.

ibratoev commented Jun 7, 2016

This might be caused by lack of proper locale. See #7301 for workaround.

@JuHwon

This comment has been minimized.

Show comment
Hide comment
@JuHwon

JuHwon Jun 7, 2016

i am having the same issue on linux with zsh

JuHwon commented Jun 7, 2016

i am having the same issue on linux with zsh

@Sephizor

This comment has been minimized.

Show comment
Hide comment
@Sephizor

Sephizor Jun 8, 2016

Same issue here on Linux, 1.2 release.

OS: Ubuntu Gnome 16.04
Shell: Zsh (oh-my-zsh)
Zsh theme: powerlevel9k
Font: Ubuntu Mono derivative Powerline Regular

I tried the mac workaround but unfortunately it did nothing.

Sephizor commented Jun 8, 2016

Same issue here on Linux, 1.2 release.

OS: Ubuntu Gnome 16.04
Shell: Zsh (oh-my-zsh)
Zsh theme: powerlevel9k
Font: Ubuntu Mono derivative Powerline Regular

I tried the mac workaround but unfortunately it did nothing.

@reaktivo

This comment has been minimized.

Show comment
Hide comment
@reaktivo

reaktivo Jun 15, 2016

Contributor

@jchannon I had this issue on OS X. It has to do with the Terminal not using the editor.fontFamily setting, can you try setting your terminal.integrated.fontFamily to the same powerline font used in editor.fontFamily?

Contributor

reaktivo commented Jun 15, 2016

@jchannon I had this issue on OS X. It has to do with the Terminal not using the editor.fontFamily setting, can you try setting your terminal.integrated.fontFamily to the same powerline font used in editor.fontFamily?

@JuHwon

This comment has been minimized.

Show comment
Hide comment
@JuHwon

JuHwon Jun 15, 2016

setting the terminal.integrated.fontFamily in my User Settings file fixed it. thx.

JuHwon commented Jun 15, 2016

setting the terminal.integrated.fontFamily in my User Settings file fixed it. thx.

@jchannon

This comment has been minimized.

Show comment
Hide comment
@jchannon

jchannon Jun 15, 2016

That seems to do the trick however, the colours are different and the right hand side seems off

screen shot 2016-06-15 at 13 31 21

jchannon commented Jun 15, 2016

That seems to do the trick however, the colours are different and the right hand side seems off

screen shot 2016-06-15 at 13 31 21

@reaktivo

This comment has been minimized.

Show comment
Hide comment
@reaktivo

reaktivo Jun 15, 2016

Contributor

Let's wait to get Terminal theme support, but that's another issue. About the time on the right, I guess the terminal is reporting incorrect terminal column width.

Contributor

reaktivo commented Jun 15, 2016

Let's wait to get Terminal theme support, but that's another issue. About the time on the right, I guess the terminal is reporting incorrect terminal column width.

@Tyriar

This comment has been minimized.

Show comment
Hide comment
@Tyriar

Tyriar Jun 15, 2016

Member

Great to hear that the main issue is the font wasn't being set. In 1.3.0 the font's default fallback is editor.fontFamily but you can set it explicitly with terminal.integrated.fontFamily #6791

I'm going to close this off but these issues may still be blocking this:

Member

Tyriar commented Jun 15, 2016

Great to hear that the main issue is the font wasn't being set. In 1.3.0 the font's default fallback is editor.fontFamily but you can set it explicitly with terminal.integrated.fontFamily #6791

I'm going to close this off but these issues may still be blocking this:

@Tyriar Tyriar closed this Jun 15, 2016

@xujipm

This comment has been minimized.

Show comment
Hide comment
@xujipm

xujipm Mar 17, 2017

I am having the same issue on OS X with zsh

font, SourceCodePro+Powerline+AwesomeRegular
font source, https://github.com/stefano-meschiari/dotemacs/blob/master/SourceCodePro%2BPowerline%2BAwesome%2BRegular.ttf

image

image

xujipm commented Mar 17, 2017

I am having the same issue on OS X with zsh

font, SourceCodePro+Powerline+AwesomeRegular
font source, https://github.com/stefano-meschiari/dotemacs/blob/master/SourceCodePro%2BPowerline%2BAwesome%2BRegular.ttf

image

image

@Tyriar

This comment has been minimized.

Show comment
Hide comment
@Tyriar

Tyriar Mar 17, 2017

Member

@xujipm try these instructions #15119 (comment)

Member

Tyriar commented Mar 17, 2017

@xujipm try these instructions #15119 (comment)

@xujipm

This comment has been minimized.

Show comment
Hide comment
@xujipm

xujipm Mar 18, 2017

@Tyriar i have try that way, but didn't work~

xujipm commented Mar 18, 2017

@Tyriar i have try that way, but didn't work~

@Gkjsdll

This comment has been minimized.

Show comment
Hide comment
@Gkjsdll

Gkjsdll Apr 10, 2017

@xujipm I use the same font and this worked for me:
"terminal.integrated.fontFamily": "'SourceCodePro+Powerline+Awesome Regular'"
Note the single quotes inside of the double quotes.
image

Gkjsdll commented Apr 10, 2017

@xujipm I use the same font and this worked for me:
"terminal.integrated.fontFamily": "'SourceCodePro+Powerline+Awesome Regular'"
Note the single quotes inside of the double quotes.
image

@LarryWachira

This comment has been minimized.

Show comment
Hide comment
@LarryWachira

LarryWachira Apr 21, 2017

@Gkjsdll Thanks! Working fine now.

LarryWachira commented Apr 21, 2017

@Gkjsdll Thanks! Working fine now.

@jongear

This comment has been minimized.

Show comment
Hide comment
@jongear

jongear Apr 27, 2017

@Gkjsdll Your solution worked!

jongear commented Apr 27, 2017

@Gkjsdll Your solution worked!

@jpdoria

This comment has been minimized.

Show comment
Hide comment
@jpdoria

jpdoria May 13, 2017

@Gkjsdll Cool! Thanks for the solution!

jpdoria commented May 13, 2017

@Gkjsdll Cool! Thanks for the solution!

@outtoin

This comment has been minimized.

Show comment
Hide comment
@outtoin

outtoin May 27, 2017

@Gkjsdll Nice Solution!

outtoin commented May 27, 2017

@Gkjsdll Nice Solution!

@Microsoft Microsoft locked and limited conversation to collaborators May 30, 2017

@Tyriar

This comment has been minimized.

Show comment
Hide comment
@Tyriar

Tyriar May 30, 2017

Member

Locking to stop notifications and prevent the solution above from being buried. If the solutions above don't work for you, feel free to file a new issue and link it to this one.

Member

Tyriar commented May 30, 2017

Locking to stop notifications and prevent the solution above from being buried. If the solutions above don't work for you, feel free to file a new issue and link it to this one.

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