c38785cbf5
When calling Edit-TextFile wihtout explicitly specifying -Path, multiple files in command line would be passed on to editor incorrectly, with the -Path explicitly specified, this now works in all versions of PowerShell |
||
|---|---|---|
| 7zip | ||
| ansible | ||
| base | ||
| base.linux | ||
| base.win | ||
| docker | ||
| git | ||
| hastebin | ||
| scoop | ||
| shell-loading-snippets | ||
| .gitignore | ||
| LICENSE | ||
| README.md | ||
| Setup-ScriptEnv.ps1 | ||
README.md
PowerShell Scripts
These are the scripts that go into $MyPSScriptRoot which is part of my $env:PATH.
The development of these is documented in my blog: https://blog.lksz.me
They are provided 'as is' for your review and for your reuse.
This envrionment can be installed using one the following options:
The Short, yet safer way
iwr https://lksz.me/pwsz | iex
This sets up the $PROFILE file, and initilizes the default dir $MyPSScriptRoot with a git clone of this repo.
The https://lksz.me/pwsz actually points to the Setup-Profile.ps1 script, which means, that after you have the Scripts directory setup, you can call Setup-Profile to update the $PROFILE after the Setup-Profile.ps1 has been modified (or updated via git pull).
The somewhat Short, but with control option
$sfw=1; iwr https://lksz.me/pwsz | iex; _setup [-sudo] [-Force] [-NoGitClone] [-GitURL <alternative git URL>] [-WhatIf] [-Confirm] [<CommonParameters>]
The key here is $sfw=1, which can be substitued with the more verbose $SetupFromWeb=1, this let's the Setup-Profile script know to just load it's content, but allow you to manually call it's internal function via _setup
The 'I don't trust one liners, what's going on ?!?' option
You can always clone the git repo first, and only then run the Setup-Profile.ps1 script.