Here strings (<<<) in Bash Scripting - Step-by-Step Execution

Concept Flow - Here strings (<<<)

Start script

↓

Use <<< to send string

↓

Command reads string as input

↓

Command processes input

↓

Output result

↓

End script

The script uses <<< to send a string directly as input to a command, which then processes it and outputs the result.

Execution Sample

Bash Scripting

grep 'hello' <<< 'hello world'
echo $?

This code searches for 'hello' in the string 'hello world' using a here string and prints the exit status.

Execution Table

Step	Action	Command Input	Command Output	Exit Status
1	Send 'hello world' to grep via here string	'hello world'	hello world	0
2	Print exit status of grep		0
3	End of script

💡 grep finds 'hello' in the input string, so exit status is 0 (success).

Variable Tracker

Variable	Start	After Step 1	After Step 2	Final
Command Input		'hello world'	'hello world'	'hello world'
Exit Status		0	0	0

Key Moments - 2 Insights

Why does grep get the string without using a file?

Because the here string (<<<) sends the string directly as input to grep, so no file is needed. See execution_table step 1.

What does the exit status 0 mean after grep runs?

Exit status 0 means grep found the pattern in the input. See execution_table step 2 where exit status is printed.

Visual Quiz - 3 Questions

Look at the execution table, what is the command input to grep at step 1?

A 'hello'

B Empty string

C 'hello world'

D 'world hello'

💡 Hint

Check the 'Command Input' column in execution_table row for step 1.

At which step is the exit status of grep printed?

A Step 2

B Step 1

C Step 3

D It is never printed

💡 Hint

Look at the 'Action' column in execution_table to find when exit status is printed.

If the string did not contain 'hello', what would the exit status be?

A 0

B 1

C 2

D No exit status

💡 Hint

Exit status 1 means grep did not find the pattern; see common grep exit codes.

Concept Snapshot

Here strings (<<<) send a string as input to a command.
Syntax: command <<< 'string'
The command reads the string as if from a file.
Useful for quick input without files.
Exit status shows if command succeeded.

Full Transcript

This example shows how to use a here string (<<<) in bash scripting. The here string sends the string 'hello world' directly as input to the grep command. Grep searches for the word 'hello' in this input. Since 'hello' is found, grep outputs the matching line and sets the exit status to 0, meaning success. Then the script prints the exit status. This method avoids creating a file for input and is a quick way to provide input to commands.

Practice

1. What does the here string operator <<< do in bash scripting?

easy

A. Redirects output to a file

B. Starts a multiline comment

C. Sends a short string as input to a command

D. Creates a new shell process

Solution

1. Step 1: Understand the purpose of here strings

   Here strings use <<< to send a short string directly as input to a command without needing a file.

2. Step 2: Compare with other redirections

   Unlike output redirection or comments, here strings provide input data inline.

3. Final Answer:

   Sends a short string as input to a command -> Option C

4. Quick Check:

   Here strings = send input string [OK]

Hint: Here strings send input text directly to commands [OK]

Common Mistakes:

• Confusing input with output redirection
• Thinking it creates files
• Mixing with multiline comments

2. Which of the following is the correct syntax to use a here string to send the text "hello world" to the cat command?

easy

A. cat <<<"hello world"

B. cat << hello

C. cat < hello

D. cat <<< hello world

Solution

1. Step 1: Identify correct here string syntax

   The here string operator is <<< followed by a quoted string to preserve spaces or special characters.

2. Step 2: Check each option

   cat <<< hello world misses quotes, which can cause word splitting. cat << hello uses here document syntax. cat < hello is input redirection from a file. cat <<<"hello world" correctly uses cat <<<"hello world".

3. Final Answer:

   cat <<<"hello world" -> Option A

4. Quick Check:

   Quotes needed with here strings = cat <<<"hello world" [OK]

Hint: Use <<< with quotes for strings containing spaces [OK]

Common Mistakes:

• Omitting quotes causing errors
• Using << instead of <<<
• Confusing input redirection with here strings

3. What is the output of the following command?

grep 'world' <<< "hello world"

medium

A. "

B. world

C. hello

D. hello world

Solution

1. Step 1: Understand grep with here string input

   The here string sends "hello world" as input to grep. Grep searches for lines containing 'world'.

2. Step 2: Determine grep output

   The entire line "hello world" contains 'world', so grep outputs the full line.

3. Final Answer:

   hello world -> Option D

4. Quick Check:

   grep outputs matching lines = hello world [OK]

Hint: grep prints full matching lines from input [OK]

Common Mistakes:

• Expecting only the matched word
• Confusing grep output with cut or awk
• Thinking here string changes grep behavior

4. Identify the error in this script snippet:

read name <<

medium

A. No error, script runs fine

B. read command cannot use here strings

C. Missing quotes around John in here string

D. Incorrect use of echo syntax

Solution

1. Step 1: Analyze the here string usage

   The here string operator works with read and does not require quotes for simple alphanumeric strings like John.

2. Step 2: Check the given snippet

   read name << correctly sets name=John (even with literal \n if present), and echo "Name is $name" outputs correctly. No syntax or runtime errors.

3. Final Answer:

   No error, script runs fine -> Option A

4. Quick Check:

   Here strings + read works without quotes for simple input [OK]

Hint: Here strings with read work without quotes for simple input [OK]

Common Mistakes:

• Assuming read can't use here strings
• Thinking quotes are always required
• Misunderstanding echo syntax

5. You want to count how many times the word "error" appears in a log line stored in a variable line. Which command correctly uses a here string to do this?

hard

A. grep 'error' < $line | wc -l

B. grep -o 'error' <<< "$line" | wc -l

C. echo $line | grep -c 'error'

D. wc -l <<< "$line" | grep 'error'

Solution

1. Step 1: Understand the goal

   We want to count occurrences of 'error' in the variable line.

2. Step 2: Analyze each option

   grep -o 'error' <<< "$line" | wc -l uses here string to send $line to grep with -o (outputs each match on a new line), then counts lines with wc -l, correctly counting occurrences.
   grep 'error' < $line | wc -l tries to redirect input from a file named by $line, which is wrong.
   echo $line | grep -c 'error' echoes line and uses grep -c, which counts matching lines, not occurrences.
   wc -l <<< "$line" | grep 'error' pipes wc -l output to grep, which is incorrect usage.

3. Final Answer:

   grep -o 'error' <<< "$line" | wc -l -> Option B

4. Quick Check:

   Use grep -o with here string to count matches [OK]

Hint: Use grep -o with <<< and wc -l to count matches [OK]

Common Mistakes:

• Using grep -c which counts lines, not matches
• Redirecting input from variable as file
• Misordering pipes causing wrong output