# PowerShell on Windows

No I'm not happy about this brain damage. And no there will not be "on MacOS" or "on Linux" flavors, from me anyway.

# Install and setup

Windows 11, at the time of writing, doesn't come with the latest PowerShell. It will tell you that when you open PowerShell even. You can acquire it like this (or [some other way](https://learn.microsoft.com/en-us/powershell/scripting/install/installing-powershell-on-windows?view=powershell-7.3)):

```powershell
winget search Microsoft.PowerShell
winget install --id Microsoft.Powershell --source winget
```

Then clone this repository to the desired `$PROFILE` sorta like this:

```powershell
# get the URL from wherever this repo is hosted
git clone <url> (Split-Path -Parent $PROFILE.CurrentUserAllHosts)
```

Or follow along below to understand what this repository is about!

# `$PROFILE`

`$PROFILE.CurrentUserAllHosts` is a good place to make customizations (if you're familiar with Bash it's similar to `~/.bashrc`). There is a specific `$PROFILE.CurrentUserCurrentHost` when you're inside VSCodium and other Hosts if you're interested in that, they all inherit from `$PROFILE.CurrentUserAllHosts` which is probably `~/Documents/PowerShell/profile.ps1` by the way!

You can create a profile with `New-Item` and start editing it with `notepad` (or `codium`).

```powershell
New-Item -Path $PROFILE.CurrentUserAllHosts -ItemType "file" -Force
notepad $PROFILE.CurrentUserAllHosts
```

A very simple first customization one can do is update the prompt. This will indicate whether or not you're running as an Adminsitrator.

```powershell
function prompt {
  $prompt = "> "
  $current_user = New-Object Security.Principal.WindowsPrincipal(
    [Security.Principal.WindowsIdentity]::GetCurrent()
  )

  If ($current_user.IsInRole(
    [Security.Principal.WindowsBuiltinRole]::Administrator
  )) {
    $prompt = "Admin$prompt"
  }

  $prompt
}
```

I also added `install_scoop` and `install_bleachbit` utility functions. They are totally optional but, I think, useful.

# `$env:PATH`

Folders in the semi-colon seperated `$env:PATH` string are searched for cmdlets, executables and scripts to run (again, if you're familiar with Bash it's similar to `$PATH`). Putting the following in `$PROFILE` will make custom `.ps1` scripts in that same folder "global" (available from any prompt without specifying the whole path).

```powershell
$env:path += ";$(Split-Path -Parent $MyInvocation.MyCommand.Path)"
```

[`Split-Path`](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.management/split-path?view=powershell-7.3) is a pretty useful cmdlet for working with paths. Here we're saying "give me the parent folder for the current command path", the current command is `$PROFILE` in this context. `MyInvocation` is from the [automatic variables](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_automatic_variables?view=powershell-7.3#myinvocation) which are provided by PowerShell under-the-hood.

With this I've also added a `full_update.ps1` script that will update Windows as well as scoop if it's installed and then run `bleachbit --preset --clean` (also only if installed) which depends on whatever you've last checked in the bleachbit UI... so run that and set it up first! The script will also run itself again as Administrator if you're not in an elevated session already... which is usually. If you're familiar with Arch Linux you might say `yay`!

Checkout the [Crash Course](./CrashCourse.md) for a terse guide on writing your own PowerShell scripts.

# See Also

- [About profile (learn.microsoft.com)](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_profiles?view=powershell-7.3)
- [Creating profiles (learn.microsoft.com)](https://learn.microsoft.com/en-us/powershell/scripting/learn/shell/creating-profiles?view=powershell-7.3)