How does `noclobber` prevent overwriting files?

That's a great practical question. noclobber acts as a safety lock for your files when you use redirection.

In the Linux shell, there are two main ways to send text into a file:

1. > (Overwrite): This creates a new file OR completely wipes an existing file and replaces it with new content.
2. >> (Append): This adds new content to the end of an existing file.

Without noclobber (The Risk)

If you have a file called important_data.txt and you accidentally run:

echo "Oops" > important_data.txt

The shell will immediately erase everything in that file and replace it with "Oops". There is no "Undo" button in the terminal!

With noclobber (The Safety Lock)

When you enable it using set -o noclobber, the shell changes its behavior for the > operator:

1. If the file is NEW: It works normally and creates the file.
2. If the file ALREADY EXISTS: The shell will block the command and show an error message like:
   zsh: file exists: important_data.txt

How to "Force" it?

If noclobber is on, but you really want to overwrite a file, you can use a special syntax >| (the pipe symbol inside the redirection):

echo "New Data" >| important_data.txt

This tells the shell: "I know noclobber is on, but I am doing this on purpose."

Summary: It protects you from your own typos and accidents by making sure you don't delete important work by mistake! Try creating a file and then running echo "test" > filename with noclobber on to see the error yourself.