From e398c8e2b2cd844cc2e14ec3ec7cc99b6574447d Mon Sep 17 00:00:00 2001 From: Vsevolod Stakhov Date: Thu, 12 Feb 2026 16:27:21 +0000 Subject: [PATCH] [Minor] Try to fix CC issue with tabs --- CLAUDE.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/CLAUDE.md b/CLAUDE.md index 4c26a96a18..073669f805 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -78,3 +78,20 @@ Format: `[Tag] Description` Tags: `[Feature]`, `[Fix]`, `[CritFix]`, `[Minor]`, `[Project]`, `[Rework]`, `[Conf]`, `[Test]`, `[Rules]` All commits must be GPG-signed (`git commit -S`). + +## Edit Tool - Whitespace Handling + +The Read tool uses `→` to mark where line numbers end and file content begins. + +**Rule:** Copy the EXACT whitespace that appears after the `→` marker. +- Whatever appears between `→` and the code text is what's actually in the file +- That whitespace must be used EXACTLY in Edit tool's old_string +- Don't count arrows, don't interpret - just copy what's after the `→` + +**Example:** +14→ private byte tag; +For Edit, use: ` private byte tag;` (copy everything after →, including the two tabs) + +**If Edit fails:** Stop and explain the problem. Do not attempt sed/awk/bash workarounds. + +**IMPORTANT**: Trust the Read tool output. Copy what's after `→` into Edit immediately. DO NOT verify with sed/od/grep first - that's wasting time and the instructions already tell you to stop if Edit fails, not to pre-verify. -- 2.47.3