Many years ago .NET Core added Command line "tab" completion for .NET Core CLI in PowerShell or bash but few folks have taken the moment it takes to set up.
I enjoy setting up and making my prompt/command line/shell/terminal experience as useful (and pretty) as possible. You have lots of command line shells to choose from on Windows!
Keep in mind these are SHELLs not terminals or alternative consoles. You can run all of these in the Windows Terminal.
- Classic cmd.exe command prompt (fake DOS!) - Still useful and Clink can make it more bash-y without going full bash.
- Yori from Malcolm Smith
- Starship - more on this later, it's somewhat unique
- Windows PowerShell - a classic because...
- PowerShell 7 is out and runs literally anywhere, including ARM machines!
I tend to use PowerShell 7 (formerly PowerShell Core) as my main prompt because it's a cross-OS prompt. I can use the same prompt, same functions, same everything on Windows and Linux.
But it's command-line autocompletion that brings me the most joy!
- git ch<TAB> -> git checkout st<TAB> -> git checkout staging
- dotnet bu<TAB> -> dotnet build
- dotnet --list-s<TAB> -> dotnet --list-sdks
- winget in<TAB> -> winget install -> winget install WinDi<TAB> -> winget install WinDirStat
Once you have successfully tab'ed you way to glory it's hard to stop. With PowerShell and its cousins this is made possible with Register-ArgumentCompleter. Here's what it looks like for the dotnet CLI.
# PowerShell parameter completion shim for the dotnet CLI
Register-ArgumentCompleter -Native -CommandName dotnet -ScriptBlock {
param($commandName, $wordToComplete, $cursorPosition)
dotnet complete --position $cursorPosition "$wordToComplete" | ForEach-Object {
[System.Management.Automation.CompletionResult]::new($_, $_, 'ParameterValue', $_)
}
}
Looks like a lot, but the only part that matters is that when it sees the command "dotnet" and some partial text and the user presses TAB, it will call "dotnet complete" passing in the cursorPosition and the wordToComplete.
NOTE: If you understand how this works, you can easily make your own Argument Completer for those utilities that you use all the time at work! You can make them for the folks at work who use your utilities!
You never actually see this call to "dotnet complete." You just see yourself typing dotnet bui<TAB> and getting a series of choices to tab through!
Here's what happens behind the scenes:
>dotnet complete --position 3 bui
build
build-server
msbuild
You can add these to your $profile. Usually I run 'notepad $profile" at the command line and it will autocreate the correct file in the correct location.
This is a super powerful pattern! You can get autocomplete in Git in PowerShell with PoshGit as well as in WinGet!
What are some more obscure autocompletes that you have added to your PowerShell profile?
ACTION: Finally, please take a moment and subscribe to my YouTube or head over to http://computerstufftheydidntteachyou.com and explore! I'd love to hit 100k subs over there. I heard they give snacks.
Sponsor: Suffering from a lack of clarity around software bugs? Give your customers the experience they deserve and expect with error monitoring from Raygun.com. Installs in minutes, try it today!
© 2020 Scott Hanselman. All rights reserved.
