• TheChefSLC@lemmy.sdf.org
      676·
      1 year ago

      Yes, yes you can.

      Also, WSL and windows terminal go a very long way in making windows actually usable…

      • UndefinedIsNotAFunction@programming.dev
        71·
        1 year ago

        I really want to love the “everything is an object” of power shell but I just have zero uses for using a shell on windows. Granted, my windows usage is like 15 minutes a week most of the time, but still. I also can’t be bothered to use it for work because it’s exclusively Linux/linux-ish over there so it’s not worth bothering.

        Either way, I like the idea, can’t really justify figuring out the details.

        • DV8@lemmy.world
          4·
          1 year ago

          If you only have to use it 15 minutes every week it’s probably not worth getting to know.

          I work in a Windows shop, so I love everything being an object, most of the time. At least for the things that are worked out completely.

          It’s great for things you need to iterate or just for figuring out what you can do by piping a result to get-member. If you are interested in getting better at powershell at some point, I highly recommend Powershell in a month of lunches. (Also because I like Manning’s model where they automatically offer the digital versions of books they sell, and also offering free previews of the entire book, given enough time)

        • ______@lemm.ee
          2·
          1 year ago

          “But PS is open source ! Don’t you want to use it in Linux and MacOS?” - Microsoft probably

          • wizardbeard@lemmy.dbzer0.comEnglish
            1·
            1 year ago

            It’s a wonderful tool for me in a Windows environment/shop, especially with how it works well with all the Windows and Microsoft administration systems/tools we use.

            Personally, I’m less interested in any language’s hypothetical merits than how it fits as a tool for what I need to accomplish and ease of future maintenance when the script/program/automation inevitably needs to be adjusted.

            All that said, I can’t think of a legitimate reason to use PSCore on non-Windows hardware unless you’re just really familiar with PS and literally nothing else. Even then you’re better off taking time learning a better tool for that environment.

            • ______@lemm.ee
              2·
              1 year ago

              That’s a very good point. My angle is as a dev and not as IT or sys admin. Power shell is probably far more powerful in those circles.

    • ox0r@jlai.luEnglish
      252·
      1 year ago

      Yeah but tbh i really despise powershells syntax. But i’m happy it is pretty powerful.

      • affiliate@lemmy.world
        36·
        1 year ago

        i’m often amazed at microsoft’s ability to take a useful product and make it agonizing to use

          • ______@lemm.ee
            82·
            1 year ago

            I hope I didn’t come across as defending ps. PS sucks and whoever decided to have functions use capital case with dashes in between needs to have their brain scanned

            • wizardbeard@lemmy.dbzer0.comEnglish
              3·
              1 year ago

              I do a lot of work in PS and I don’t find it that bad. But you forgot what’s even dumber about their function naming conventions.

              Function names are supposed to be a single word verb, then the dash, then the rest. But not any verb, you’re supposed to use one from PS’s list of acceptable ones which has some really weird omissions. And they break their own single word verb convention with “acceptable verbs” ConvertTo and ConvertFrom (ConvertTo-SecureString, ConvertFrom-Json), which are the only exception to one word verbs before the dash.

              Function names are definitely one of my biggest peeves with it.

              Additionally, their basic comparison operators are dumb as hell. How is “-le” better or clearer in meaning that “<=”? -ne instead of !=, but == isn’t just -e, it’s -eq. And you can’t slap an n in front of other comparators for not, -nle isn’t a thing. You gotta wrap the whole comparison in parentheses and slap an ! on the front or slap -not in front. But don’t try to do !-le, because that’s also not a thing. It’s not terrible but I refuse to believe that -eq is more readable than ==

              • ______@lemm.ee
                2·
                1 year ago

                Functionally speaking, PS is a really good shell language. Its minor things about it that I dont enjoy. As you said, it feels like the language design has some poor decisions.

  • voxel@sopuli.xyz
    391·
    1 year ago

    use powershell (specifically the core version!!!), or even better something like Nu shell

  • over_clox@lemmy.world
    31·
    1 year ago

    echo @dir %1 %2 %3>%windir%\system32\ls.bat

    Something like that should fix the problem, I think…

        • hemko@lemmy.dbzer0.comEnglish
          4·
          1 year ago

          Not gonna lie I love easily readable scripts. Powershell was my first, and as much pain it can be it’s for sure readable even for the most novice.

          Maybe that’s why I love Python too, but have hard time learning sh past very basics…

          Edit: oh lol that’s a fork bomb, curiosity won and had to ddg what that is. Love the simplicity of that

    • stevedidWHAT@lemmy.worldEnglish
      11·
      1 year ago

      I’m gonna take it a step further and say to use the new Terminal app from the winapp store which lets you integrate ALL command lines into one app and it looks snazzy to boot!

      Check it out mother fuckers!

      • SpaceCowboy@lemmy.ca
        11·
        1 year ago

        Yeah powershell is better 95% of the time. But that other 5% of the time you have to go back to CMD and redo what you were attempting. So the work done in powershell is a waste of time 5% of the time, and you still will need to know CMD to be able make everything work.

        So Powershell is better in theory, but in actual practice I tend to do things in CMD because I know it will work.

        • sznio@lemmy.world
          3·
          1 year ago

          I really like PowerShell’s object-oriented approach to pipelines. Unix pipes feel really dated in comparison.

  • mateomaui@reddthat.comEnglish
    1132·
    1 year ago

    What year is this from? You absolutely can use ls in a windows command prompt now.

    • captsneeze@lemmy.one
      681·
      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.comEnglish
        81·
        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
          1·
          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.comEnglish
            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
        31·
        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.comEnglish
          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
          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
        1016·
        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
            11·
            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
          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
            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.comEnglish
              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.

    • ShortFuse@lemmy.world
      1·
      1 year ago

      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 logoff don’t work.