summaryrefslogtreecommitdiff
path: root/src/macos/Sources/ScenePostprocessor.swift
diff options
context:
space:
mode:
authorGabriel Schneider <[email protected]>2026-09-28 13:14:20 -0300
committerGabriel Schneider <[email protected]>2026-10-01 00:12:14 -0300
commit41fb292f314844d1f47e608fbdd4a34cfc8d5618 (patch)
tree5f0b6f9bd6feddb88881623a6d990bcab454021e /src/macos/Sources/ScenePostprocessor.swift
parent84fca2d6e5f498f2d4384712d49d727a25441d68 (diff)
downloadpardes-41fb292f314844d1f47e608fbdd4a34cfc8d5618.tar.gz
pardes-41fb292f314844d1f47e608fbdd4a34cfc8d5618.zip
An address searches back after a minus, and a range ending before its start is refused
-/re/ searched forward, since only ?re? set the direction, where acme's address() takes the direction a minus set (addr.c). And #100,#50 was taken, leaving data to act on an empty range at 100; sam refuses it as 'addresses out of order', which acme leaves out, and so does pardes now. The rest of the dogfood report on addresses already held and is now tested: an expression is evaluated from the current address, as acme evaluates it from w->addr (xfid.c:446), so a search starts where the last address or data write left it and . is that address. Taking . as the selection instead, as the report asked, would part from acme, which has dot only in its ctl messages; the docs say which is which. Co-Authored-By: Claude Opus 5.5 <[email protected]>
Diffstat (limited to 'src/macos/Sources/ScenePostprocessor.swift')
0 files changed, 0 insertions, 0 deletions