For those of you playing the Powershell home game, searching recursively for something might've been troublesome. In command and cmd, you might've done something like this:
dir /s partial_file_name*
And then called it a day. Microsoft thought that was too easy, so they removed the ability to just search from where you're at and move down the various directories. You now have to specify where to start from.
get-childitem 'starting_path' partial_file_name* -recurse
dir -r 'starting_path' partial_file_name*
The reason this is important is because Powershell has the ability to browse network shares without mapping a network drive. You can browse completely by UNC path. So in my case I can get to my file server, Codex, and it's file share Fileworld like so.
PS C:\Users\mbelle> cd \\codex\fileworld
PS Microsoft.PowerShell.Core\FileSystem::\\codex\fileworld> dir -r '.\Mykie Docs' wowauth.txt
And oh look, there's the text file with my WoW authenticator code. The command prompts are comical at first, and irritating as balls when you look at them for more than a second.
And finally, no. Microsoft STILL has not figured out how to make a terminal window dynamically resizable.