Reading and Understanding Command Output
Output is just text printed back to you
After you run a command, whatever appears beneath it — a file list, a success message, a version number — is called "output". Reading output slowly and fully (not skimming) is the single most valuable terminal habit you can build.
Success looks quiet, failure looks loud
Many commands print nothing at all when they succeed — silence often means "it worked". Failures, on the other hand, usually print something explicit, often in red text, containing the word "Error", "failed", or "cannot". If you see red text or the word "error", that's your signal to slow down and read carefully.
Scrolling matters
Some commands (like installing software) print many lines of output over several seconds. It's easy to only see the last few lines and miss an important warning that scrolled past. If something seems to have gone wrong, scroll up in your terminal window to read the full output from the start.
Key Takeaways
- Whatever text appears after running a command is called "output" — read it fully, not just skim it.
- Silence after a command often means success; explicit red text or 'Error' means something failed.
- Long-running commands print many lines — scroll up to see the full output if something seems wrong.
- Reading output carefully is the single most valuable terminal habit to build.
Compare a silent success and a loud failure
Run `mkdir test-folder` (likely silent success). Then run `mkdir test-folder` again — since it already exists, this should print an explicit error. Compare the two outputs.