How to use oh-my-posh with Constrainedlanguage mode?

[alexanderwwagner]

Hello together,

Description
for me it's not possible to install oh-my-posh with one of the described methods... because of the
ConstrainedLanguage mode. I did some research but I could not found a working solution.

Setup

• Windows 10
• Powershell 7
• ConstrainedLanguage

Reproduce
Try to install with the manual method:

PS C:\Users\wagneral> Set-ExecutionPolicy Bypass -Scope Process -Force; Invoke-Expression ((New-Object System.Net.WebClient).DownloadString('https://ohmyposh.dev/install.ps1'))
New-Object: Cannot create type. Only core types are supported in this language mode.

I can install oh-my-posh with this command if I start a powershell with local admin... but I'm not able to install it for my normal user.

Do you have a idea what I can do to get oh-my-posh working?
Thank you!

[JanDeDobbeleer]

Why not install from the Windows Store in this case?

[JanDeDobbeleer]

@alexanderwwagner you probably need to change jobs at this point in time. We source a script, something that works in constrained language mode, but probably not for all locked down cases. That's not something we can solve on our end. You could try to save the init script (oh-my-posh init pwsh --print) elsewhere and load that.

[alexanderwwagner]

Hmm if I call a "HelloWorld" powershell script within my $PROFILE configuration it works out of the box.
Microsoft.PowerShell_profile.ps1
./helloworld.ps1

Console output:

PowerShell 7.3.4
Hello, World!
Hello, World!
PS C:\Users\wagneral>

If I copy the inserts of "oh-my-posh" init pwsh --print") to a new powershellscript and start this within my $PROFILE configuration
I have again:
Microsoft.PowerShell_profile.ps1: Cannot dot-source this command because it was defined in a different language mode. To invoke this command without importing its contents, omit the '.' operator.

Have you any idea on which point in your script I get the problem with the language mode?

[JanDeDobbeleer]

@alexanderwwagner no, that's a PowerShell question that goes beyond my current knowledge.

[alexanderwwagner]

Hmm now I am one step further...
If I change my "Microsoft.PowerShell_profile.ps1" to use a hardcoded path (not a env) I can run oh-my-posh!
oh-my-posh init pwsh --config 'C:\Users\wagneral\AppData\Local\Packages\oh-my-posh\themes\jandedobbeleer.omp.json' | Invoke-Expression

After that I manually install the recommenend font "Meslo LGM NF" in a manually way for all users.
Then I changed the font in "Windows Terminal" to use this:

But for any reason my symbols are not working... do I have to set manually some path ENVs?

Thank you again!

[JanDeDobbeleer]

@alexanderwwagner probably the font name is incorrect. Or the WT configuration.

[alexanderwwagner]

So finally I get it working!

1. Installed it with the manual method of the documentation (oh-my-posh) as admin

2. Copied installation directories inclusive all binarys to a path to which my normal user has access

3. Add path of binary to "ENV PATH variable"

4. Write in the absolute path without env variable in my $PROFILE
   oh-my-posh init pwsh --config 'C:\Users\wagneral\AppData\Local\Packages\oh-my-posh\themes\jandedobbeleer.omp.json' | Invoke-Expression

5. Install recommended font like specified in the documentation of oh-my-posh

6. Install WindowsTerminal (manually from github)

7. Set Font to installed font of step 5
   

8. Set locale to UTF8
   

9. Add registry insert to can open Windows terminal from the context menu like Powershell 7 (Normal/Admin)

@JanDeDobbeleer thank you for your support! :)

[cspargo-healthedge]

For me I just had to set the Locale to UTF-8 and it started working again 🥂