We can get rid of this nonsense now that Powershell is executing mkdir (and can escape the path properly).

I tried exit 1 here, but apparently Powershell ignores it and decides to just exit with an error code of 0 instead. So instead I'm throwing an exception which causes it to have an error code of 1, but unfortunately causes this message to get sent to stderr.

This prevents Powershell from wrapping lines (well, any lines shorter than 512 characters).

This copies the environment variables from a real Windows session and overrides the UNIX-like environment that Cygwin sets up.

This re-invokes Powershell with the command. The reason for this is that Powershell behaves differently with regard to exit codes and error handling from a command in these two scenarios:

powershell.exe -Command some_command

$script = @"

# prefix code here

some_command
"@

powershell.exe -EncodedCommand <encoded script>