What happens when you open a terminal and enter `ls’

Re:What happens when you open a terminal and enter `ls’ by analog31 on Wednesday January 11, 2023 @06:42PM (#34346744)

    ls is not recognized as an internal or external command,
    operable program or batch file.

;-)

[ Parent | on HN ]

Re:What happens when you open a terminal and enter `ls’ by szgupta on Wednesday January 11, 2023 @06:48PM (#34346814)

Haha, yeah we probably should have added a caveat that this is only applicable to Unix

[ Parent | on HN ]

Re:What happens when you open a terminal and enter `ls’ by analog31 on Wednesday January 11, 2023 @06:51PM (#34346845)

I assumed so, but then I got curious what would happen in a DOS window.

[ Parent | on HN ]

Re:What happens when you open a terminal and enter `ls’ by kkielhofner on Wednesday January 11, 2023 @08:30PM (#34347859)

Thankfully it works in Powershell on Windows. I lost any muscle memory for `dir` a long long time ago.

[ Parent | on HN ]

Re:What happens when you open a terminal and enter `ls’ by waste_monk on Thursday January 12, 2023 @10:33PM (#34363649)

Until you hit something like "Get-ChildItem : A parameter cannot be found that matches parameter name 'lh'" and are jarringly reminded that this is not your old friend `ls` after all.

[ Parent | on HN ]

Re:What happens when you open a terminal and enter `ls’ by JdeBP on Friday January 13, 2023 @10:18PM (#34377064)

This is why, if I use a shorthand in PowerShell at all, I avoid using "dir", "ls", and the like. "gci" is at least not like any common Unix/BSD/PC-DOS/Windows/OS/2 command.

[ Parent | on HN ]