-
Notifications
You must be signed in to change notification settings - Fork 945
VSCode integrated terminal versus nerdfont-complete #672
Comments
UpdateAt first it seemed like if I found a PowerLine font that was also enabled with My only question now is how to get the prompt to not display so lightly, almost looks like their is opacity to it. settings.json {
"terminal.external.osxExec": "iTerm.app",
"terminal.integrated.cursorBlinking": true,
"terminal.integrated.enableBold": true,
"terminal.integrated.fontFamily": "MesloLGL Nerd Font",
"terminal.integrated.fontSize": 14,
"terminal.integrated.rightClickCopyPaste": true,
} |
Hey @rockchalkwushock! Wow, I'm so sorry it's taken me over a month to respond to this! I'm clearly rather behind at the moment. Okay, so it looks like you were able to resolve your original problem for the most part, but now have a colors issue. In most environments, that is actually a terminal setting where you define what each color looks like. So, for example, if ZSH says "draw a blue character", your terminal will say, "Okay, blue is " and draw it. What is usually totally configurable - you could make it red, if you wanted. Based on your screenshot, it looks to me like your I'm not familiar with VScode, myself. Do you see a way anywhere in the options to tweak that? |
No worries on the delay, I understand. For future users that are using vscode they can follow the instructions found here on how to customize color schemes. In particular they will want to make use of the integrated terminal section. I use
|
This is great! Thanks so much for providing the additional docs, @rockchalkwushock! |
@zhouchao941105 seems you are not using right font. Install nerd font and add font configuration item as mentioned above. |
@LuciferLu Thank you! I installed a new nerd font from github and set it in my vscode, finally it works. |
Thanks so much, everyone! I added @rockchalkwushock's settings to the Wiki, as well =) https://github.com/bhilburn/powerlevel9k/wiki/Troubleshooting#p9k-in-the-vscode-terminal |
For the DejaVu, use "DejaVuSansMono Nerd Font" |
@rockchalkwushock I like your zsh theme, can your share the url? thanks |
ZSH_THEME="powerlevel9k/powerlevel9k" |
This doesn't work for me. I tried downloading https://github.com/ryanoasis/nerd-fonts/blob/master/patched-fonts/Meslo/M/Regular/complete/Meslo%20LG%20M%20Regular%20Nerd%20Font%20Complete%20Mono.ttf and copying it into ~/Library/Fonts I set "terminal.integrated.fontFamily": "MesloLGM Nerd Font" It still gives the weird characters. I can't figure out how to fix it. |
Update: I'm really dumb The filename is separate from what you actually have to put into vs code. In my case, the font name was actually I spent two hours on this.... smh |
Ok. So I think I figured out the problem, ... on MacOSX at least (and maybe on other platforms). When you name the font in VSCode settings it has to match EXACTLY what is reported by your font manager. Not what the filename (or what the download says it's called). Be sure that the names match. For example: That did the trick for me. Hope that helps someone. Give that a try @TheButlah @rockchalkwushock @bhilburn |
Thanks, I was wondering for days why I couldn't configure the fonts in my VScode. |
vscode fonts for the terminal and the icons from Nerd Font. |
I'm new to
zsh
and am running into an issue usingnerdfont-complete
in my config withvscode
. I was looking through related issues and found making sure the fonts match between the terminal and the integrated terminal in VSCode seems to be the underlying issue with the glyphs not displaying. Doesn't seem to be the case though withnerdfonts
. Below are the pertinent screenshots and configurations. If I missed the issue that discusses this please feel free to comment with it and close as a duplicate. I'm wondering if anyone else has ran into this issue with usingnerdfonts
andvscode
.Thank you for your time and assistance!
zsh
5.4.2
macOS
10.3.1
iTerm
3.1.5
VSCode
1.18.0
.zshrc
settings.json
iTerm2 Preferences
iTerm2 Display
VS Code Display
The text was updated successfully, but these errors were encountered: