Command history and shell shortcuts — working faster in the terminal

Every command you run is saved to a history file (~/.bash_history or ~/.zsh_history, depending on your shell). You've probably already used the up arrow to step backward through it — but a few underused shortcuts make that history far more useful than scrolling one line at a time.

Ctrl+R alone is worth more than the rest combined — searching history by content, rather than counting how many presses of the up arrow a command is away, turns "I know I ran something like this yesterday" into a two-second lookup instead of a re-typed command.

Pressing Tab completes a partially-typed file name, directory, or (for many tools) command flags — and pressing it twice when the first press doesn't finish anything lists every possible match. Typing cd Doc<Tab> completing to cd Documents/ isn't just fewer keystrokes; it also avoids the actual class of bug where a manually-typed filename has a typo the shell would otherwise silently fail on with "No such file or directory."

An alias is a shortcut name for a longer command, defined in your shell's config file (covered in the environment variables and shell configuration lesson):

Once defined and reloaded (source ~/.bashrc), typing gs runs git status exactly as if you'd typed it out. Aliases are especially worth creating for any command you find yourself typing identically, several times a day.

None of these shortcuts change what's possible in the shell — everything here is also achievable by typing the full command out every time. What they change is friction: a terminal that requires re-typing or slowly scrolling for anything not run in the last few commands feels slow enough that people avoid it in favor of a GUI, even when the command line would genuinely be faster. Fixing that friction is most of what separates someone comfortable in a terminal from someone who dreads opening one.