Quiz: Bash & Shell Mastery

Variables in Bash are declared without spaces around the = sign. For example:

name=Alice

This assigns the value "Alice" to the variable name.

Note: $name is used to reference or read a variable’s value.

Adding spaces causes the shell to interpret the command as a program to run, which is not what you want when setting a variable.

Also, Bash is case-sensitive, so name, NAME and Name are different variables.

Finally, variables can’t have spaces or dashes (-) in their names. Use underscores (_) or camelCase instead.

I know. It’s wild how quickly escaping makes strings tough to parse. Imagine escaping other languages in Bash strings - with all those quotes, apostrophes and $ symbols to f*ck you up. 🫠

Single quotes need escaping inside single-quoted strings. The backslash-escaped single quote ('\'') allows output of:

It's Bash Time!

There are other ways to handle this, but this is the most common.

The {} brace expansion generates multiple versions of its string context, one (or more) for each comma-separated value or pattern.

Here, a{b,c}d expands to:

abd acd

Numbered variables have special meaning. In this case, $1 is a special variable that holds the first argument passed to the script or function.

Since we’re running the script in a REPL, there are no arguments, so $1 is empty. The remaining text 00 is printed as-is.

To print a literal $ character, use single quotes, or escape it with a backslash (\):

price="\$100"
echo "Cost: $price"

The ${var/pattern/replacement} syntax replaces the first occurrence of pattern with replacement. Here, the output is:

Bark meow

It is case-sensitive. To make it case-insensitive, use ${var^pattern/replacement}.

To replace all occurrences, use ${var//pattern/replacement}.

To replace from the beginning of the string, use ${var/#pattern/replacement}.

To replace from the end of the string, use ${var/%pattern/replacement}.

The ${#username} syntax returns the length of username.

For example:

username="@justsml"
echo ${#username} # => 8

While wc would work, it’s technically not a part of Bash.

The utility wc is an old inside joke referring to “water closet,” or toilet. KIDDING! Does anyone reads these?

In reality wc is an ancient command from Posix (and the AT&T Unix days.) It is short for “word count” and it can count lines, words, and characters in a file or input stream.

Did you catch the missing space before the closing bracket?

Bash is quite touchy here: spaces are required inside bracket expressions.

The correct syntax is:

if [ -e example.txt ]; then
  echo "File exists"
else
  echo "File does not exist"
fi

Note: Double brackets [[ ]] are recommended for conditional expressions. See BashFAQ.

Another Error! 🚨

Did you catch the invalid === operator?

You might have been thinking of JavaScript…

In Bash, use == for equality comparisons.

Functions in Bash can accept arguments. The $1 variable holds the first argument passed to the function.

Remember, $0 is the script name, $1 is the first argument, $2 is the second, and so on. Spaces separate arguments. So, greet Hi Dan passes "Hi" as the first argument. In order to pass "Hi Dan" as a single argument, you would need to quote it: greet "Hi Dan".

The | pipe operator connects the output of one command to the input of another. For example:

echo "Mr. Levy 👨🏻‍🔬" | wc -m
# => 14

The (( )) syntax performs integer math in Bash.

It can be used for simple calculations:

((result = 2 + 2))
echo $result # => 4

Or for conditional expressions:

if (( 2 > 1 )); then
  echo "2 is greater than 1"
fi

For floating-point arithmetic, consider using bc or awk.

The (( )) syntax ONLY performs integer arithmetic. You know, whole numbers, with no floating point!

Bash (perhaps surprisingly) lacks built-in support for floating-point arithmetic.

The most common solution is to use GNU utils bc or awk.

The ${var:offset} syntax extracts a substring starting from offset. Here, the output is:

good cat

To extract a substring of a specific length, use ${var:offset:length}.

To extract from the end of the string, use ${var: -offset}. (Note the space before the -!)

each is not a loop keyword in Bash. The main loop keywords are for, while, and until.

While do is not technically a loop keyword, it’s a key part of loop syntax.

The $(ls -l) syntax executes the command inside the parentheses and substitutes the output. For example:

echo "Today is $(date +%F)"

The 1st option uses Single quotes ', not backticks. This prevents expansion, so '$(date +%F)' would simply print the literal string $(date +%F).

While it’s still supported to use backticks (`ls -l`) for command execution, it’s recently become somewhat of an anti-pattern (in some contexts.) Most recommend using $(command) for better readability & consistency with different shells & versions.

Curly braces ${} are used for variable expansion, not command substitution.

The % character is not used for command substitution.

The 2>&1 operator redirects standard error (file descriptor 2) to standard output (file descriptor 1). This is useful for capturing error messages in the same output stream as regular output.

The 1>&2 operator redirects standard output to standard error, however, the question asked how to redirect standard error to standard output.

To Learn more about what’s going on under the hood, check out Greg’s excellent Redirection FAQ.

Also, thanks to Reddit user u/OneTurnMore for suggested copy improvements.