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
You must log in or register to comment.
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):File neither interactive login both /etc/zshenvx x x x ${ZDOTDIR:-$HOME}/.zshenvx x x x ${ZDOTDIR:-$HOME}/.zprofilex x ${ZDOTDIR:-$HOME}/.zshrcx x ${ZDOTDIR:-$HOME}/.zloginx x ${ZDOTDIR:-$HOME}/.zlogoutx x One 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.
manually call the others
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.
It’s all about context. If you write a convenience function and put it in zshrc, scripts you run from the cli will not have access to the function as defined in zshrc. Same with aliases added by zsh plugins etc.
If you need “the thing” on the command line, zshrc. If you also need it in scripts you run from the cli, toss it in the profile file.
ETA: I personally keep the functions I want to access from scripts in .zshenv as I recall reading that this file is ALWAYS sourced.
What kind of functions do you write which you share between your scripts? Generally if I’m wanting to reuse a non-trivial function, I extend the functionality of the first script instead.
All of the repos for my GitHub sourced vim plugins live under one parent directory. I symlink to them from ~/.vim
One example is a simple function that pushes the top level repo directory onto my dir stack and then runs a loop where it pushes each subdir into the stack, runs “ggpull” then pops back to the top level repo directory. ggpull is an alias added by the zsh git plugin. After all repos have been updated it pops back to my original pwd.
I run this as part of my “update all the things” script but sometimes I also want to run it in demand from the cli. So I want this function in all scopes and I want it to have access to “ggpull” in all of those scopes.
I also “misuse” timewarrior a bit and use it to time things like “how much time do I spend waiting for salt to run”. That has its own timewarrior db and a wrapper function for pointing the command at said db. I use this in both login and non login shell contexts.
Yeah, I’d write this as a single
updatescript with options toupdate vimpluginsorupdate pkgorupdate all.I see that you want it to be a function so you can get the chdir as a side effect, but mixing that with updating doesn’t make sense to me.
zshenv’s selling point isn’t necessarily that your typical functions are available across scripts (though that can be neat, too – I sourcealiasrcas well as anutilsscript file in my shell config) – it’s that it’s there for non-interactive shells too, whereaszprofileis only applied for login shells (andzshrconly for interactive ones).So for example, I could open a command in my editor of choice (Helix’s
:shfor me), and if I define stuff using thezshenv, all of my aliases etc. are right there. I just have to avoid naming conflicts for script function names if it’s the default shell, but that’s pretty easily done.
Switching to Fish was the best decision I ever made in my terminal. Besides using tmux.
Isn’t the POSIX incompatibility a major roadblock when scripting?
Not really, you can make .fish scripts or call “bash script.sh” when it’s more appropriate to be posix compliant
Not really. I hate writing bash scripts anyway so I usually script whatever I need in Ruby which is far better at scripting than any posix script ever will be, and even when I do need to run a bash script I still can or just shell down into bash or zsh if I really really need to. But that’s like once a year.
Yeah. Fish just simplifies life everywhere. No longer do I need to care about those silly files or other configurations for basic stuff like search history.
Best decision ever.
The only thing I miss in fish is
$?I know
$statusexists but my fingers don’t.Could you make an alias for it?
Alright stranger, let’s hear it. What is it about Fish that you love so much?
I’ve been generally happy with bash or zsh, pretty much whatever is installed by default (and I honestly don’t know the difference between the two I just mentioned 😬).
Zsh has more features and customization options than bash. Fish has a ton of convenience features at the cost of POSIX compatibility (which many view as a good thing)
Once upon a time I was the person that was constantly messing with my shell. I would performance tune it, try out new plugins weekly, change my config often. It honestly became a huge waste of time. Since switching to fish I literally haven’t spent any time configuring it at all, besides adding in the fzf plugin and the fzf-marks plugin. It just works. And it has all of the same features that everyone adds to zsh with plugins straight out of the box.
If you’re happy with the default in bash or zsh then you will be even more happy with the default in fish, as it’s just much much more user friendly (which is why so many people add so many plugins to bash and zsh: to make it more user friendly). You can even configure it (even the colors) with a web interface! No mucking about in text files if you don’t want to.
I have sort of been eyeing fish on and off for years. I enjoy my oh my zsh setup and have it somewhat customized. I use a modified version of the funky theme. (I can share if interested.) When I’m at work I don’t try new things that might affect my productivity (like trying a new shell) and when I have motivation to do techy stuff in my free time I really need to utilize it to do what I want because my focus really meanders.
I was the person who used every kind of zsh package manager that existed. I even had performance tweaks for some because they were too slow for me. I didn’t even use oh my zsh because it was too slow, and I had hundreds of customizations and maybe 30 plugins.
I no longer needed any of the plugins except fzf and fzf-marks when I switched to fish. It really did simplify my life a whole lot. I don’t ever mess with configs anymore.
That’s fair. But look at it this way, when you’re at work you’re being paid for it, and you might eventually improve your productivity.
Also, you can have a look at oh my fish, it’s an alternative to omz I used before switching to starship.
I feel pretty productive with CLI stuff. Fish does look nifty though. I’ll give it a shot sometime. Oil has been intriguing too, I’ve enjoyed reading updates about it over the years back on r/programming. https://www.oilshell.org/cross-ref.html?tag=OSH#OSH
pretty sure that’s your dating profile. And/or cat photos.
cat ~/Photos/cat.jpeg >> ~/.dating_profile
Hey, I’m a cool kid, too! I have a custom
.nanorcShow us!
Afaik the difference is whether a session is interactive or not, and non-interactive ones don’t source the rc
But what would I want in a login shell that I don’t also want in a non login shell?
Presumably just to get rid of unnecessary stuff that would slow down the start of all bash instances. Also aliases that could fuck with scripts
When in doubt,
~/.zshrc. It’s the right choice 99% of the time. Otherwise, there’s a chance you fuck up scripts you’ve installed which assume no shell options have been changed in non-interactive contexts.So, assuming bash is your shell, the ~/.bash_profile is executed for login shells for the user logging in.
~/.bashrc is the initialization script for when starting a bash session (for the current user).
In my experience, the ~/.bashrc will also execute ~/.bash_profile if it exists. So you can use either.
What would I want in login environments I wouldn’t also want in interactive ones though?
I just thow shit wherever it works lol
You’ve shared the true
bash configurationflow chart.- Add this line to your
.bashrc. - If that didn’t work, move it into
.bash_profile. - If that didn’t work, call up that bash fanatic you know, and let them screw with both files for like 1t minutes.
- If that didn’t work, there’s this tarot card reader I know that comes very recommended. Maybe we can get a bulk discount.
We all know what tarot were gettin
Works every time
- Add this line to your
What about what I do: Just add
. ~/.bash_BeigeAgendaat the bottom of one of the files, for all my own crap.I just link one to the other and make sure it’s idempotent.
Easier said than done. Try echoing
$PATHthen runningzshthen$PATHagain. It’s likely gotten bigger lol. I don’t think it’s a real problem though.Yeah, I may have a larger $PATH than required.
It doesn’t really matter tbh, you shouldn’t be arbitrarily running a shell in a shell (apart from command substitutions).
You’re aware of what the * does? And of people using other shells?
