Appending to files (>>) in Bash Scripting - Step-by-Step Execution

Concept Flow - Appending to files (>>)

Start

↓

Run command with >>

↓

Check if file exists

↓

Open file in append mode

↓

Write output at file end

↓

Close file

↓

End

The shell runs a command, then appends its output to the end of a file, creating the file if it doesn't exist.

Execution Sample

Bash Scripting

echo "Hello" >> greetings.txt
cat greetings.txt

This script adds the word 'Hello' to the end of greetings.txt, then shows the file content.

Execution Table

Step	Command	File Exists?	Action	File Content After
1	echo "Hello" >> greetings.txt	No	Create greetings.txt and write 'Hello\n'	Hello
2	echo "World" >> greetings.txt	Yes	Append 'World\n' to greetings.txt	Hello World
3	cat greetings.txt	Yes	Display file content	Hello World
4	echo "!" >> greetings.txt	Yes	Append '!\n' to greetings.txt	Hello World !

💡 All commands executed; file content updated by appending each echo output.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 4
greetings.txt content	(file does not exist)	Hello	Hello World	Hello World !

Key Moments - 3 Insights

Why does the file get created if it does not exist when using >>?

Because the shell opens the file in append mode, which creates the file if missing, as shown in execution_table step 1.

Does >> overwrite the existing file content?

No, it adds new content at the end. See execution_table steps 2 and 4 where content grows without losing previous lines.

What happens if you use a single > instead of >>?

The file would be overwritten each time, losing previous content. This differs from >> which appends, as shown in the concept flow.

Visual Quiz - 3 Questions

Look at the execution_table, what is the content of greetings.txt after step 2?

A "World\n"

B "Hello\nWorld\n"

C "Hello\n"

D "Hello\n!\n"

💡 Hint

Check the 'File Content After' column for step 2 in the execution_table.

At which step does the file greetings.txt get created?

A Step 2

B Step 3

C Step 1

D Step 4

💡 Hint

Look at the 'File Exists?' column and see when it says 'No' in execution_table.

If we replaced >> with > in step 2, what would be the file content after step 2?

A "World\n"

B "Hello\nWorld\n"

C "Hello\n"

D '' (empty file)

💡 Hint

Using > overwrites the file, so only the last echo output remains, check concept_flow for difference.

Concept Snapshot

Appending to files with >>
- Syntax: command >> filename
- Appends output to file end
- Creates file if missing
- Does NOT erase existing content
- Use > to overwrite instead

Full Transcript

This visual trace shows how the bash append operator >> works. When you run a command like echo "Hello" >> greetings.txt, the shell checks if greetings.txt exists. If not, it creates it and writes 'Hello' plus a newline. If the file exists, it opens it in append mode and adds the new output at the end without deleting previous content. This is different from using > which overwrites the file. The execution table shows step-by-step how the file content grows as more echo commands append lines. The variable tracker highlights the file content changes after each append. Key moments clarify common confusions like file creation and difference from overwrite. The quiz tests understanding of file content after each step and the behavior of >> versus >.