Ok, getting past the dickish, completely unhelpful first part of your reply (as you can see in the comments, not EVERYONE was saying that), the second part helped me trace it back to this:
which is a toolset that I never intentionally installed, and was evidently added by an emulator package without me knowing where it was or what it did.
So thank you for (eventually) helping me find what it was, and now you and others know how to add it to cmd and don’t have to complain about its absence.
Probably using Powershell, or you added it. Ls definitely doesn’t work in windows 10 or 11 in cmd.
No it works in cmd. I didn’t add it intentionally atleast. Never even tried to use it till now.
Bone stock windows 11. It isn’t, and has never been in cmd.
deleted by creator
I’m still confused.
Bone stock windows 11. Like I have everyone else has said, you have done something to add it to cmd. It isn’t, and has never been in cmd.
EDIT:
Try this. in CMD type in
where LSE:\>where ls f:\Git\usr\bin\ls.exeMystery solved
Ok, getting past the dickish, completely unhelpful first part of your reply (as you can see in the comments, not EVERYONE was saying that), the second part helped me trace it back to this:
https://github.com/devkitPro/installer/releases
which is a toolset that I never intentionally installed, and was evidently added by an emulator package without me knowing where it was or what it did.
So thank you for (eventually) helping me find what it was, and now you and others know how to add it to cmd and don’t have to complain about its absence.