Regex in [[ ]] with =~ in Bash Scripting - Step-by-Step Execution

Concept Flow - Regex in [[ ]] with =~

Start

↓

Evaluate string

↓

Evaluate regex pattern

↓

Use [[ string =~ regex

↓

If match: return true

↓

If no match: return false

↓

Use result in if/else or variable

↓

End

The shell evaluates the string and regex pattern inside [[ ]]. It tests if the string matches the regex using =~, then returns true or false for conditional use.

Execution Sample

Bash Scripting

text="hello123"
if [[ $text =~ ^hello[0-9]+$ ]]; then
  echo "Match"
else
  echo "No match"
fi

This script checks if the variable 'text' matches the regex pattern for 'hello' followed by one or more digits.

Execution Table

Step	Action	String Value	Regex Pattern	Match Result	Output
1	Assign text variable	hello123	^hello[0-9]+$
2	Evaluate [[ $text =~ regex ]]	hello123	^hello[0-9]+$	true
3	If condition true, execute then branch	hello123	^hello[0-9]+$	true	Match
4	End if statement	hello123	^hello[0-9]+$	true	Match

💡 Regex matches string, condition is true, so 'Match' is printed and script ends.

Variable Tracker

Variable	Start	After Step 1	After Step 2	Final
text		hello123	hello123	hello123
match_result			true	true
output				Match

Key Moments - 3 Insights

Why do we use double square brackets [[ ]] instead of single [ ] for regex matching?

Double brackets [[ ]] support the =~ operator for regex matching, while single brackets [ ] do not. See execution_table step 2 where [[ ]] evaluates the regex.

What happens if the regex does not match the string?

The match_result becomes false, so the else branch runs. This is shown by the exit_note explaining the condition outcome.

Can we use quotes around the regex pattern inside [[ ]]?

No, quoting the regex disables regex matching and treats it as a string. The pattern must be unquoted as shown in the code sample.

Visual Quiz - 3 Questions

Look at the execution_table, what is the match result at step 2?

A error

B false

C true

D empty

💡 Hint

Check the 'Match Result' column in execution_table row for step 2.

At which step does the script print 'Match'?

A Step 2

B Step 3

C Step 1

D Step 4

💡 Hint

Look at the 'Output' column in execution_table to find when 'Match' is printed.

If the variable text was 'helloabc', what would be the match result?

A false

B true

C error

D depends on shell version

💡 Hint

Refer to variable_tracker and regex pattern: digits expected after 'hello', letters cause no match.

Concept Snapshot

Use [[ string =~ regex ]] to test if string matches regex.
Double brackets [[ ]] enable regex matching with =~ operator.
Regex pattern must be unquoted inside [[ ]].
Returns true if match, false if no match.
Use in if statements to branch logic based on pattern match.

Full Transcript

This example shows how to use regex matching in bash with double square brackets and the =~ operator. We assign a string variable 'text' with value 'hello123'. Then we test if 'text' matches the regex '^hello[0-9]+$' which means 'hello' followed by one or more digits. The [[ $text =~ regex ]] returns true because 'hello123' fits the pattern. The if condition runs the then branch and prints 'Match'. Variables 'text' and 'match_result' keep their values through the steps. Key points: use [[ ]] not [ ], do not quote regex, and the condition result controls the output. This helps check patterns in strings easily in bash scripts.

Practice

1. What does the expression [[ "hello123" =~ [a-z]+[0-9]+ ]] check in a bash script?

easy

A. If the string is exactly 'hello123'

B. If the string contains letters followed by numbers

C. If the string contains only numbers

D. If the string starts with a number

Solution

1. Step 1: Understand the regex pattern

   The pattern [a-z]+[0-9]+ means one or more lowercase letters followed by one or more digits.

2. Step 2: Apply the pattern to the string

   The string "hello123" starts with letters "hello" and ends with digits "123", so it matches the pattern.

3. Final Answer:

   If the string contains letters followed by numbers -> Option B

4. Quick Check:

   Regex matches letters then digits = A [OK]

Hint: Look for letter-digit sequence in string with regex [OK]

Common Mistakes:

• Thinking quotes are needed around regex inside [[ ]]
• Confusing exact match with pattern match
• Assuming regex matches anywhere without order

2. Which of the following is the correct syntax to test if variable var matches regex ^[0-9]+$ in bash?

easy

A. [[ $var =~ "^[0-9]+$" ]]

B. [[ "$var" =~^[0-9]+$ ]]

C. [[ $var =~ ^[0-9]+$ ]]

D. [[ "$var" =~ "^[0-9]+$" ]]

Solution

1. Step 1: Recall regex syntax in [[ ]]

   Inside [[ ]], the regex pattern should NOT be quoted to work correctly.

2. Step 2: Check each option

   [[ $var =~ ^[0-9]+$ ]] uses [[ $var =~ ^[0-9]+$ ]] without quotes around regex, which is correct syntax.

3. Final Answer:

   [[ $var =~ ^[0-9]+$ ]] -> Option C

4. Quick Check:

   No quotes around regex pattern = B [OK]

Hint: Do not quote regex pattern inside [[ ]] [OK]

Common Mistakes:

• Putting quotes around regex pattern causing syntax errors
• Quoting variable but not regex or vice versa
• Using single brackets [ ] instead of [[ ]]

3. What will be the output of this bash script snippet?

text="abc123"
if [[ $text =~ ^[a-z]+[0-9]+$ ]]; then
  echo "Match"
else
  echo "No match"
fi

medium

A. Match

B. No match

C. Syntax error

D. Empty output

Solution

1. Step 1: Analyze the regex pattern

   The pattern ^[a-z]+[0-9]+$ means the string must start with one or more lowercase letters and end with one or more digits, with nothing else.

2. Step 2: Check the string against the pattern

   The string "abc123" starts with letters "abc" and ends with digits "123", so it matches the pattern exactly.

3. Final Answer:

   Match -> Option A

4. Quick Check:

   String matches regex pattern = D [OK]

Hint: Check start ^ and end $ anchors carefully [OK]

Common Mistakes:

• Ignoring anchors ^ and $ in regex
• Assuming partial match is enough
• Quoting regex pattern causing failure

4. Identify the error in this bash snippet:

input="2023-04-01"
if [[ "$input" =~ "^[0-9]{4}-[0-9]{2}-[0-9]{2}$" ]]; then
  echo "Valid date"
else
  echo "Invalid date"
fi

medium

A. Quotes around regex cause the match to fail

B. Variable input is not quoted

C. Regex pattern is invalid syntax

D. Missing semicolon after if condition

Solution

1. Step 1: Check quoting rules for regex in [[ ]]

   Regex pattern inside [[ ]] with =~ must NOT be quoted; quotes make it a string literal, breaking regex matching.

2. Step 2: Identify the error in the snippet

   The snippet quotes the regex pattern, causing the condition to always fail and print "Invalid date".

3. Final Answer:

   Quotes around regex cause the match to fail -> Option A

4. Quick Check:

   No quotes around regex pattern = C [OK]

Hint: Never quote regex pattern inside [[ ]] [OK]

Common Mistakes:

• Quoting regex pattern inside [[ ]]
• Forgetting to quote variable when needed
• Assuming regex syntax errors without checking quotes

5. You want to check if a variable filename ends with either ".jpg" or ".png" using regex in bash. Which condition correctly tests this?

hard

A. [[ "$filename" =~ "\.(jpg|png)$" ]]

B. [[ $filename =~ "\.(jpg|png)$" ]]

C. [[ "$filename" =~\.(jpg|png)$ ]]

D. [[ $filename =~ \.(jpg|png)$ ]]

Solution

1. Step 1: Understand regex for file extensions

   The pattern \.(jpg|png)$ matches a dot followed by 'jpg' or 'png' at the end of the string.

2. Step 2: Apply correct quoting rules

   Regex pattern must NOT be quoted inside [[ ]], and variable can be unquoted if it has no spaces. [[ $filename =~ \.(jpg|png)$ ]] correctly uses unquoted regex and variable.

3. Final Answer:

   [[ $filename =~ \.(jpg|png)$ ]] -> Option D

4. Quick Check:

   Unquoted regex with alternation = A [OK]

Hint: Use unquoted regex with alternation inside [[ ]] [OK]

Common Mistakes:

• Quoting regex pattern causing failure
• Not escaping dot before extension
• Quoting variable unnecessarily