Startup Sequences of Shells

<a href="http:&#x2F;&#x2F;blog.flowblok.id.au&#x2F;static&#x2F;images&#x2F;shell-startup-actual.png" rel="nofollow">http:&#x2F;&#x2F;blog.flowblok.id.au&#x2F;static&#x2F;images&#x2F;shell-startup-actua...</a><p>&quot;To read it, pick your shell, whether it&#x27;s a login shell, whether it&#x27;s interactive, and follow the same colour through the diagram. When the arrows split out to multiple files, it means that the shell will try to read each one in turn (working left to right), and will use the first one it can read.&quot;<p>Note that what the man pages <i>say</i> happens (as of 2013) is in this diagram:<p><a href="http:&#x2F;&#x2F;blog.flowblok.id.au&#x2F;static&#x2F;images&#x2F;shell-startup.png" rel="nofollow">http:&#x2F;&#x2F;blog.flowblok.id.au&#x2F;static&#x2F;images&#x2F;shell-startup.png</a>

I thought maybe this just had a bad UI layout on mobile, but after reviewing on desktop browser, I now know that this useful info was just presented rather poorly.

Bash is broken in this regard, having no way to reliably enforce a consistent baseline across the four possible startup modes except by having all the possible startup files explicitly call some shared source. Glad to see zsh has addressed this.

thanks for this - very useful