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?

  • Ferk@lemmy.ml
    0·
    2 days ago

    It’s not only clusters… I have my shell configuration even in my Android phone, where I often connect to by ssh. And also in my Kobo, and in my small portable console running Knulli.

    In my case, my shell configuration is structured in some folders where I can add config specific to each location while still sharing the same base.

    Maybe not everything is general, but the things that are general and useful become ingrained in a way that it becomes annoying when you don’t have them. Like specific shortcuts for backwards history search, or even some readline movement shortcuts that apparently are not standard everywhere… or jumping to most ‘frecent’ directory based on a pattern like z does.

    If you don’t mind that those scripts not always work and you have the time to maintain 2 separate sets of configuration and initialization scripts, and aliases, etc. then it’s fine.

    • nimpnin@sopuli.xyz
      0·
      2 days ago

      those scripts not always work

      This feels like ragebait. I have multiple devices, use fish whenever that can be installed and zsh/bash when not, and have none of these issues.

      EDIT:

      or some methods to jump to most recent directory like z.

      Manually downloading the same shell scripts on every machine is just doing what the package manager is supposed to do for you. I did this once to get some rust utils like eza to get them to work without sudo. It’s terrible.

      • Ferk@lemmy.ml
        1·
        2 days ago

        Manually downloading the same shell scripts on every machine is just doing what the package manager is supposed to do for you

        If you have a package manager available, and what you need is available there, sure. My Synology NAS, my Knulli, my cygwin installs in Windows, my Android device… they are not so easy to have custom shells in (does fish even have a Windows port?).

        I rarely have to manually copy, in many of those environments you can at least git clone, or use existing syncing mechanisms. In the ones that don’t even have that… well, at least copying the config works, I just scp it, not a big deal, it’s not like I have to do that so often… I could even script it to make it automatic if it ever became a problem.

        Also, note that I do not just use things like z straight away… my custom configuration automatically calls z as a fallback when I mistype a directory with cd (or when I intentionally use cd while in a far/wrong location just so I can reach faster/easier)… I have a lot of things customized, the package install would only be the first step.

        • nimpnin@sopuli.xyz
          1·
          2 days ago

          So you’re willing to do a lot of manual package managing, in general put a lot of work into optimizing your workflow, adjusting to different package availability, adjusting to different operating systems…

          …but not writing two different configs?

          That is your prerogative but you’re not convincing me. Though I don’t think I’ll be convincing you either.

          I have separate configs/aliases/etc for most of my machines just because, well, they are different machines with different hardware, software, data, operating systems and purposes. Even for those (most) that I can easily install fish on.

          • Ferk@lemmy.ml
            1·
            2 days ago

            It’s actually the lazy way. I only work once, then copy that work everywhere. The copying/syncing is surprisingly easy. If that’s what you call “package management” then I guess doing “package management” saves a lot of work.

            If I had to re-configure my devices to my liking every time I would spend way too much time. I don’t want to… I configured it once already, so I want to be able to simply copy it over easily instead of re-writing it every time for different systems.

            If someone does not customize their defaults much or does not mind re-configuring things all the time, I’m sure for them it would be ok to have many many different shells, maybe one on each device… but that’d be more work than working once and copying it.

            Coincidentally, I do have a fish config. I just don’t use it because most devices don’t have fish… and fish does not personally offer me something of enough value, so my fish config is very barebones and it’s not as well crafted as the POSIX/bash one which gets used much more.

            • nimpnin@sopuli.xyz
              1·
              1 day ago

              I only work once, then copy that work everywhere.

              Good that works for you. If only my needs were so simple that the configs could be same on each machine.

              paljastus

              I know that’s an insufferable way to put it but holy shit have you been like that too.