The displayed Name and Hex properties are empty

[sba923]

I've tried the example given in https://twitter.com/JamesBru/status/1761091548383707161.

All I get (both in Windows PowerShell 5.1.19041.4046 and in PowerShell 7.4.1) is:

(OS is Windows 10 build 10.0.19041.4046)

[StartAutomating]

Thank you for the reminder....

To mark this module as only working on core.

Most of the Emoji will not render on non-core, and the escape sequence is not supported.

[sba923]

It also fails with 7.4.1!

Here's what $error has to say:

[sba923]

Works from 7.4.1 launched with -noprofile:

[StartAutomating]

@sba923 Still looks very weird. I don't think oh-my-posh is doing it, but trying without that might work.

The other guess I have is execution policy (it could be affecting the types files more silently than I would like).

[sba923]

Launching oh-my-posh with the same arguments as from my profile doesn't break Get-Emoji:

[StartAutomating]

The place that is complaining is related to colorization / style, and might be tripped if $psStyle was set to an unexpected value.

If this is the case, you should also see colorization errors if you load up Posh

If you do, then the actual issue is in EZOut (which builds formatters for all of these things)

[sba923]

Does this shed some light on the issue?

[StartAutomating]

Yeah and no. Based off of what you've already sent I already know it's related to $psStyle and how colorization is handled.

But not why it's broken, or how.

Can you poke at $psStyle a bit when it's broken (and not broken) and see what might be going on?

[sba923]

$PSStyle is identical in broken and non-broken sessions.

Posh doesn't break Get-Emoji's output.

[sba923]

And the culprit is...🥁

Set-StrictMode -Version latest

[StartAutomating]

Glad we've found the culprit!

You should be able to reproduce this in EZOut by creating any formatter that uses -Style* parameters:

https://twitter.com/SBarizien/status/1766043978640585185 (just add -StyleProperty to your example)

[sba923]

Fix confirmed, good job!