Why quoting rules prevent errors in Bash Scripting - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to safely print the variable content with spaces.

Bash Scripting

echo [1]

Drag options to blanks, or click blank then click option'

A$"var"

B$var

C'$var'

D"$var"

Attempts:

3 left

💡 Hint

Common Mistakes

Not quoting the variable causes word splitting.

Using single quotes prevents variable expansion.

Using double quotes around the variable ensures spaces are preserved and prevents word splitting.

2fill in blank

medium

Complete the code to assign a string with spaces to a variable correctly.

Bash Scripting

name=[1]

Drag options to blanks, or click blank then click option'

AJohn_Doe

B"John Doe"

C'John Doe'

DJohn Doe

Attempts:

3 left

💡 Hint

Common Mistakes

Not quoting causes syntax errors or splits the value.

Using unquoted spaces breaks the command.

Double quotes allow the string with spaces to be assigned as one value.

3fill in blank

hard

Fix the error in the command to safely list files with spaces in their names.

Bash Scripting

for file in [1]; do echo "$file"; done

Drag options to blanks, or click blank then click option'

A"*"

B*

C'*'

D\*

Attempts:

3 left

💡 Hint

Common Mistakes

Using unquoted * splits filenames with spaces.

Single quotes prevent globbing.

Using double quotes around * prevents word splitting and preserves filenames with spaces.

4fill in blank

hard

Fill both blanks to safely read a filename and print its content.

Bash Scripting

read -r filename
cat [1]$filename[2]

Drag options to blanks, or click blank then click option'

A"

B'

D\

Attempts:

3 left

💡 Hint

Common Mistakes

Not quoting the variable causes errors with spaces.

Using single quotes prevents variable expansion.

Double quotes around the variable prevent word splitting and preserve spaces in the filename.

5fill in blank

hard

Fill all three blanks to safely append a string with spaces to a file.

Bash Scripting

text=[1]
file=[2]
echo [3] >> "$file"

Drag options to blanks, or click blank then click option'

A"Hello World"

Boutput.txt

C$text

Doutput txt

Attempts:

3 left

💡 Hint

Common Mistakes

Not quoting strings with spaces causes errors.

Using unquoted variables in echo can split words.

File names with spaces need quotes.

Double quotes around the string preserve spaces; file name is simple; variable expansion is quoted in echo.

Practice

1. Why is it important to use quotes around variables in bash scripts when the variable might contain spaces?

easy

A. To keep the variable's value as a single word and avoid splitting it into multiple arguments

B. To make the variable value uppercase automatically

C. To comment out the variable so it doesn't run

D. To convert the variable into a number

Solution

1. Step 1: Understand how bash treats unquoted variables

   When a variable is unquoted, bash splits its value by spaces into separate words, causing errors if the value contains spaces.

2. Step 2: Effect of quoting variables

   Using quotes around the variable keeps its entire value as one single argument, preventing unwanted splitting.

3. Final Answer:

   To keep the variable's value as a single word and avoid splitting it into multiple arguments -> Option A

4. Quick Check:

   Quoting prevents word splitting = A [OK]

Hint: Quote variables to keep spaces inside values intact [OK]

Common Mistakes:

• Not quoting variables with spaces causes errors
• Assuming quotes change variable content
• Using quotes to convert variable types

2. Which of the following is the correct way to echo a variable that might contain spaces without causing errors?

easy

A. echo $"var"

B. echo $var

C. echo '$var'

D. echo "$var"

Solution

1. Step 1: Understand the difference between single and double quotes

   Single quotes prevent variable expansion, so '$var' prints literally. Double quotes allow expansion and keep spaces intact.

2. Step 2: Choose the correct quoting for variable expansion with spaces

   Using double quotes around $var expands the variable and preserves spaces, avoiding errors.

3. Final Answer:

   echo "$var" -> Option D

4. Quick Check:

   Double quotes expand variables safely = A [OK]

Hint: Use double quotes to expand variables safely [OK]

Common Mistakes:

• Using single quotes prevents variable expansion
• Not quoting variables causes word splitting
• Using invalid quote syntax like $"var"

3. What will be the output of this script if name="John Doe" and the command is echo Hello $name without quotes?

medium

A. Hello John Doe

B. Hello John

C. Hello John Doe (with quotes)

D. Syntax error

Solution

1. Step 1: Analyze how bash splits unquoted variables

   Without quotes, $name expands to two words: 'John' and 'Doe'. The echo command treats them as separate arguments.

2. Step 2: Understand echo behavior with multiple arguments

   Echo prints all arguments separated by spaces, so it prints 'Hello John Doe'. The command echo Hello $name without quotes prints three words separated by spaces.

3. Final Answer:

   Hello John Doe -> Option A

4. Quick Check:

   Unquoted variable splits words = C [OK]

Hint: Unquoted variables split on spaces, producing multiple words [OK]

Common Mistakes:

• Thinking output is one word
• Confusing quotes effect
• Expecting syntax error

4. Given the script snippet: filename=My File.txt rm $filename What is the main problem and how to fix it?

medium

A. No problem; script works fine

B. rm command will fail with syntax error; fix by escaping spaces

C. rm command will delete the wrong file; fix by quoting: rm "$filename"

D. rm command will delete all files; fix by using single quotes

Solution

1. Step 1: Identify the issue with unquoted variable containing spaces

   Without quotes, rm sees two arguments: 'My' and 'File.txt', causing errors or deleting wrong files.

2. Step 2: Fix by quoting the variable

   Using rm "$filename" treats the whole filename as one argument, preventing errors.

3. Final Answer:

   rm command will delete the wrong file; fix by quoting: rm "$filename" -> Option C

4. Quick Check:

   Quote filenames with spaces to avoid rm errors = D [OK]

Hint: Quote filenames with spaces to avoid command errors [OK]

Common Mistakes:

• Not quoting variables with spaces
• Using single quotes prevents variable expansion
• Assuming no error occurs

5. You want to pass a variable containing special characters and spaces to a command safely. Which quoting method should you use to allow variable expansion but prevent errors?

hard

A. Use single quotes around the variable like '$var'

B. Use double quotes around the variable like "$var"

C. Use no quotes at all

D. Escape every special character manually

Solution

1. Step 1: Understand single vs double quotes in bash

   Single quotes prevent variable expansion, so '$var' prints literally. Double quotes allow expansion but keep the value as one piece.

2. Step 2: Why double quotes are best for variables with spaces and special chars

   Double quotes expand variables and prevent word splitting or globbing, avoiding errors without manual escaping.

3. Final Answer:

   Use double quotes around the variable like "$var" -> Option B

4. Quick Check:

   Double quotes expand variables safely = B [OK]

Hint: Double quotes expand variables and keep text safe [OK]

Common Mistakes:

• Using single quotes disables variable expansion
• Not quoting variables causes errors
• Trying to escape all special characters manually