Fuck it, .zshrc it is.

Image transcription:

  • Top text: I STILL DON’T KNOW WHAT SHOULD GO IN .*RC VERSUS .*PROFILE
  • Bottom text: AND AT THIS POINT I’M AFRAID TO ASK
  • bigredgiraffe@lemmy.world
    link
    fedilink
    arrow-up
    71
    arrow-down
    1
    ·
    4 months ago

    I found this diagram on SO at one point but I can’t find the post and it is the best explanation I have found for how all of the files work for bash and zsh, each color is an individual path of execution (eg, follow the red line).

    Bottom line though, it only really matters if you are overriding something that is already defined, for example I tell my users to use zshrc and I provide defaults and common things in zprofile because zshrc is executed last when they login.

    • JackbyDev@programming.devOP
      link
      fedilink
      English
      arrow-up
      48
      ·
      4 months ago

      I feel like I couldn’t make this more confusing if I tried. What is doing on with the golden arrows around /etc/profile??

      • AggressivelyPassive@feddit.de
        link
        fedilink
        arrow-up
        35
        ·
        4 months ago

        That’s decades of legacy for you…

        I bet each step/arrow/decision had a good reason at some point, but most of them probably back when computers lived in caves and hunted their tapes using spears and rocks.

        I feel like we’re slowly reaching a point where the complexity is collapsing in on itself - just look at the absolute chaos a modern web app is.

      • Gamma@programming.dev
        link
        fedilink
        English
        arrow-up
        11
        ·
        edit-2
        4 months ago

        Select the color which matches the steps before filenames ((non-)login and (non-)interactive), then follow that arrow the rest of the way. There’s more colors in Bash because Bash makes a distinction between remote and local shells.

        Another way to look at the same data for Zsh (note: $ZDOTDIR will be used instead of $HOME if it’s defined at any step along the way):

        File neither interactive login both
        /etc/zshenv x x x x
        ${ZDOTDIR:-$HOME}/.zshenv x x x x
        ${ZDOTDIR:-$HOME}/.zprofile x x
        ${ZDOTDIR:-$HOME}/.zshrc x x
        ${ZDOTDIR:-$HOME}/.zlogin x x
        ${ZDOTDIR:-$HOME}/.zlogout x x

        One confusion on the Bash side of the diagram is that you see branching paths into ~/.profile, ~/.bash_profile and ~/.bash_login. Bash will use for ~/.bash_profile, ~/.bash_login, and ~/.profile, in that order, and execute only the first one that exists and is readable.

        • JackbyDev@programming.devOP
          link
          fedilink
          English
          arrow-up
          3
          ·
          4 months ago

          And what’s confusing is that many times those files still manually call the others to make it more logical like zsh. That’s what I remember at least, it’s been quite a while since I used bash.

          • Gamma@programming.dev
            link
            fedilink
            English
            arrow-up
            4
            ·
            4 months ago

            manually call the others

            Yeah, most distros will set up source chains to make things nicer for users.

    • mumblerfish@lemmy.world
      link
      fedilink
      arrow-up
      4
      ·
      edit-2
      4 months ago

      Is this a diagram for how it should work? Not how it actually works? Like I put my stuff in the ~/.bashrc, mostly because I think the debian one says like “put your fun stuff below here” or something. The green and grey lines go through the ~/.bashrc, but both of them go through the “no login” bubble in the diagram. But I know my ~/.bashrc works, so the diagram is a suggestion?

      • JackbyDev@programming.devOP
        link
        fedilink
        English
        arrow-up
        2
        ·
        4 months ago

        A lot of systems will call various inits from others to give you a more simplified flow. (Closer to what zsh does.) Check out some of those files in /etc/ it is calling as well as ~/.bash_profile. Or, you might not even be in a login shell!