-
Notifications
You must be signed in to change notification settings - Fork 388
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Icons are broken [WSL / Ubuntu] #379
Comments
Hi. What version of colorls are you using? And what is the output of |
Same issue and setup, on WSL2. ➜ colorls --version ➜ locale |
How did you configure |
Here is what I've got, @avdv. Thanks!
(1) How did you configure fontFamily for Hyper, which nerd font did you install?
(2) Does colorls work in other terminal emulators?
|
This is not a Nerd font. The corresponding Nerd font is called "SauceCodePro Nerd Font" (renamed because of legal reasons), see here. |
Thanks, @avdv! That was it! I thought Powerline and nerd font were the same thing 🤦♀️ Thanks for helping! |
Closing, since this should be resolved. |
I still have the same problem with these font settings in Hyper. It works fine on my laptop with Ubuntu desktop. |
You need to install a Nerd Font first. Then you should add that font to the setting in hyper. All Nerd Fonts have "Nerd Font" in their name. |
Thanks, I got it fixed now! |
@bluebrown try to use a different variant instead of "Mono". Especially the "Windows Compatible" variants maybe? |
Hello, I am having a similar issue? I am using WSL with ubuntu, and FiraCode, I followed this tutorial: https://www.youtube.com/watch?v=2LEnBXH8xV0&t=2s
the fonts, I downloaded from: https://www.nerdfonts.com/font-downloads and also installed inside the linux terminal using |
Description
Type of issue: Font-related
I have tried a bunch of different Nerd fonts to no avail. All the font icons work fine in the Spaceship prompt, which makes me think it might be a icon mapping issue specific to my system (WSL2).
System:
Windows 10 Pro 2004 19041.421
WSL2 Ubuntu 18.04.4 LTS
Hyper / VS Code
The text was updated successfully, but these errors were encountered: