Pretty grid $colors = [enum]::GetValues([System.ConsoleColor]) Foreach ($bgcolor in $colors){ Foreach ($fgcolor in $colors) { Write-Host “$fgcolor|” -ForegroundColor $fgcolor -BackgroundColor $bgcolor -NoNewLine } Write-Host ” on $bgcolor” } Updated colours in newer powershell: https://gist.github.com/timabell/cc9ca76964b59b2a54e91bda3665499e
It returns true if the last command was successful, else false. However, there are a number of caveats and non-obvious behaviour (e.g. what exactly is meant by “success”). I strongly recommend reading this article for a fuller treatment. For example, consider calling Get-ChildItem. PS> Get-ChildItem PS> $? True $? will return True as the call … Read more
Unless you read the input file into memory in full, up front, you cannot safely read from and write back to the same file in a given pipeline. Specifically, a command such as Import-Csv file.csv | … | Export-Csv file.csv will erase the content of file.csv.[1] The simplest solution is to enclose the command that … Read more
tl;dr While Joel Coehoorn’s helpful answer provides an effective solution to your Start-Process problem (which stems from the bug detailed below), you can simplify your code to: foreach ($file in $myfiles) { # Note: | Out-Null is a trick that makes calling *GUI* applications # *synchronous* (makes PowerShell wait for them to exit). & $npp … Read more
If you construct a string such as -t foo and pass it via a variable to an external program, it is passed as a single, double-quoted argument (that is, donet will literally see “-t foo” on its command line) – and therefore won’t be recognized as parameter name-value combination. You must pass -t and foo … Read more
Note that [securestring] is not recommended for new code anymore. While on Windows secure strings offer limited protection – by storing the string encrypted in memory – via the DPAPI – and by shortening the window during which the plain-text representation is held in memory, no encryption at all is used on Unix-like platforms.[1] The … Read more
It’s kinda true, but not really at all. What do I mean with that? First, let’s get your documentation question out of the way. The following is from paragraph ยง3.13 of the PowerShell version 3.0 Language Specification: If a command writes a single object, its successor receives that object and then terminates after writing its … Read more
The syntax is way off. A few issues: I’m not sure what $($.19981016) was intended to produce, but $( ) evaluates the expression in the parentheses and interpolates the result into the string, and you’re getting the error because $.19981016is not a valid expression. The error would be repeated for each .jpg file in the … Read more
.Length and .Count are aliases of one another and are so-called intrinsic members (properties) that PowerShell adds to most objects, in the interest of unified treatment of scalars and collections (see this answer for background). The exception are objects of types that PowerShell treats as collections, i.e. objects that it automatically enumerates in the pipeline, … Read more
To complement zett42’s helpful answer: If you’re running PowerShell (Core) 7+, you can pass the file path that represents the terminal (console) to the (positionally implied) -FilePath parameter (in Windows PowerShell, this causes an error, unfortunately – see bottom section): # PowerShell 7+ only # Windows Get-Content data.txt | Tee-Object \\.\CON | data_processor.exe # Unix-like … Read more