The docs say a look's :col counts bytes, as addr's and every row's do

Columns are bytes everywhere a row is written (Grep, the language servers) and read (addr, look); the look's spelling did not say so.

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 6084b834..83906d0a 100644
--- a/docs/fs.md
+++ b/docs/fs.md
@@ -546,7 +546,9 @@ at #0 as sam does (a search never answers where it started), so it finds
 the next one: for the start itself write `file:0` or `file:#0`.
 `:addr` does the same in the pane itself, and a pattern may hold blanks
 (`calc.py:/return a/`). `file:12` selects line 12, its newline included,
-as acme's does; `file:12:5` puts the caret at line 12, column 5. A bare
+as acme's does; `file:12:5` puts the caret at line 12, column 5 (columns count bytes from 1,
+as `addr`'s `12:5` does and as the rows of Grep, +Search and the language
+servers write them). A bare
 `/re/` is a path, as in acme, and failing that a search for its text. A
 look that finds nothing, an address that does not evaluate, or a line past
 the file's end (`calc.py:99`) says so on the message row and in the log