This is a follow up to the previous post on things that trip newbies in Powershell
In this post, I will be concentrating on Encodings. When I began using Powershell, it managed to confuse, trick and irritate me a lot. Encodings issues continue to be problematic with Powershell even in v3.0.
Let me start off with a common enough usage that might come to bite you. Say you have a git repo. You can want to pipe some content to
.gitignore to ignore some files and directories. Easy right?
You can do:
As any git user would know, that should ignore any dll file in your repo. But will it? Go ahead try it out.
a.dll be ignored. Let’s see what’s going on here:
So git is treating the
.gitignore file as a binary. This is where encodings come into the picture.
"*.dll" > .gitignore is pretty much the same as doing
"*.dll" | out-file .gitignore. The default encoding that is used here is
UCS-2. Many tools like git are not happy with it, at least by default.
We have this, from the docs:
By default, the Out-File cmdlet creates a Unicode file. This is the best default in the long run, but it means that tools that expect ASCII files will not work correctly with the default output format. You can change the default output format to ASCII by using the Encoding parameter
To make git happy, you can convert the
.gitignore file to, say
ascii. Actually, the
out-file cmdlet provides ability to do just that.
Now, the dlls should be ignored as expected. Unfortunately, there is no way to change how
> behaves in this aspect!