1. 14
  1.  

  2. 6
    alias filesize='ls --size --human-readable -1'
    

    May I suggest du -h?

    1. 1

      Thanks for the feedback. This was mainly an artefact from the first chapter, where we started with ls and then experimented with options, long and short. du -h is the “right” command for this indeed. I removed the alias. Thanks again!

    2. 5

      For the terminal, I cannot recommend enough Alacritty. Although it’s still beta, I’ve never had any issues with it. The yaml configuration is just perfect, it supports everything I need, and has been super nice in term or rendering speed.

      1. 1

        Interesting! And I guess if you need to have tabs and panes in your alacritty terminal, you use something like tmux do to this ?

        1. 1

          Why not just have multiple terminals open?

          1. 1

            I guess it’s just a habit of mine. I run gnome-shell which does not have a very good window tiling story.

            Edit: Oh and also I like the fact that splitting a terminal pane in 2 places you in the same directory. This way you can easily add more panes for the same project without having to cd to the project directory. I guess the workflow just grew on me.

            1. 1
              1. With screen/tmux I can have several sessions, with a very specific layout for each project, and switch to each of them easily.
              2. The organization of windows like my panes are setup, would require a tilling window manager, which I would use only for terminals.
              3. Having the same setup at work (macOS) and at home (nix) with a simple config file.

              And probably many other reasons that I don’t have from the top of my head.

              1. 1

                I understand the appeal of tmux, even if 99% of my usage has only been to detach a terminal. I was asking because I wondering why you needed terminal-emulator tiling.

            2. 1

              Yes. I personally use tmux.

              If you’re using tabs and splits from your terminal, I think taking the time to transition to tmux has some benefits, for not a lot of work.

              1. 1

                Yep, I have actually been playing with it server-side. I find myself using it more and more now that I’m happy with my config. Thanks for the feedback!

          2. 2

            So, I’m reading his section on Terminals, and he mentions running Terminator on Linux and iTerm2 on Mac, which has always been my choice. Lately I’ve been doing a lot of work on Terminator (see below) and I’ve actually gotten it to work on my mac. I’m working out the bugs up and down the stack ( one problem ended up being a bug in the quartz backend of GTK) but I’m hoping to have support for Mac integrated for the next major release.

            I’m also a Fedora co-maintainer for Terminator and along with the debian maintainer, we’re about to release v1.92 which will finally migrate to python3, after many years of no updates.

            1. 1

              Oh that’s great to hear! As a long-time Terminator user (8 years I think?), thank you for the work!

            2. 1

              As a person who manages many corporate systems, I actually try very hard not to customize my shell environment too much. Once you commit that super handy custom shell alias or vim key binding to muscle memory, you’ll find yourself trying to use it everywhere, which leads to frustration.

              But if I was a developer who rarely left the comfort of localhost, sure, I’d customize the crap out of everything.

              1. 3

                FWIW it’s relatively easy to package up basic config and ship it over when you SSH into a system, so there’s no reason you can’t bring some conveniences with you. There’s stuff like xxh. I just use this small script to send a basic bash config around.

                1. 1

                  Oh absolutely. The whole premise of the article is that you are able to mirror your customization everywhere. As this article was mainly targetting newcomers, I was assuming one computer, or maybe 2. I could make this more explicit, and state that you don’t have to customize if we can’t or don’t want to.

                  1. 1

                    That’s only true for a part of the corporate world. You might be in charge of deploying the bash config ;)

                    Only half-joking, in my last company I sat down and created a minimal, but useful .bash_aliases that we just deployed to every machine as part of the general updates, including nice prompts and different colors per data center/staging/prod.

                    Nothing fancy, just some common stuff that even some distros have been shipping for a while, and some defaults, also a better vim color scheme.