An Edit x gives each of its searches the step budget, and a search that spends it says it took too much time

The budget was the compiled pattern's, spent over every search an x made: Edit ,x/x+/c/z/ over 100k lines ran out and failed, blamed on backtracking. Each search now starts with the whole budget, and one that spends it says regular expression search took too much time, gave up. (Not "too long": 9ns reads those words as ENAMETOOLONG.)

Co-Authored-By: Claude Opus 5.5 <[email protected]>

1 files changed, 3 insertions, 3 deletions

diff --git a/.agents/skills/pardes-9p/SKILL.md b/.agents/skills/pardes-9p/SKILL.md
index 0de8820a..7e1c7d98 100644
--- a/.agents/skills/pardes-9p/SKILL.md
+++ b/.agents/skills/pardes-9p/SKILL.md
@@ -295,9 +295,9 @@ refused, not silently unmatched. `^def|^ ` finds lines starting either way
 written, or just past the last `data` write): `.` is that address, not the
 selection, `/re/` searches on from its end and wraps unless `limit` is set,
 `?re?` or `-/re/` searches back, `#100,#50` fails `addresses out of order`,
-and a search that backtracks
-past a step budget (about 300 ms) fails with `regular expression search
-gave up, ...`. A failed address says
+and one search that runs past its step budget (about 300 ms; each search of
+an Edit `x` has its own) fails with `regular expression search took too
+much time, gave up`. A failed address says
 why (`no match for regexp`, `address out of range`) and leaves no address:
 `addr` reads empty and `data` refuses until the next good one, so a missed target is never
 written at the old one. Moving `dot` scrolls the pane to it. `limit` bounds