I know what you’re probably thinking. One of the reasons you use Windows is so you don’t have to use the command line. But sometimes it’s unavoidable—maybe you need to do some advanced git-wrangling, or you’re developing in an environment with CLI-based tools that are far more mature than their GUI counterparts. But it doesn’t have to be painful. With a little bit of tweaking, it can even be—dare I say?—more pleasant than a GUI-based experience.
A word of warning: most of the advice that follows only applies to Windows 7 SP1 and up. Proceed at your own risk if you’re running anything earlier.
Let’s be honest. What many people think of as “the default Windows command line”, cmd.exe, is atrociously bad. Selection is awkward, resizing is hard, the syntax is arcane, the list goes on. If you do nothing else, there are two things you can do to make the basic, vanilla experience bearable.
Banish cmd.exe from your shortcuts, and upgrade to it’s successor, PowerShell. It includes a vast array of built in commands (known as Cmdlets) and scripts that support piping between each other, allowing you to compose actions from simple building blocks. If there’s ever anything you’re missing from the old cmd, you can always invoke cmd.exe from PowerShell. There’s also tons of community support, so if there’s something missing out of the box, odds are that somebody has filled that gap already.
And, purely subjectively, I think the .ps1 syntax is a lot more readable than the old .bat syntax.
Upgrade to Windows 10
I know that this one will be a harder pill to swallow (and is likely impossible in some enterprise scenarios) but the benefits really can’t be overstated. ‘conhost.exe’, Windows’ basic console window host that underlies both cmd and PowerShell has seen some pretty substantial improvements. This MSDN article lays out the details, but the high points are as follows:
- Automatic text reflowing on resize
- Ctrl + X/C/V support for cut/copy/paste
- Selection that does line-wrapping
- A full-screen mode
Already on Windows 10? You can enable these features by just right-clicking the console’s title bar and going to Properties. Once there, you’ll want to enable the following in the Options tab:
- Enable Ctrl key shortcuts
- Filter clipboard contents on paste
- Enable line wrapping selection
- Extended text selection keys
then, in the Layout tab:
In addition, Windows 10 also bundles PsReadLine and OneGet (though it calls it PackageManagement), which make the PowerShell experience leaps and bounds better.
PSReadLine gives you a lot of syntax and autocompletion goodies, and I’ll be going into more detail about PackageManagement in a little bit.
Just those two changes will make your command line experience significantly more palatable…but we can go further.
First, lets take care of anybody who can’t upgrade to Windows 10—you can still get a lot of the goodness that follows. You’ll need to do two things to catch up to the Windows 10 default experience. If you’re already on Windows 10, you can skip to to the “Package Management” section.
Install WMF 5.0
Windows Management Framework 5.0 will give you OneGet/PackageManagement (which I’ll be talking about soon, I swear), and enables easy installation of modules from the PowerShell Gallery. We need that second piece because next, we’re going to…
PsReadLine gives you syntax highlighting, context-sensitive autocompletion via Ctrl + Space, supercharged tab-completion and a whole lot more. The project’s Github page has more information, and links to articles of deep dives into it, so check those out if you’re curious. To install it, just make sure that WMF 5.0 is installed, open a PowerShell prompt, and enter:
This is where it starts getting good. If you’ve ever used Debian or any of its derivatives, you’ve probably been a little jealous of apt-get. Well, Windows (finally!) has an answer to that in the form of the PackageManagement module. The project itself is open source, and goes by the name of OneGet.
Why don’t we try it out? Let’s go get the Powershell Community Extensions from the PowerShell Gallery. I happen to know that the name of the package I’m after is “PSCX”, so:
PackageManagement is actually more of a “Package Manager Manager”—it doesn’t provide packages itself, but provides a common interface to other package providers. By default, PackageManagement only has one provider: PowerShellGet, which uses the PowerShell Gallery as its source. In fact, if you installed PsReadLine earlier, you were using PowerShellGet directly with that ‘Install-Module’ call!
That’s pretty neat, but fairly limited in scope. We want a provider that points toward a more general software repository. Fortunately, just such a thing exists, in the form of Chocolatey!
At this point, we have two options—we can install Chocolatey manually, or we can do it through PackageManagement. Unfortunately, the Chocolatey provider for PackageManagement isn’t ready for prime time just yet. It works, but it’s out of date compared to the standalone Chocolatey client, and isn’t recommended. The Chocolatey team hopes to have the PackageManagement provider ready some time this year, but for now, head over to chocolatey.org and follow their instructions to get the standalone client installed.
In Part 2 of this series, we’re going to be leaning on Chocolatey pretty heavily to improve our Git experience, but for now, let’s just take it for a test drive.
You can invoke it with ‘chocolatey’, but brevity is nice, and it responds to ‘choco’ as well.
Now, I always find myself needing a simple, lightweight image editor with a bit more power than Paint. I’m a big fan of Paint.NET, so why don’t we see if we can get it from chocolatey?
C:Usersmcali> choco list paint.net jivkok.dev1 184.108.40.206 kellyelton.devenvironment 220.127.116.11 paint.net 4.0.6 Pinta 18.104.22.16830501 4 packages found.
Yep, there it is!
‘choco list’ does a search of the chocolatey gallery, with an optional search term. You can also ask it to show you locally-installed packages with the ‘–local-only’ or ‘-l’ flag. For example, my work laptop lists the following for locally-installed packages:
C:Usersneilm> choco list -l chocolatey 0.9.9.12 ConEmu 22.214.171.124 DotNet4.5.1 126.96.36.19940606 git 2.7.4 git.install 2.7.4 notepadplusplus 6.9 notepadplusplus.install 6.9 poshgit 0.6.0.20160310 rust 1.7.0 VisualStudioCode 0.10.11 10 packages installed.
Let’s get Paint.NET installed, and see if chocolatey delivers on its promise.
C:Usersmcali> choco install paint.net Installing the following packages: paint.net By installing you accept licenses for the packages. Chocolatey installed 1/1 package(s). 0 package(s) failed. See the log for details (C:ProgramDatachocolateylogschocolatey.log).
In Paint.NET’s case, chocolatey just fires up the .exe installer in silent mode, which then takes over.
But actually, maybe I’ve had a change of heart. I don’t need an image editor after all. Let’s uninstall it:
C:Usersmcali> choco uninstall paint.net Uninstalling the following packages: paint.net paint.net v4.0.6 Skipping auto uninstaller - AutoUninstaller feature is not enabled. paint.net has been successfully uninstalled. Chocolatey uninstalled 1/1 packages. 0 packages failed. See the log for details (C:ProgramDatachocolateylogschocolatey.log).
Note that it hasn’t been completely removed. The package didn’t include a
chocolateyUninstall.ps1, and Chocolatey defaults to the more conservative option, and doesn’t attempt to uninstall it from the system without that script. If you’d rather it were just removed completely, even if the package doesn’t have a dedicated uninstaller, you can set
choco feature enable -n autoUninstaller and it’ll remove everything when you do an ‘uninstall’.
And of course, like any good package manager, Chocolatey can keep your packages updated. Either by name:
choco upgrade paint.net
or all at once:
choco upgrade all
That’s all for now! At the very least, now you’ve got some better syntax highlighting, tab-and-auto-completion, and a nice package manager or two.
Next time, we’ll be talking about better Git integration, and improvements to the actual console experience. Look forward to tabs, splitting your console, and better resize support for non-Windows 10 machines!
Part 2 is now available here!
Original URL: http://feedproxy.google.com/~r/feedsapi/BwPx/~3/iwO6rVVRPMY/a-saner-windows-command-line-part-1