Nushell
www.nushell.sh
A new type of shell.
  • dylanmorgan@slrpnk.net
    10·
    1 year ago

    This may be the wrong place to ask, but what am I missing about shells? Other than executing commands, what do you do with them?

    • TiphaineRupa@feddit.de
      11·
      1 year ago

      Many Linux users spend a considerable amount of time using the command line interface, so the right shell configuration can make them much more productive.

    • hallettj@beehaw.orgEnglish
      10·
      1 year ago

      I think the best way to get an idea is to look at feature lists for fancy shells like zsh or fish. But in short there are a number of things a good shell can do to help to execute commands faster and more easily. Stuff like autocompletions which make you faster, and also make things more discoverable; fuzzy searching/matching; navigating command history; syntax highlighting which helps to spot errors, and helps to understand the syntax of the command you’re writing.

      • Tin@beehaw.org
        3·
        1 year ago

        I use fish mainly just for the quality of life increase that its predictive features and command history give. I also really like that it uses functions to play the role of aliases, and it’s super easy to write and save new functions on the fly.

        That said… I haven’t put in the time to really learn its nuances and I still write shell scripts using bash. Maybe I’m doing it wrong, but it works for me.

    • SWW13@lemmy.brief.guru
      2·
      1 year ago

      You can do most things by combining simple cmdline tools. E.g. filter out some specific lines from all files in a directory, get the value after the second :, write those to another file and then sort, deduplicate and count them.

      This may sound complicated, but it’s pretty easy and fast if your are familiar with a shell. To be that efficient with your shell you want it to actually be powerful and not just a plain text input. Also writing cmdline tools is rather easy compared to a usable GUI tool.

      • smeg@feddit.ukEnglish
        1·
        1 year ago

        Genuine question: why not use grep, awk, sed, or any of the other gnu tools that can already do that?

        • SWW13@lemmy.brief.guru
          1·
          1 year ago

          That’s what I meant, using your shell to run command line tools to solve your issue at hand. And having a powerful shell with e.g. context dependend autocomplete (and a lot more) helps to speed up that task.

        • colournoun@beehaw.org
          1·
          1 year ago

          You could, but maybe a good shell makes it easier than the external tool. Or maybe you use the shell to effectively combine the inputs and outputs of the other tools.

          • smeg@feddit.ukEnglish
            1·
            1 year ago

            I guess that’s convenient if you’re only ever on one machine, I prefer commands that work (almost) everywhere!

            • colournoun@beehaw.org
              2·
              1 year ago

              Me too. I could never get into nushell or fish because they’re not posix and I don’t need to learn two ways to do something.

  • hallettj@beehaw.orgEnglish
    5·
    1 year ago

    Well I might be hooked. It didn’t take me long to reproduce the niceties in Nushell I’m used to from my zsh config. Some of the important parts were setting up zoxide with a key binding for interactive mode, switching on vi key bindings, setting up my starship prompt.

    Home Manager is preconfigured for the above integrations which made things easier.

    One feature that is missing that I like to use is curly brace expansion to produce multiple arguments. For example,

    $ mv *.{jpg,jpeg}

    Unless there is a way to do something like this in Nushell that I haven’t seen yet?

    Something I enjoyed was automating a sequence of steps I’ve been running a lot lately due to a program that often partially crashes,

    def nkill [name_substring] {
  ps | where name =~ $name_substring | each { |p| kill $p.pid; $p }
}

    I realized after writing this that I basically recreated killall -r. But it’s nice that it was so easy to make a custom command to do a very specific thing. And my version gives me a nice report of exactly what was killed.

    Thanks for making this post OP! When I’ve heard mentions of Nushell I’m the past I think I conflated it with Powershell, and wrote it off as a Windows thing. (Maybe because it’s introduced as being “like Powershell”.) But now that I see that it’s cross-platform I’m enjoying digging into it!

    • FUsername@feddit.de
      2·
      1 year ago

      …so you’re locked in ever since? 🤪 Is it a serious case of Stockholm Syndrome or do you like it?

      • eric@lemmy.caEnglish
        2·
        1 year ago

        My workflow works the best in bash/zsh shells. Shells that are too different are too much of a change. I like fish as well. Probably a touch of Stockholm Syndrome too haha

  • TiphaineRupa@feddit.de
    2·
    1 year ago

    Definitely an interesting project especially for those Linux users that mostly stick to one machine and like to experiment with new features.
    For the regular sys admin type of person that needs to jump from one Maschine to another it’s probably a little too non-standard and hard to get productive with

  • Hawk@lemmynsfw.com
    1·
    1 year ago

    If you want something more Unix like and less PowerShell (but absolutely not POSIX), checkout Elvish.