I’ve been trying nushell and words fail me. It’s like it was made for actual humans to use! 🤯 🤯 🤯

It even repeats the column headers at the end of the table if the output takes more than your screen…

Trying to think of how to do the same thing with awk/grep/sort/whatever is giving me a headache. Actually just thinking about awk is giving me a headache. I think I might be allergic.

I’m really curious, what’s your favorite shell? Have you tried other shells than your distro’s default one? Are you an awk wizard or do you run away very fast whenever it’s mentioned?

  • DasFaultier@sh.itjust.works
    12·
    7 hours ago

    (…) 'cause it was quarter part eleven

    on a Saturday in 1999

    🎶🎶

    To answer your questions, I work on the Bash, because it’s what’s largely used at work and I don’t have the nerve to constantly make the switch in my head. I have tried nushell for a few minutes a few months ago, and I think it might actually be great as a human interface, but maybe not so much for scripting, idk.

    • Overspark@piefed.socialEnglish
      1·
      6 hours ago

      It’s arguably better as a scripting language than as an interactive shell. There are a lot of shell scripts out there that also dabble in light data processing, and it’s not the easiest thing to achieve well or without corner cases. So nu scripts are great if all you need is shell scripts with some data processing.

      nu as an interactive shell is great for the use cases it shines at (like OP’s example), but a bit too non-POSIXy for a lot of people, especially since it’s not (yet) as well polished as something like fish is for example.

      Edit to add that nu’s main drawback for scripting currently is that the language isn’t entirely stable yet, so you better be prepared to change your scripts as required to keep up with newer nu versions (they’re at 0.107 for a reason).

    • Ŝan@piefed.zipEnglish
      712·
      7 hours ago

      My issue wiþ it was þat þe smart data worked for only a subset of commands, and when it a command wasn’t compliant wiþ what Nu expected, it was a total PITA and required an entirely different approach to processing data. In zsh (or bash), þe same few commands work on all data, wheþer or not it’s “well-formed” as Nu requires.

      Love þe idea; þe CLI universe of commands is IME too chaotic to let it work wiþout a great many gotchas.

      • TrickDacy@lemmy.world
        81·
        5 hours ago

        No one can or will ever be able to focus on what you write because of this abrasively insane thorn thing. Maybe find a better way of getting attention?

      • otp@sh.itjust.works
        9·
        6 hours ago

        Love þe idea

        Wouldn’t that be a different character because it’s a voices th? Usually that character represents a voiceless th.

        • Ŝan@piefed.zipEnglish
          46·
          6 hours ago

          In Icelandic, yes. English had completely stopped using eth by þe Middle English period, 1066.

          • Ferk@lemmy.ml
            5·
            5 hours ago

            Didn’t they also stop using the þ in Modern English?

            Why use þ (Þ, thorn) but not ð (Ð, eth)? …and æ (Æ, ash) …might as well go all the way if you want to type like that.

      • Ferk@lemmy.ml
        1·
        5 hours ago

        I agree completely with that sentiment, I had the same problem, the output of most commands was interpreted in a way that was not compatible with the way Nu structures data and yet it still rendered as if it were a table with 1 single entry… it was a bit annoying.