troubleshooting oh-my-posh glyphs / terminal-icons #3790
-
Hello, I'm rather embarrassed to bring this up but I've been troubleshooting for two days now. I cannot get many glyphs to display properly on Terminal. I should start out by saying I'm native and fluent with Bash/Unix environments. I like to use oh-my-posh as a way of prettying up whenever I remote into a server or need work done on Windows while gaming. I've been trying to read through every FAQ and documentation and still can't get this fixed, so I'm here. I will fully admit that my install process has been confusing. I feel like the way to fix this is the equivalent of git re-basing my entire Windows. I just want a pretty terminal, dangit. Issue: Glyphs not mapping correctly to oh-my-posh installation.Debug Details
Config details:
Logs:
.ps1 profile:
I've tried all three methods of installing oh-my-posh (winget, scoop, manual- in that order). I suspect it is something to do with this. I have removed scoop from my system entirely. Relevant detailsAttempted fix:
Brief notes:
I believe the fundamental issue is that terminal-icons is not mapping correctly with oh-my-posh installation. However, I do not know enough about the source code or its Go to debug it. I am hoping the provided stacktrace provides a little help for my troubleshooting problems. Additionally, I have some questions. Detailed QuestionsQuestions:
Quick Comments:
I hope someone here is able to guide me through some of these hang-ups for why my oh-my-posh can't render glyphs correctly. I'm nearly positive it's terminal-icons module not working properly with my oh-my-posh installation. This is a detail I can't seem to find in the documentation for. A lot of the existing help sources give lots of configs and help for previous versions, which has been confusing to compare with existing documentation. If I can't get this to work through the Windows terminal, I'll probably look at if I can get a ConEmu/other terminal version working. I'm concerned that if I can't get this working on the Windows terminal it'll be even worse with another emulator. I know this is a lot of info to drop just to get glyphs working right. It might be better to post over at terminal-icons, but I want to check whether it's an issue with the OMP installation finding the terminal-icons, not the terminal-icons. Hoping this is a simple easy fix I'm missing:) Best, Gray |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
The solution was I think my confusion was the migration process for the Nerd Fonts had been applied but without success. Given the several installation methods attempted with the correct fix method applied without success. I think the reason I was fooled was verifications of static refs with a cached font. I noticed that I cannot confirm why the given quickfix did not work for me, but I can confirm that it was tried several times earlier today. However, my uneducated guess think that in between my first installation of oh-my-posh and various attempts at installing It appears that I'm particularly unlucky in my timing to install oh-my-posh with the newest release of Nerd Fonts v3, with relevant issues #3781 and ryanoasis/nerd-fonts#365 popping up around the same time. Anyway, I'm happy there's a fix and I hope everyone is entertained enough by my fumbling to not make the same mistakes. Gray |
Beta Was this translation helpful? Give feedback.
-
@noelle-gray think i'm having the same issue and that command didnt seem to help me even after a close and reopen of terminal (vscode hosted powershel) seems like vscode (cursor really) isnt configured correctly and not respecting my theme config change either no real question - more of a papertrail - i'll report back if / when i sort it out |
Beta Was this translation helpful? Give feedback.
The solution was
oh-my-posh config migrate glyphs --write
.I think my confusion was the migration process for the Nerd Fonts had been applied but without success.
Given the several installation methods attempted with the correct fix method applied without success. I think the reason I was fooled was verifications of static refs with a cached font.
I noticed that
oh-my-posh/src/engine/migrate_glyphs.go
references a static map to migrate glyph values. Just throwing out there that it looks like a case could be made for improvingTestGetCodePoints
from checking the length of a key-value map of a single in-house font font to checking the actual font being sent to the terminal emulator in use. …