terminal 104: installing tools on macOS with Homebrew terminal 104: ติดตั้งเครื่องมือบน macOS ด้วย Homebrew

in terminal 103 you learned the workflow idea: search, pipe, redirect, keep only the useful part.

the next wall is simpler and more annoying:

“okay, but how do i install the command everyone keeps mentioning?”

on a Mac, that answer is usually Homebrew.

this lesson is Mac-only on purpose. the goal is not “learn every package manager.” the goal is to make one very common beginner moment feel predictable:

• you try brew install ...
• maybe brew is missing
• you install Homebrew
• the installer prints a shell-setup step
• you run that printed setup step instead of guessing
• the tool appears on disk
• and then which proves whether your shell can see it

once that sequence makes sense, “command not found” stops feeling random.

if you’re on Windows, don’t force this lesson to map 1:1 to your machine. the important mental model is still useful, but the install tool is different. you can skim this to understand the shell-setup/PATH problem, then continue with the series in terminal 105, where the PATH model gets explained directly.

what you’ll know by the end

• what Homebrew is and why Mac users reach for it
• how to install Homebrew with the official installer
• how to follow the installer’s post-install shell step instead of skipping it
• how to install a tool with brew install
• how to upgrade a tool with brew upgrade
• how to use which to check whether your shell can actually find a command
• the footgun for this lesson: a tool can be installed on disk while your current shell still can’t see it

what this assumes

terminal 101, terminal 102, and terminal 103.

if pwd, ls, cat, pipes, and redirects feel okay now, you’re ready.

5 commands + 1 mental model

this lesson focuses on modern macOS with zsh.

the simulator uses the Apple Silicon Homebrew path, which is:

/opt/homebrew/bin

if you’re on an Intel Mac, you’ll usually see /usr/local/bin instead. same idea, different folder.

the demo uses ~/.zprofile because that is a common zsh login startup file on macOS. if your installer prints a different file, use the one it prints.

the mental model underneath those commands is the real lesson:

1. install puts files somewhere on disk
2. your shell only runs commands it can find through PATH
3. the installer may put the right files on disk before your shell has loaded the PATH setup

if PATH still feels fuzzy here, that’s fine — terminal 105 explains it directly.

try it yourself

the interactive demo below is a compressed version of the real beginner experience. click through this order:

1. brew install ripgrep first
2. watch it fail because brew does not exist yet
3. run the Homebrew installer
4. notice that the installer prints the shell-setup commands
5. try which brew
6. notice the teaching moment: Homebrew now exists on disk, but PATH is not set yet
7. run the printed shell setup
8. run which brew again
9. run brew install ripgrep
10. run which rg
11. run rg deploy ~/projects/launch-plan
12. open a new shell and run which brew one more time
13. run brew upgrade ripgrep

the key moment is between steps 5 and 8:

• install success does not guarantee that the current shell sees the new command immediately
• on modern macOS, the installer prints the shell setup you need; follow those printed commands instead of guessing a startup file
• when a command still says “not found”, check whether it’s missing from disk or just missing from your current PATH

what a package manager is, without the jargon

a package manager is just a tool that installs other tools in a consistent way.

instead of:

• downloading random zip files
• dragging binaries around by hand
• forgetting where you put them

you get one command:

brew install ripgrep

Homebrew handles the fetch, the files, and the symlink that makes the command usable.

you do not need deeper internals than that yet. for a beginner, “one trusted install command instead of ad hoc downloads” is the important part.

why “installed” and “usable right now” are not the same thing

this is the exact confusion 104 is here to fix.

after Homebrew installs, two different things can both be true:

• brew or rg exists on disk
• your current shell still cannot resolve it

that does not mean the install failed.

it usually means the Homebrew files exist, but the shell setup has not been loaded into this shell yet. the practical beginner move is simple:

1. run which brew or which rg
2. if the installer printed shell-setup commands, run those exact commands
3. open a new shell session if you want to prove the startup file loads next time
4. try again before reinstalling everything

the post after this one explains why that works in more detail. for now, the reliable habit is enough.

why which is worth learning immediately

which is tiny, but it saves a lot of guessing.

which brew
which rg

if it prints a path, your shell knows where the command lives.

if it prints nothing useful, you have a visibility problem, not a typing problem.

that one distinction prevents a lot of beginner thrashing.

one real-world task

on your real Mac, this is the practical flow:

1. install Homebrew with the official installer
2. read the post-install message and run the shell commands it prints
3. open a fresh Terminal tab or window if you want to verify the setting persists
4. run which brew
5. run brew install ripgrep
6. run which rg
7. go to a small project folder
8. run rg TODO

that gives you a real payoff immediately:

• you install one useful tool
• you verify that it resolves
• you use it for a real text-search task instead of installing it “just in case”

common mistakes

you keep reinstalling instead of checking resolution. if brew or rg says “not found”, run which brew or which rg before you install again.

you assume the install failed because the shell cannot see brew yet. this is the big one. the files can be correct while the PATH setup has not been loaded.

you skip the installer’s shell step. current Homebrew docs say the installer prints the shell-config directions you need. on modern macOS, that usually means adding Homebrew’s shellenv setup to a startup file and loading it into the current shell.

you think the exact folder is the lesson. it isn’t. the simulator uses /opt/homebrew/bin because that’s the common modern Mac path. on Intel Macs, the path is usually /usr/local/bin. the idea is still “the shell searches folders in order.”

official references

• Homebrew installation docs
• Homebrew documentation index

what this unlocks

you can now install a tool on a Mac, verify that your shell can see it, and separate “the install is wrong” from “the shell setup has not loaded yet.”

that’s a serious jump in confidence, because a lot of terminal frustration lives exactly there.

next up: terminal 105 — PATH and environment variables. that’s where this stops being a troubleshooting trick and becomes a real mental model.