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
this post was submitted on 18 Jul 2024
268 points (98.6% liked)
Programmer Humor
19512 readers
324 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
I feel like I couldn't make this more confusing if I tried. What is doing on with the golden arrows around
/etc/profile??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.
I was referring more to the graphical representation that the actual flows.
Agreed! It's cathartic to see it laid out so terrifying. Now I feel less bad for never understanding it.
What do the differently coloured arrows mean? I'm confused.
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:
$ZDOTDIRwill be used instead of$HOMEif it's defined at any step along the way):/etc/zshenv${ZDOTDIR:-$HOME}/.zshenv${ZDOTDIR:-$HOME}/.zprofile${ZDOTDIR:-$HOME}/.zshrc${ZDOTDIR:-$HOME}/.zlogin${ZDOTDIR:-$HOME}/.zlogoutOne confusion on the Bash side of the diagram is that you see branching paths into
~/.profile,~/.bash_profileand~/.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.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.
Yeah, most distros will set up
sourcechains to make things nicer for users.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?
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!Here's the seemingly original source for those who like to know.