From 1cb17699488ef6627647e26da41f1d0513c2d9d8 Mon Sep 17 00:00:00 2001 From: secretspecter Date: Mon, 19 Jun 2023 10:04:31 -0400 Subject: [PATCH] Update 'CrashCourse.md' --- CrashCourse.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CrashCourse.md b/CrashCourse.md index 26f59ea..c40f25a 100644 --- a/CrashCourse.md +++ b/CrashCourse.md @@ -13,7 +13,7 @@ codium "$(Split-Path -Parent $PROFILE.CurrentUserAllHosts)\my-script.ps1" # variables -[PowerShell is as case-insensitive as possible.](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_case-sensitivity?view=powershell-7.3) This means `$MyInvocation` works just the same as `$mYinoCAtiOn` among other things. Coming from a Unix background and preferring some consistency I like to pretend it is case-sensitive so in this repo I'll strive for that but it's worth keeping in mind. Especially since **the Microsoft docs use case a lot** in variable and cmdlet names. +[PowerShell is as case-insensitive as possible.](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_case-sensitivity?view=powershell-7.3) This means `$MyInvocation` works just the same as `$mYinVoCAtiOn` among other things. Coming from a Unix background and preferring some consistency I like to pretend it is case-sensitive so in this repo I'll strive for that but it's worth keeping in mind. Especially since **the Microsoft docs use case a lot** in variable and cmdlet names. Variables use `$` to distinguish themselves and can be set with `=`