• captsneeze@lemmy.one
    link
    fedilink
    arrow-up
    30
    ·
    2 years ago

    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.

    • mateomaui@reddthat.com
      link
      fedilink
      English
      arrow-up
      8
      arrow-down
      1
      ·
      edit-2
      2 years ago

      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.

      • captsneeze@lemmy.one
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        2 years ago

        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?

        • mateomaui@reddthat.com
          link
          fedilink
          English
          arrow-up
          1
          ·
          2 years ago

          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.

    • icesentry@lemmy.ca
      link
      fedilink
      arrow-up
      3
      arrow-down
      1
      ·
      2 years ago

      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.

      • mateomaui@reddthat.com
        link
        fedilink
        English
        arrow-up
        2
        ·
        2 years ago

        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.

      • captsneeze@lemmy.one
        link
        fedilink
        arrow-up
        1
        ·
        2 years ago

        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.