Reading files line by line (while read) in Bash Scripting - Step-by-Step Execution

Concept Flow - Reading files line by line (while read)

Open file

↓

Read line

↓

Is line empty?

Yes→End loop

No↓

Process line

↓

Read next line

↩Back to Is line empty?

The script opens a file and reads it line by line. For each line, it processes the content until no more lines remain.

Execution Sample

Bash Scripting

while IFS= read -r line; do
  echo "$line"
done < input.txt

Reads each line from input.txt and prints it to the screen.

Execution Table

Step	Action	Line Read	Condition (line empty?)	Branch Taken	Output
1	Read first line	Hello, world!	No	Process line	Hello, world!
2	Read second line	This is a test.	No	Process line	This is a test.
3	Read third line	Line three here.	No	Process line	Line three here.
4	Read fourth line		Yes	End loop

💡 Reached end of file; empty line read signals loop termination.

Variable Tracker

Variable	Start	After 1	After 2	After 3	Final
line		Hello, world!	This is a test.	Line three here.

Key Moments - 3 Insights

Why do we use 'IFS=' before read?

Setting IFS= prevents trimming of leading/trailing whitespace in the line, ensuring the line is read exactly as is (see execution_table rows 1-3 where lines keep spaces).

What does the '-r' option do in 'read -r'?

The '-r' option tells read not to treat backslashes as escape characters, so lines with backslashes are read literally (important for accurate line reading).

Why does the loop end when an empty line is read?

When read reaches the end of the file, it returns an empty line and the condition detects this to stop the loop (see execution_table row 4).

Visual Quiz - 3 Questions

Look at the execution table, what is the value of 'line' after step 2?

A "This is a test."

B "Hello, world!"

C "Line three here."

D ""

💡 Hint

Check the 'Line Read' column at step 2 in the execution_table.

At which step does the loop stop reading lines?

A Step 3

B Step 4

C Step 2

D Step 1

💡 Hint

Look at the 'Condition (line empty?)' and 'Branch Taken' columns in the execution_table.

If we remove 'IFS=' from the read command, what might happen?

A Leading/trailing spaces in lines might be trimmed

B The loop will never end

C Backslashes will be treated literally

D The file will not open

💡 Hint

Refer to the key_moments about IFS and how lines are read exactly.

Concept Snapshot

Reading files line by line in bash:
Use 'while IFS= read -r line; do ... done < file'
- IFS= preserves spaces
- -r prevents backslash escapes
- Loop ends when read returns empty line
- Process each line inside the loop

Full Transcript

This example shows how to read a file line by line in bash using a while loop with 'read'. The loop reads each line into the variable 'line' and prints it. The 'IFS=' ensures spaces are preserved, and '-r' prevents backslash escapes. The loop stops when no more lines are available, indicated by an empty line. This method is useful for processing files safely and accurately.

Practice

1. What does the command while IFS= read -r line; do echo "$line"; done < file.txt do in a bash script?

easy

A. Deletes the contents of file.txt.

B. Reads the entire file at once and prints it.

C. Writes each line of file.txt to a new file.

D. Reads the file file.txt line by line and prints each line.

Solution

1. Step 1: Understand the while read loop

   The loop reads input line by line from the redirected file file.txt.

2. Step 2: Check the action inside the loop

   Each line read is stored in variable line and printed with echo.

3. Final Answer:

   Reads the file file.txt line by line and prints each line. -> Option D

4. Quick Check:

   Line-by-line reading = A [OK]

Hint: Remember: while read loops read files line by line [OK]

Common Mistakes:

• Thinking it reads the whole file at once
• Confusing input redirection with output
• Ignoring the role of IFS= and -r

2. Which of the following is the correct syntax to read a file line by line in bash?

easy

A. while read line; do echo $line; done < file.txt

B. while read -r line; do echo $line; done > file.txt

C. while read line; do echo $line; done >> file.txt

D. while read line; do echo $line; done | file.txt

Solution

1. Step 1: Identify input redirection for reading

   The correct way to read from a file is using input redirection: < file.txt.

2. Step 2: Check the loop syntax

   while read line; do ... done is the standard loop to read lines.

3. Final Answer:

   while read line; do echo $line; done < file.txt -> Option A

4. Quick Check:

   Input redirection with < = C [OK]

Hint: Use < file.txt to feed file lines into the loop [OK]

Common Mistakes:

• Using output redirection (>) instead of input (<)
• Piping file name instead of redirecting input
• Missing the -r option to prevent backslash escapes

3. What will be the output of this script if file.txt contains:

apple
banana
cherry

Script:

while IFS= read -r line; do echo "Fruit: $line"; done < file.txt

medium

A. Fruit: apple
Fruit: banana
Fruit: cherry

B. apple
banana
cherry

C. Fruit: apple banana cherry

D. Syntax error

Solution

1. Step 1: Understand the loop reading each line

   The loop reads each line from file.txt separately.

2. Step 2: Check the echo command

   Each line is printed prefixed with "Fruit: ".

3. Final Answer:

   Fruit: apple Fruit: banana Fruit: cherry -> Option A

4. Quick Check:

   Line prefixing with echo = B [OK]

Hint: Each loop iteration prints one line with prefix [OK]

Common Mistakes:

• Expecting all lines printed on one line
• Ignoring the prefix in echo
• Confusing input and output redirection

4. Identify the error in this script snippet:

while read line; do echo $line; done file.txt

medium

A. Echo command syntax is wrong

B. Incorrect variable name used

C. Missing input redirection operator < before file.txt

D. Missing semicolon after read

Solution

1. Step 1: Check how the file is provided to the loop

   The file must be redirected as input using < file.txt, not as an argument.

2. Step 2: Confirm syntax correctness

   The rest of the syntax is correct; variable and echo usage are fine.

3. Final Answer:

   Missing input redirection operator < before file.txt -> Option C

4. Quick Check:

   Input redirection needed = D [OK]

Hint: Use < file.txt to feed file lines, not argument [OK]

Common Mistakes:

• Passing filename as argument instead of redirecting input
• Forgetting semicolon after read (optional here)
• Misusing echo syntax

5. You want to read a file line by line and skip empty lines. Which script snippet correctly does this?

hard

A. while read line; do echo "$line"; done < file.txt | grep '^$'

B. while IFS= read -r line; do if [[ -n $line ]]; then echo "$line"; fi; done < file.txt

C. cat file.txt | while read line; do echo "$line"; done

D. while IFS= read -r line; do echo "$line"; done < file.txt

Solution

1. Step 1: Understand skipping empty lines

   We need to check if the line is not empty using [[ -n $line ]].

2. Step 2: Confirm reading and condition

   while IFS= read -r line; do if [[ -n $line ]]; then echo "$line"; fi; done < file.txt reads lines safely and prints only non-empty lines inside the loop.

3. Final Answer:

   while IFS= read -r line; do if [[ -n $line ]]; then echo "$line"; fi; done < file.txt -> Option B

4. Quick Check:

   Condition inside loop filters empty lines = A [OK]

Hint: Use if [[ -n $line ]] inside loop to skip empty lines [OK]

Common Mistakes:

• Using external grep after loop (may lose variable scope)
• Not checking for empty lines inside the loop
• Using unnecessary cat command