• wheezy@lemmy.ml
      link
      fedilink
      English
      arrow-up
      1
      ·
      6 hours ago

      What’s worse is making a bunch of bash aliases that are easier to remember and then you hit an environment you can’t use your bashrc in for whatever reason. Then you have no idea how to actually do anything.

      I try to only use aliases for things that I repeat often but are only going to be used in my specific environment.

      Unless you mean

      alias ls="ls | sort -V"
      

      Which would be really awful to do for obvious reasons.

      • everett@lemmy.ml
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        5 hours ago

        That example is indeed what I meant. What’s awful about it?

        edit: I use a customized ls alias. Most of the time it’s fine, and when I occasionally need the default output, I can type /bin/ls, no new alias to memorize. The history command suggests I do this pretty infrequently, though ymmv.

        • wheezy@lemmy.ml
          link
          fedilink
          English
          arrow-up
          2
          ·
          39 minutes ago

          ls doesn’t have the version sort option so since you’re aliasing a piped command to sort you’d be passing any additional commands to sort

          So

          ls -r

          Would actually be

          /bin/ls | /bin/sort -V -r

          You could overcome this with xargs but it’s just definitely a bad idea in general to alias a standard command piped into another command. Will cause headaches.

          Where as something like

          ls="/bin/ls -r"
          

          Just defaults ls to a reverse sort and you can still safely add additional args.