Vim filters are cool. They let you run the content of your current buffer through a command and have its output returned into the bugger. That means that you can use filters to edit text using any command your operating system has available.
Now on a Linux machine that’s quite handy. On a Windows machine that isn’t so handy, because the default shell is CMD and that doesn’t have all those handy Unix text manipulating utilities. But what about a PowerShell script that would encode or decode a URL for example?
It turns out that wasn’t as easy as I expected, so I’ll spill it here in case you’re looking to do something similar.
First calling the script from Vim means you have to call
powershell.exe because by default Vim uses
cmd.exe as its shell. That isn’t so hard:
nnoremap <Leader>dc :%!powershell.exe -noprofile -nologo -file c:\tools\decode-string.ps1<CR> nnoremap <Leader>ec :%!powershell.exe -noprofile -nologo -file c:\tools\encode-string.ps1<CR>
I create 2 shortcuts here to encode (ec) and decode (dc) trigger using the leader key.
These will pipe the content of your buffer through the script, and get whatever it spits out through the standard output back into your buffer.
The extra command line parameters I pass into
powershell.exe are to make it as fast as possible and not do any unnecessary junk. The
-noprofile is the most important one as this skips loading any special modules you have set up in your PowerShell profile.
Reading from the pipe in a PowerShell script wasn’t as easy as I thought. Using the
ValueFromPipeline attribute on the input parameter didn’t work for some reason. After some searching I came across a magical
$input parameter that gets anything you receive from standard input for use in your script. Handy.
So the script was as simple as doing this:
[Reflection.Assembly]::LoadWithPartialName("System.Web") | Out-Null [System.Web.HttpUtility]::UrlEncode($input)
What do we do when PowerShell can’t help us out of the box? That’s right. We summon the powers of .NET assemblies to get the job done. In this case, we’re summoning
System.Web and using the
HttpUtility class to encode the incoming data.
We do exactly the same to decode text by the way:
[Reflection.Assembly]::LoadWithPartialName("System.Web") | Out-Null [System.Web.HttpUtility]::UrlDecode($input)
This is pretty powerful. By using the
$input variable in PowerShell together with the Vim filter function, you can do all sorts of text transformations. This can make your developer life a lot easier.