Why Color output (ANSI escape codes) in Bash Scripting? - Purpose & Use Cases

The Big Idea

What if your terminal could talk to you in colors, making errors impossible to miss?

The Scenario

Imagine you run a script that prints many lines of text in the terminal. All lines look the same, so you have to carefully read each one to find errors or important messages.

The Problem

Without colors, it's hard to quickly spot warnings or errors. You waste time scrolling and re-reading. Mistakes can be missed because everything blends together.

The Solution

Using ANSI escape codes, you can add colors to your terminal output. This highlights important parts like errors in red or success messages in green, making it easy to see at a glance.

Before vs After

✗ Before

echo "Error: File not found"
echo "Process completed successfully"

✓ After

echo -e "\033[31mError: File not found\033[0m"
echo -e "\033[32mProcess completed successfully\033[0m"

What It Enables

It enables you to create clear, colorful terminal messages that catch your eye and speed up understanding.

Real Life Example

System administrators use colored output to quickly spot failed services or warnings in long logs, saving hours of manual checking.

Key Takeaways

Manual terminal output is plain and hard to scan.

ANSI escape codes add color to highlight important info.

Colored output helps you find errors and messages faster.

Practice

1. What does the ANSI escape code \e[31m do in a bash script?

easy

A. Resets all colors and styles

B. Changes the background color to blue

C. Changes the text color to red

D. Makes the text bold

Solution

1. Step 1: Understand ANSI escape code format

   ANSI escape codes start with \e[ and end with m, where numbers define colors or styles.

2. Step 2: Identify code 31

   Code 31 sets the text color to red in terminal output.

3. Final Answer:

   Changes the text color to red -> Option C

4. Quick Check:

   \e[31m = red text color [OK]

Hint: 31 means red text color in ANSI codes [OK]

Common Mistakes:

• Confusing text color with background color
• Thinking \e[31m resets colors
• Assuming it makes text bold

2. Which of the following is the correct syntax to print the word Success in green color using echo in bash?

easy

A. echo "\e[0m32mSuccess\e"

B. echo -e "\e[32mSuccess\e[0m"

C. echo "\e[32mSuccess"

D. echo "\e[32mSuccess\e[32m"

Solution

1. Step 1: Use correct ANSI escape code format

   The code to start green text is \e[32m and to reset colors is \e[0m.

2. Step 2: Check each option's correctness

   echo -e "\e[32mSuccess\e[0m" correctly wraps 'Success' with start and reset codes. Others have syntax errors or missing reset.

3. Final Answer:

   echo -e "\e[32mSuccess\e[0m" -> Option B

4. Quick Check:

   Start green with \e[32m and reset with \e[0m [OK]

Hint: Always reset color with \e[0m after colored text [OK]

Common Mistakes:

• Forgetting to reset color after text
• Placing reset code before text
• Using incorrect escape code syntax

3. What will be the output of the following bash command?

echo -e "\e[33mWarning\e[0m: Disk space low"

medium

A. No color, plain text output

B. Entire line in yellow color

C. Syntax error due to missing quotes

D. Warning in yellow color followed by ': Disk space low' in default color

Solution

1. Step 1: Analyze the escape codes in the command

   \e[33m sets yellow text color, \e[0m resets color back to default after 'Warning'.

2. Step 2: Understand echo -e behavior

   Echo with -e interprets escape sequences, so 'Warning' appears yellow, rest normal.

3. Final Answer:

   Warning in yellow color followed by ': Disk space low' in default color -> Option D

4. Quick Check:

   \e[33m colors 'Warning', \e[0m resets color [OK]

Hint: Reset color after colored text to limit color scope [OK]

Common Mistakes:

• Assuming entire line is colored
• Ignoring -e flag in echo
• Confusing color codes with styles

4. Identify the error in this bash snippet intended to print Error in red:

echo "\e[31mError\e[0m"

medium

A. Missing -e flag in echo to enable escape sequences

B. Wrong color code for red

C. Reset code \e[0m is incorrect

D. Quotes should be single quotes instead of double

Solution

1. Step 1: Check echo command usage

   By default, echo does not interpret escape sequences without -e flag.

2. Step 2: Confirm color codes and quotes

   Color code 31 for red and reset \e[0m are correct; double quotes allow escape sequences with -e.

3. Final Answer:

   Missing -e flag in echo to enable escape sequences -> Option A

4. Quick Check:

   Use echo -e to interpret \e codes [OK]

Hint: Use echo -e to enable ANSI escape codes [OK]

Common Mistakes:

• Forgetting -e flag in echo
• Changing correct color codes
• Using wrong quote types unnecessarily

5. You want to write a bash script that prints Success in green and Error in red on separate lines, then resets color. Which script snippet correctly does this?

hard

A. echo -e "\e[32mSuccess\e[0m"; echo -e "\e[31mError\e[0m"

B. echo "\e[32mSuccess"; echo "\e[31mError"; echo "\e[0m"

C. echo -e "\e[32mSuccess\e[31mError\e[0m"

D. echo "\e[32mSuccess\n\e[31mError\e[0m"

Solution

1. Step 1: Check color codes and reset usage

   Each line uses correct color code (32 for green, 31 for red) and resets color with \e[0m.

2. Step 2: Verify echo usage and line separation

   echo -e "\e[32mSuccess\e[0m"; echo -e "\e[31mError\e[0m" uses separate echo commands with -e flag and resets color after each line, ensuring correct colors and reset.

3. Final Answer:

   echo -e "\e[32mSuccess\e[0m"; echo -e "\e[31mError\e[0m" -> Option A

4. Quick Check:

   Separate echo with -e and reset color each line [OK]

Hint: Use separate echo -e with reset for each colored line [OK]

Common Mistakes:

• Not resetting color after each line
• Using single echo without proper newlines
• Omitting -e flag in echo