Init does not work in Windows PowerShell 5.1 if username has unusual characters æ,ø,å
#6739
Unanswered
o-l-a-v
asked this question in
Troubleshoot
Replies: 1 comment 1 reply
-
|
@o-l-a-v unfortunately I can't solve this as it's really an encoding issue client side and not inside oh-my-posh. Additionally, I'm not actively supporting Windows PowerShell anymore as it's crazily outdated. What you could try is upgrade PSReadLine inside that one and see if it makes a difference. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Code of Conduct
What happened?
This is an Intune enrolled, Entra ID joined device, where my username has a
øin it as it's derived from my display name in Entra ID.I've seen the documentation about enabling UTF-8 when initializing oh-my-posh.
https://ohmyposh.dev/docs/faq#powershell-the-term-oh-my-poshexe-is-not-recognized-as-a-name-of-a-cmdlet
Thus, I've placed this in my profile before
oh-my-posh init pwsh:It works in PowerShell v7.5.2. It works in Windows PowerShell on my personal PC where I don't have
øin the username. But it does not work with Windows PowerShell on this system where username hasøin it.Theme
Default, uses
oh-my-posh init pwsh.What OS are you seeing the problem on?
Windows
Which shell are you using?
powershell
Log output
Beta Was this translation helpful? Give feedback.
All reactions