diff options
| author | Gabriel Schneider <[email protected]> | 2026-09-28 13:09:12 -0300 |
|---|---|---|
| committer | Gabriel Schneider <[email protected]> | 2026-10-01 00:12:14 -0300 |
| commit | 84fca2d6e5f498f2d4384712d49d727a25441d68 (patch) | |
| tree | 47a6d01ee65c5d631f59bee2f1efc5685ceb95f4 /.agents | |
| parent | 047a2b50a7ac0162d7ef38f912d41c15a47479c7 (diff) | |
| download | pardes-84fca2d6e5f498f2d4384712d49d727a25441d68.tar.gz pardes-84fca2d6e5f498f2d4384712d49d727a25441d68.zip | |
A click that takes no text tells the event reader nothing, and click records are tested for their offsets
Dogfooding saw a body right-click reported as ML0 0 2 3 qty. On file panes
the offsets were right in every case tried here (a scratch made over 9P and
clicked while another pane is active, after a hover, scrolled, soft-wrapped,
tab-indented, inside parentheses); the test now holds them. The 0 0 form
is a terminal's body, which has no offsets to give (its body is a history
snapshot); since the event file now takes a record back whole, such a record
can still be written back and done, and the docs say so. What the test did
find: a click on whitespace sent an empty record, where acme's look3 and
execute return without a word on an empty expansion (look.c:37, exec.c:141).
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Diffstat (limited to '.agents')
| -rw-r--r-- | .agents/skills/pardes-9p/SKILL.md | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/.agents/skills/pardes-9p/SKILL.md b/.agents/skills/pardes-9p/SKILL.md index c9efec0b..6346e7b4 100644 --- a/.agents/skills/pardes-9p/SKILL.md +++ b/.agents/skills/pardes-9p/SKILL.md @@ -211,7 +211,8 @@ not the read-until-EOF helper. `pty/data` captures output while held open; it is not a history replay. Both files are shared, consuming queues, not per-client broadcasts, so a slow reader loses older data. Holding `event` open intercepts that pane's Look and Exec clicks -- and lines written to that pane's -own `look`/`exec`, as `F` records at `0 0` with the text -- so it is not a +own `look`/`exec`, as `F` records at `0 0` with the text, and clicks in a +terminal's body, also at `0 0` -- so it is not a passive logger. To have a record done, write it back: the short form `<origin><action><q0> <q1>\n` acts on that range's text, and the whole record as read acts on its text when the range is empty (the only way for a record |