Update custom prompt tutorial w latest OMP steps

[mattwojo]

No description provided.

[opbld31]

Docs Build status updates of commit 3e2f1dd:

✅ Validation status: passed

File	Status	Preview URL	Details
TerminalDocs/images/ohmyposh-terminal-prompt.png	✅Succeeded	View
TerminalDocs/tutorials/custom-prompt-setup.md	✅Succeeded	View

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching the docs.microsoft.com contributor guides
• Post your question in the Docs support channel

[JanDeDobbeleer]

This cmdlet is currently deprecated. Favoring the init script instead:

oh-my-posh --init --shell pwsh --config ~/jandedobbeleer.omp.json | Invoke-Expression

Import-Module oh-my-posh is only required when installing with Install-Module oh-my-posh

[mattwojo]

I'm not sure that I understand and am not quite clear on what you're saying is deprecated.
In the OMP docs, it looks like the PowerShell install for Windows has the first step for install as: Install-Module oh-my-posh -Scope CurrentUser
...so I'm also confused by the statement that Import-Module oh-my-posh is only required when installing with Install-Module oh-my-posh. We are installing with Install-Module, yes?

So the Import-Module oh-my-posh should not be added to the PowerShell $PROFILE file?
And does that init script go in the $PROFILE to run every time? Or is this a one-time command?

[JanDeDobbeleer]

When installing with Install-Module oh-my-posh you always need to run Import-Module oh-my-posh to load the oh-my-posh executable in the $PATH. That part is correct. I was stating we've deprecated the Set-PoshPrompt cmdlet although it's still available and will work. Now, for sake of our documentation we're not adding that again as it makes the maintenance between everything rather challenging but in this context it makes perfect sense. So let's agree to keep supporting the cmdlet meaning the above information is correct.

[mattwojo]

Ahh! Thanks for clarifying. Ok - so no change?

I can replace Set-PoshPrompt with oh-my-posh --init --shell pwsh --config ~/jandedobbeleer.omp.json | Invoke-Expression if that is the preferred method, but if it's just a matter of upkeep for documentation and Set-PoshPrompt works fine, then I'll leave as-is as you suggest. Just let me know if that changes and thank you again for the help on getting all of this clear.

[JanDeDobbeleer]

Let's leave it as is for the sake of simplicity.