After a failed address, one that goes from it (., +, -) says there is none

addr kept the old address under a failed one, and an address written relative to it went from that old one. Such an address now fails with no address: the last one written to addr failed, until one that stands alone is written.

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

1 files changed, 3 insertions, 1 deletions

diff --git a/docs/fs.md b/docs/fs.md
index fdcbdaf0..700ec97b 100644
--- a/docs/fs.md
+++ b/docs/fs.md
@@ -740,7 +740,9 @@ address at all, where acme
 keeps the old one: until a good address is written, `addr` reads empty
 (as an unset `limit` does), and reading, writing or truncating `data` and
 `xdata` fail with `no address: the last one written to addr failed`, so a script that
-missed its target cannot then write at the last one.
+missed its target cannot then write at the last one; so does an address
+written to `addr` that goes from the current one (`.`, `+1`, `-/re/`), which
+there is none of, until an address that stands alone (`2`, `#0`, `/re/`) is.
 
 The three flag files `dirty`, `mark` and `scroll` read `0` or `1` and take
 `0` or `1`: whether the buffer differs from its file, whether a write pushes