Dominik Kaszewski

Does the issue persist between commands? That is, if you run e.g. `Get-ChildItem` after that, does it display color normally or is it still messed up? If only this specific...

I'll take a look at it as part of PR #17780 , I saw something that may suggest the error hint about `en-US` being available does not actually take into...

I found an issue in `UpdatableHelpCommandBase:EndProcessing`: even though original exceptions contain a list of supported cultures: `"The specified culture is not supported: en-GB. Specify a culture from the following list:...

Can you please explain what you mean by "customization"? I am not aware of anything outside of `$PROFILE` file which you can easily backup.

Isn't `Set-StrictMode` already a "breaking" change for most scripts? Yet many people put it at the top of every file to avoid things like access to non-existent variables, while only...

I compiled from source, set `$DOTNET_ROOT` to the `.dotnet` in repo, works. Try with `OmniSharp` downloaded from releases, works. I moved it couple times to another directory and back (always...

I managed to solve it by setting `$DOTNET_ROOT` to .NET6 **and** adding it to `$PATH`. If I don't add to `$PATH`, then I get the error as above. If I...

Yeah, would be good to distinguish the following cases: * cannot find dotnet in `$PATH` * can find dotnet, but no 6+ SDKs * can find dotnet, but all SDKs...

Workaround is to wrap any globbing with `(Get-ChildItem ...)`. This is also a problem on Windows using utilities ported from Unix which expect globbing to be expanded by shell. Examples:...

[Posh-Git seems to work](https://github.com/dahlbyk/posh-git/blob/master/src/Utils.ps1#:~:text=function%20Get%2DPromptPath), I checked that updating the prompt to the following is sufficient: ```pwsh function prompt { $pathInfo = $ExecutionContext.SessionState.Path.CurrentLocation # Simplify provider path like `Microsoft.PowerShell.Core\FileSystem::C:\Windows` $currentPath =...