Hacker News Reader

Its not the filesystem thats the problem, but the terrible partitioned-backslash-ridden namespace. Come on MS, embrace the forward slash already.

View on HN

I haven't noticed the forward slash not working anywhere I need to use paths, from the command prompt and elsewhere.. it doesn't work for tab completion at a command prompt though.

You can always use a bash/cygwin prompt for that if you want.

The forward slash in paths only sort of works but not really. And because you can sort of use forward slash and backslash for paths deliminators you can't escape spaces in path names.

And why did they have to screw up tab completion like that? More like tab cycling. Why does MS always have to be different just for the sake of being different?

MS whole approach to the cli grinds my gears. And Powershell fixes nothing.

You can get bash style completion in PowerShell with https://github.com/lzybkr/PSReadLine.

cd "My Folder Has Spaces/So Does It's Child"

CRLFs instead of just LFs is also annoying.

Reply on news.ycombinator.com