The plugin's default shell on Windows will be changed to PowerShell 5

[Taitava]

This announcement only concerns Windows users, not Linux or Mac.

I have a plan to change the default Windows shell that SC uses from CMD to PowerShell, because it will (I hope) allow variable value escaping. I just need to pick either PowerShell 5 or PowerShell Core (a user can change that setting, I'm only talking about the default).

• PowerShell 5: Comes preinstalled on all Windows 10 systems, and if I have understood correctly, also on Windows 11. Has a damn charset inconsistency, so when outputting to a file with >/>>, the output will be UTF-16 instead of UTF-8. Other output is UTF-8.
• PowerShell Core: Newer and better behaving, but does not come preinstalled on any Windows version AFAIK. Can be installed manually, and can be taken into use in SC in settings (as of SC version 0.7.0).

So I guess PowerShell 5 will be the default, because I cannot rely that all Windows users of SC will have PowerShell Core installed, and I don't want to increase the getting started curve of SC by saying to all Windows users: "Hey, after installing this plugin, you should also install PowerShell Core".

• Changing the default shell will only affect new installations, old ones will still use CMD so a user's current commands will not suddenly change to use a different shell.
• I haven't decided a release for this change, but it's not gonna be yet in 0.7.0.

[Taitava]

Just an update to this: I haven't yet changed the default shell for Windows, it's still CMD. I still need to think about this, there are some non-ASCII character encoding problems with the PowerShell support.