* Allow global install of PowerShell modules to $env:ProgramFiles\WindowsPowerShell\Modules
* tabs vs spaces
* Updated CHANGELOG.md
* Changed global install of PowerShell modules to $globaldir\Modules
COMSPEC commands fail when called with unescaped directory arguments which contain white spaces (typically a compound user name).
- Closes lukesampson/scoop-extras#1781
- Closes lukesampson/scoop-extras#2389
- Closes#2801
Signed-off-by: Niklas H. <Typhoon.CommanderCool@gmail.com>
* Workaround Microsofts syntactic PSModulePath
The default user PSModulePath is "$env:USERPROFILE\Documents\WindowsPowerShell\Modules". I the user env variable PSModulePath actually exists the default path is omitted - so we need to explicitly add it.
Removes extra 'ERROR' in text where the `error` method is used.
Converts some `write-host "error message"` to use the `error` method
Converts some `write-host "error message"; exit 1` to use the `abort`
method.