The Heredoc Trick: One Paste, Zero Friction

By markjc Mon Jun, 2026 (0)

The Heredoc Trick: One Paste, Zero Friction

0

Vote for this post

Click the arrows to vote • 1 vote per logged in user
Login to Vote

The Heredoc Trick: One Paste, Zero Friction

For months the routine never changed. Open Notepad++. Find the file. Select all. Delete. Paste. Save. Repeat for every single file Claude touched. It worked, but it was friction — five steps standing between an idea and a working change.

Then came one small shell trick that quietly rewrote that whole routine: the heredoc.

What a Heredoc Actually Does

A heredoc is a Bash feature that lets a terminal command swallow a whole multi-line block of text in one go, instead of typing it line by line. The syntax is almost deceptively simple: cat > somefile.php << 'EOF', followed by everything that belongs in the file, followed by a closing EOF on its own line. Bash reads everything between those two markers and writes it straight to disk, then closes the file the moment it sees the closing marker.

The single quotes around EOF matter more than they look. They tell Bash to treat the block as inert text — no shell expansion, no attempt to substitute a $variable. That detail is not cosmetic when the file being written is full of PHP and Blade code, which leans on $variables in nearly every line.

Git Bash terminal running a heredoc command

One paste into Git Bash, and the file exists exactly as written — no editor required.

Why It Changed the Workflow

Claude gives one block: cat > path/to/file.php << 'EOF' followed by the complete file, followed by a closing EOF. That block gets pasted into Git Bash once. The file is created, or completely overwritten, character for character, in the time it takes to press Enter.

Before Heredoc vs. After Heredoc

Open Notepad++, hunt for the right file in the right folder
Select all, hope nothing was missed, delete
Paste, save, hope the encoding survived
One paste into Git Bash creates or overwrites the file in full
A follow-up grep confirms the change landed, no editor needed
New files for a fresh module exist the instant the terminal returns

Now with heredoc Claude just gives me to completed code and if I like what I see I copy and paste. I.e. see the example of this class below. A short one but Claude and I have handled code running into thousands of lines like this. And repetitive work. i.e. Step 1. Step 2. Step 3. (like the one below)

This is how Claude gives me the information

No partial selections, no missed lines — the file becomes exactly what was pasted. I copy the code. Right click on my code folder. Open as Git Bash and paste and enter. And then, class created, and checked then Bob is your uncle! Hit me with the next one Claude!

The Real Win Is Not Speed — It Is Certainty

A heredoc paste cannot leave half the old file behind. It cannot silently keep a stray line that was never deleted. The file becomes exactly, character for character, what was in the block. For anyone working directly on a live production site with no separate development environment, that certainty matters more than the seconds saved.

One Word of Caution: Protect the Database

The same exactness that makes heredoc reliable for code makes it unforgiving for data. A stray quote or apostrophe pasted straight into a SQL statement, or into a PHP array destined for a database seeder, can break the query or open the door to a SQL injection style problem. Anything heading into the database, whether through a seeder, a tinker session, or a raw query, should go through proper escaping or parameter binding first. Heredoc moves text faithfully. It has no concept of safe text versus dangerous text, so that judgement still belongs to the person doing the pasting.