In order for it to work in all locations, you will have to modify your oh-my-posh themes to use a different character that can be represented with a UCS-2 character.įor Version 2 of Oh My Posh, to make the font changes you have to edit the $ThemeSettings variable. That is why you can't have happy faces 😀 in your Windows Console (which makes me sad ☹️). You also tell this because you get 2 boxes (i.e. When you see boxes, that means that the character that is being used is using a region outside of the UCS-2 range. as long as the character can be represented in UCS-2), but won't support all potential (32-bit) Unicode regions. This means you have 'partial' support for Unicode characters in the Windows Console (i.e. One problem, for example, is that because UCS-2 is a fixed-widthġ6-bit encoding, it is unable to represent all Unicode codepoints.

Thus, the Console’s text buffer contains 2-byte wchar_t values per Represent each text character as a fixed-length 16-bit value (UCS-2). Windows Console was created way back in the early days of Windows,īack before Unicode itself existed! Back then, a decision was made to I get the same behavior in Windows Terminal Preview, which is supposed to be the least 'bleeding edge' version.Įven trying non-nerd fonts for 'fontFace' has no effect, however, 'fontSize' will work.The problem is because the Windows Console doesn't fully support UTF-8: Here is the relevant portion of settings.json: ', I'm trying to use a nerd font for some powerline stuff, works in Powershell running in ConEmu but not in Windows Terminal. The problem is that changes to 'fontFace' are not having any effect. I found a profiles.json that follow the new conventions closely enough to work when pasted into settings.json, (I know it took because the theme changed).

Trying out Windows Terminal customization via settings.json.

Windows terminal font type