1) It would be good were this (overly?) long page to disclose how one simply gives a colour to the prompt (and differentially to its various elements, if that is possible without a plugin), as against going the whole way with the 'Oh My Posh' plugin. The page does include a link to a page that treats the PowerShell Prompt and which, sort of, treats how to change the colour of that prompt. But what is wanted is an easy way for Windows Terminal users to find a reasonably thorough guide to changing the prompt's colour. For, setting that colour is fairly basic stuff, and yet users new to Windows terminal will not know how to do it.
2) (a) The aforementioned webpage about 'Oh My Posh' gives a command for installing that program and then a few lines later says, in effect: 'hey! Don't use that installation command - use this one (the Windows Store one) instead'! I ended up aborting the first command and then running the second. (b) That same webpage recommends the command oh-my-posh init pwsh --config "$env:POSH_THEMES_PATH\paradox.omp.json" | Invoke-Expression, which throws a warning (albeit perhaps from my linter). The warning is: `Invoke-Expression is used. Please remove Invoke-Expression from script and find other options instead.'
from @LinuxDesktop in https://github.com/microsoft/terminal/issues/17591
1) It would be good were this (overly?) long page to disclose how one simply gives a colour to the prompt (and differentially to its various elements, if that is possible without a plugin), as against going the whole way with the 'Oh My Posh' plugin. The page does include a link to a page that treats the PowerShell Prompt and which, sort of, treats how to change the colour of that prompt. But what is wanted is an easy way for Windows Terminal users to find a reasonably thorough guide to changing the prompt's colour. For, setting that colour is fairly basic stuff, and yet users new to Windows terminal will not know how to do it.
2) (a) The aforementioned webpage about 'Oh My Posh' gives a command for installing that program and then a few lines later says, in effect: 'hey! Don't use that installation command - use this one (the Windows Store one) instead'! I ended up aborting the first command and then running the second. (b) That same webpage recommends the command
oh-my-posh init pwsh --config "$env:POSH_THEMES_PATH\paradox.omp.json" | Invoke-Expression, which throws a warning (albeit perhaps from my linter). The warning is: `Invoke-Expression is used. Please remove Invoke-Expression from script and find other options instead.'