search

ryanoasis / nerd-fonts

Iconic font aggregator, collection, & patcher. 3,600+ icons, 50+ patched fonts: Hack, Source Code Pro, more. Glyph collections: Font Awesome, Material Design Icons, Octicons, & more
https://NerdFonts.com
Other
53.94k stars 3.63k forks source link

Caskaydia Cove not displaying on visual studio code, but displayed correctly in the integrated terminal. #785

Closed mina-atef-00 closed 1 year ago

mina-atef-00 commented 2 years ago

🗹 Requirements

🎯 Subject of the issue

Same as Title, Using the same property CaskaydiaCove NF on both the integrated terminal font and the editor font family. But the font is only displayed properly in the integrated terminal.

🔧 Your Setup

★ Screenshots (Optional)

image

johnholliday commented 1 year ago

Is there a workaround to enable CaskaydiaCove NF and Terminal-Icons in the VS terminal? I'm using oh-my-posh in PowerShell and VSCode, but not in VS 2022.

Finii commented 1 year ago

You could use Delugia [1] instead of Caskaydia Cove, if their settings suit you. Otherwise you can use a tool like TransType ($$$) or other open source tools to convert the otfs to ttfs.

Hmm, that answer springs from the conclusion above:

the VS terminal thing does only work with ttf and not with otf at all?

while this Issue's title talks about Visual Studio Code. I'm confused :grinning: You state you use Caskaydia in VSCode.

[1] https://github.com/adam7/delugia-code

johnholliday commented 1 year ago

@Finii I can't use oh-my-posh in Visual Studio 2022 because it does not support CaskaydiaCove NF like both PowerShell and VSCode do. I will try using the delugia-code font to see if that works with Terminal-Icons.

Finii commented 1 year ago

Ok, please report back. Can try to check if problem still. I guess I do not understand what 'Terminal-Icons' means, but maybe that is not important.

bevanshaw commented 1 year ago

Ok, please report back. Can try to check if problem still. I guess I do not understand what 'Terminal-Icons' means, but maybe that is not important.

This is what terminal icons means. They are the small triangles and pictures that work with nerd fonts. Below is an image from Visual Studio Code where the icons are working followed by Visual Studio 2022 Developer Powershell 7 Terminal where they are not:

VS Code icons working: image

VS 2022 icons not working: image

Finii commented 1 year ago

With the Nerd Font v3.0.0 Release Caskaydia Cove is now ttf and not otf any longer. That was needed to get the hints in the font match expectations (i.e. compare almost equal to the variable Cascadia Code font that a lot people have installed out of the box and that they use to compare.

Regarding the missing icons, if that is still a problem with 3.0.0, please open a new Issue.

To make sure the correct fonts are installed

ite-klass commented 1 year ago

I have removed Caskaydia Cove, verified no Caskaydia font files in system nor user folder, restarted the system, installed all the Caskaydia ttf for all users.

They work fine in various programs (VS Code, KDiff3, Double Commander). But not in Visual Studio. (It falls back to a different font, seemingly Courier.)

Windows 10. VS 2022 17.5.5. Nerd Fonts 3.0.1.

Finii commented 1 year ago

That is Visual Studio 'proper', not Visual Studio Code, I guess.

Is that in the code editor or the terminal? Screenshot, also of the settings?

Edit: Ah yes, you explicitly mention VScode as working :+1:

Finii commented 1 year ago

Hmm, it happens in both, the editor and the terminal. It also happens with VS 19

(O_o)

alexis35115 commented 1 year ago

any news on this, i have the same issue on Visual Studio 2022 and the lastest version of the font.

It was working on W10 but not longer works on W11.

johnholliday commented 1 year ago

Caskaydia Code doesn't work, but Hack Nerd works just fine. First, go to nerdfonts.com and download the Hack Nerd Font. Then install the font onto your system. Finally, restart Visual Studio and select "Hack Nerd Font Mono" for the Terminal font.

github-actions[bot] commented 7 months ago

This issue has been automatically locked since there has not been any recent activity (i.e. last half year) after it was closed. It helps our maintainers focus on the active issues. If you have found a problem that seems similar, please open a new issue, complete the issue template with all the details necessary to reproduce, and mention this issue as reference.