‘Cmd’ is to ‘horse and buggy’ as ‘powershell’ is to ‘automotive vehicle’
Have no idea where you decided to pull this 100mph idea from. It wasn’t a comment about speed, it was a comment about utilizing modern practices and tools. And that the joke falls apart because it’s forcing the narrative all windows has is cmd and blatantly ignoring pwsh. It be me like making a joke how linux can’t do wifi… because there was a time Windows did wifi just fine but linux required using a special process using an ndiswrapper with windows drivers to get linux on wifi… so like 16-17 years ago. See, hilarious.
What? Ignoring the out of date, over used, ‘gottem’, phrase… it literally doesn’t make sense given the context. I’m advocating for modern tools… how is that a ‘boomer’ move?
I ended it with a question mark because I was uncertain but otherwise your asinine, dismissive statement sounds like something a jackass who’s been around too long would say because he’s entirely too full of himself. I’m willing to recognize that it’s actually ignorance formed out of youth. Don’t think about it too hard.
That is interesting. I just remoted into 5 different machines at the office and none of them worked with ‘ls’. If you enter ‘ls /?’, does it give you a synopsis and argument list?
If I do “ls /?” it returns no such file or directory, but just “ls” performs exactly as you’d expect. I haven’t installed anything to provide that function that I know of. It never occurred to me that I would have to because as far as I know it’s always worked. Until today I just assumed it had become a standard command and never investigated. Was just happy I could use the same command in cmd and on my Pi box.
Lately I’ve been using it as a simple way to drag and drop a source .tar.xz archive on a .bat file so it can be twice extracted, moved, renamed, have dependencies downloaded by git, run a cmake process, do a visual studio compile, then move the result release directory back to where the .bat file is while removing unneeded files and adding new ones.
It’s my own fault, and the result of 30+ years of muscle memory building up. Plus, while I agree cmd isn’t nearly as powerful as powershell or wsl can be, when I’m in Windows it’s still the fastest way for me to do 90% of the simple things I need to do. I have a long history with it, and a thorough understanding of it, so I don’t really need to think for most of the things I’m doing there.
If I need to script something, or do anything that seems like it would be annoying to do in CMD, I hop into WSL pretty quickly and get to work with bash or python. The problem I have now is that I’ve developed a little muscle memory there as well… hence my issue with entering ‘ls’ everywhere.
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.
What year is this from? You absolutely can use ls in a windows command prompt now.
As of Aug 26, 2023, Windows command prompt absolutely does not recognize “ls” as a command.
Powershell is a different story.
Source: I type “ls” 40 times a day into a command prompt on my up-to-date win10 PC at work.
The year is 2023, if you’re still using CMD or batch files still that’s on you. It’s like riding a horse down a freeway and yelling at cars.
Sometimes you just need a quick ipconfig or nslookup, or a simple scheduled shutdown /s /f /t 00
You can still do those in PowerShell. Just saying.
Yeah, but it’s muscle memory at this point
Win+r
Cmd
Ipconfig
Gonna take some time to get my hands to type wt instead of cmd
Win+X i ipconfigdeleted by creator
That wasn’t the conversation.
‘Cmd’ is to ‘horse and buggy’ as ‘powershell’ is to ‘automotive vehicle’
Have no idea where you decided to pull this 100mph idea from. It wasn’t a comment about speed, it was a comment about utilizing modern practices and tools. And that the joke falls apart because it’s forcing the narrative all windows has is cmd and blatantly ignoring pwsh. It be me like making a joke how linux can’t do wifi… because there was a time Windows did wifi just fine but linux required using a special process using an ndiswrapper with windows drivers to get linux on wifi… so like 16-17 years ago. See, hilarious.
ok boomer?
What? Ignoring the out of date, over used, ‘gottem’, phrase… it literally doesn’t make sense given the context. I’m advocating for modern tools… how is that a ‘boomer’ move?
I ended it with a question mark because I was uncertain but otherwise your asinine, dismissive statement sounds like something a jackass who’s been around too long would say because he’s entirely too full of himself. I’m willing to recognize that it’s actually ignorance formed out of youth. Don’t think about it too hard.
That is a fair statement, but also a different topic.
I am thankful to live in an age with WSL.
deleted by creator
I literally just typed it into cmd.exe on Windows 10, fully updated, and it absolutely did work. No idea why it doesn’t work for you.
edit: ???
edit: it’s been traced back to this:
https://github.com/devkitPro/installer/releases
which is an emulator toolset that I didn’t know existed on my system until today.
Lmao
That is interesting. I just remoted into 5 different machines at the office and none of them worked with ‘ls’. If you enter ‘ls /?’, does it give you a synopsis and argument list?
Mystery solved, ls works for me due to this:
https://github.com/devkitPro/installer/releases
which is a toolset that was installed by an emulator package somewhere along the line, I just didn’t know it was there.
Thanks for letting us know!
If I do “ls /?” it returns no such file or directory, but just “ls” performs exactly as you’d expect. I haven’t installed anything to provide that function that I know of. It never occurred to me that I would have to because as far as I know it’s always worked. Until today I just assumed it had become a standard command and never investigated. Was just happy I could use the same command in cmd and on my Pi box.
Out of curiosity what do you do to frequently end up with cmd? I don’t think I’ve touched it in many years at this point.
Lately I’ve been using it as a simple way to drag and drop a source .tar.xz archive on a .bat file so it can be twice extracted, moved, renamed, have dependencies downloaded by git, run a cmake process, do a visual studio compile, then move the result release directory back to where the .bat file is while removing unneeded files and adding new ones.
cmd and batch still has its uses.
It’s my own fault, and the result of 30+ years of muscle memory building up. Plus, while I agree cmd isn’t nearly as powerful as powershell or wsl can be, when I’m in Windows it’s still the fastest way for me to do 90% of the simple things I need to do. I have a long history with it, and a thorough understanding of it, so I don’t really need to think for most of the things I’m doing there.
If I need to script something, or do anything that seems like it would be annoying to do in CMD, I hop into WSL pretty quickly and get to work with bash or python. The problem I have now is that I’ve developed a little muscle memory there as well… hence my issue with entering ‘ls’ everywhere.
I can’t remember doing anything and “ls” works for me
Probably using Powershell, or you added it. Ls definitely doesn’t work in windows 10 or 11 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.
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.
It works on Powershell but not with CMD.
That’s a problem when using NeoVim on windows
Yes in Windows Server since, IIRC, 2012". No in Windows client versions.
I’m so used to Server commands I sometimes am surprised when commands like
logoffdon’t work.