• captsneeze@lemmy.one
    link
    fedilink
    arrow-up
    67
    arrow-down
    1
    ·
    1 year 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
      7
      arrow-down
      1
      ·
      edit-2
      1 year 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
        1 year 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
          ·
          1 year 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
      ·
      1 year 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
        ·
        1 year 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
        ·
        1 year 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.

    • CaptPretentious@lemmy.world
      link
      fedilink
      arrow-up
      11
      arrow-down
      17
      ·
      1 year ago

      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.

        • CaptPretentious@lemmy.world
          link
          fedilink
          arrow-up
          1
          arrow-down
          1
          ·
          1 year ago

          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.

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

        That is a fair statement, but also a different topic.

        I am thankful to live in an age with WSL.

        • CaptPretentious@lemmy.world
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          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?

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

            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.