4 ms·
PowerShell takes some time to grok, but once you get it it has very deep integration with Windows systems, and can become a joy to work with. That being said,
by badloginagain 6y ago
PowerShell takes some time to grok, but once you get it it has very deep integration with Windows systems, and can become a joy to work with.
That being said, I still feel violated every time `ls` returns `bad command or filename`
- ooboe 6y agoAre there different versions of PowerShell? 'ls' has always worked for me. 'ls -al' does not however, and that does feel a bit violating.
- JamesSwift 6y ago`ls` is an alias on windows systems. I dont remember what the command maps to, but it maps to something. Same thing with a lot of others (e.g. cat is an alias for Get-Content)
- ksaj 6y agoYou could always make aliases. For example, ls would be 'wsl ls' to run the ls command from Linux instead of searching down the Windows exec path for it. Also, I noticed at least my version of powershell actually has a built in 'ls'. It isn't quite the same as 'wsl ls' but it does show results more appropriate for Windows file systems.