Makes it trivial to launch terminals as different users.

Supports opening multiple terminals in different tabs.

An advanced console emulator where you can run your shell of choice.

Proper support for copy/paste/cut (Ctrl+C/X/V should all work just fine)Īlternatively, you can use Clink, which has a similar set of features but wasn't strictly written for PowerShell.

Easily view previous multi-line commands using arrow keys rather than just the last line of the command.

Bash/zsh interactive history search (Ctrl + R).

Clearly indicates syntax errors with a red '>' character.

Syntax highlighting whenever you start typing commands.

Significantly improves the console editing experience.

If you're interested in trivia, here's an answer to why MS created PowerShell from the lead architect.

Optionally consider Posh-Git, a PowerShell script for git to gain contextual tab-completion.

PSGet is a package manager for PowerShell allowing you to easily extend it. This requires getting used to but avoids reparsing when you want to get out a property. Unlike Unix, it pipes objects rather than text streams.

Aliases can be persisted in a PowerShell profile.

For example: Set-Alias server python -m rver 8000 launches a Python server when the server alias is used. If moving from another shell to PS, Set-Alias lets you map aliases you're used to to Windows equivalents. Has integrated aliases and commands (called cmdlets - e.g Select-String is like grep, Invoke-Elevated is like sudo, Sort-Object is like sort, Get-Process lists all active processes).Significantly closer to a real 'shell' than cmd.exe, offering us a powerful scripting environment for task automation.See below for some more notes on what these different pieces of machinery give you. As devs who spend the majority of our time coding on OSX and Linux, we were curious what a modern command-line setup might look like on Windows.Ī StackOverflow developer survey reminded us that there are more devs using Windows than any other OS so we were curious if the tooling there was on par with what we were used to in *nix land.Īfter spending some time evaluating the landscape of Windows CLI tooling, we settled on a set of tools we think gets us 95% of the way there.Īt the end of the day, we landed on a combination of:

Java command line tool mac error