terminal 106: shell config on macOS terminal 106: shell config บน macOS

in terminal 105 you learned the rule underneath a lot of command-resolution problems:

• the shell searches PATH in order
• a temporary export changes the current shell
• and a new shell starts with its own startup state

106 is where you stop patching the current shell and start configuring the default one.

for modern macOS, that default shell is usually zsh.

if you’re on Windows, the specific files here (~/.zshrc, ~/.zprofile) are zsh/macOS. the underlying idea — “your shell reads startup files, and you have to reload them after editing” — still applies to PowerShell, just with a different file ($PROFILE) and reload step. skim for the mental model, then look up the PowerShell specifics separately.

the beginner problem here is not “how do i become a shell wizard?”

it’s much simpler:

where do i put everyday shell settings so they actually load, and what do i have to do after editing that file?

the answer for this lesson is:

• put aliases and everyday interactive shell config in ~/.zshrc
• if a tool installer tells you to put PATH setup in ~/.zprofile, follow the tool’s instruction
• reload it with source ~/.zshrc or open a new shell

what you’ll know by the end

• the difference between Terminal and the shell running inside it
• that modern macOS usually starts zsh by default
• where ~/.zshrc fits into the everyday workflow
• when ~/.zprofile is the better file for login-time PATH setup
• how to reload changes with source ~/.zshrc
• how to add and use a simple alias
• the footgun for this lesson: editing ~/.zshrc does not change the current shell until you reload it

what this assumes

terminal 101 through terminal 105.

if PATH and temporary export changes make sense now, you’re ready for the file that makes those changes stick.

4 ideas that make shell config feel normal

the practical rule is:

editing ~/.zshrc changes the file on disk first. your current shell only notices after reload or restart.

for this lesson, keep the scope narrow: aliases and everyday interactive tweaks belong in ~/.zshrc. if an installer like Homebrew tells you to add a PATH line to ~/.zprofile, follow that instruction instead of forcing everything into one file.

try it yourself

the interactive demo below focuses on exactly that stale-config moment.

work through this order:

1. leave the default alias as gs -> git status
2. click write alias to ~/.zshrc
3. click run alias
4. notice that the file changed, but the current shell still says command not found
5. click cat ~/.zshrc
6. confirm the alias line is really saved on disk
7. click source ~/.zshrc
8. click run alias again
9. click open new shell
10. click run alias one more time

the teaching moment is steps 2 through 8:

• saving config is not the same as loading config
• source ~/.zshrc tells the current shell to read the file again

once that becomes obvious, shell setup stops feeling like superstition.

Terminal vs shell

people mix these words constantly, so keep the simple version:

• Terminal is the app window
• shell is the program inside that reads and runs commands

on modern macOS, that shell is usually zsh.

this distinction matters because you are not editing “Terminal settings” when you add an alias. you are editing a shell startup file that zsh reads.

why ~/.zshrc is the right beginner default for aliases

you will eventually hear about other files like .zprofile, .bashrc, or .bash_profile.

for this series, that is noise.

the useful beginner default on modern macOS is:

~/.zshrc

for aliases, prompts, and small interactive tweaks, that keeps the lesson honest and actionable. you need one right place for everyday shell habits, not a survey of every startup-file edge case.

the important boundary is this:

• ~/.zshrc is a good default for aliases and interactive shell behavior
• ~/.zprofile is commonly where macOS installers put login-time PATH setup

so if Homebrew or another tool gives you a specific file, trust the tool for that case.

what source ~/.zshrc actually does

this command:

source ~/.zshrc

tells the current shell:

“read this file again right now”

it does not open a new terminal window. it does not edit the file for you. it just makes the already-running shell load the current contents.

that is why it fixes the beginner moment of:

• “the alias line is clearly in the file”
• “but the alias still doesn’t work”

one real-world task

on your real Mac, try this:

1. open ~/.zshrc in an editor (nano ~/.zshrc is enough; if the file does not exist yet, the editor can create it)
2. add:

alias gs='git status'

3. save the file
4. run source ~/.zshrc
5. run gs

that is deliberately small. the goal is not to build a giant config file. the goal is to prove that you understand the saved-file vs loaded-shell difference.

once that clicks, adding PATH lines, aliases, and small quality-of-life tweaks becomes much less fragile.

common mistakes

you edit ~/.zshrc and expect the current shell to update itself. it will not. reload or open a new shell.

you confuse the Terminal app with the shell configuration inside it. different layers, different settings.

you paste config into random startup files because different blog posts say different things. for this stage, keep the alias lesson simple: use ~/.zshrc, and only switch files when a tool gives you a specific instruction.

you make permanent changes before testing the command once. keep the first alias tiny and easy to verify.

you treat aliases as magic instead of text substitution. an alias is just a shorter name that expands to another command.

official references

• zsh startup files reference
• Homebrew installation docs

what this unlocks

you now have the core beginner setup model for the terminal:

• install tools
• understand PATH
• make temporary fixes
• move the real fix into shell config
• reload the shell and verify it

that is enough foundation to use the terminal with much less guesswork.

for the next step, use the terminal series hub to find the next post. the beginner foundation is now coherent enough to build on with applied-workflow posts.