The docs describe the pager that landed: pardes - and its +Pager pane, a terminal's PAGER, command panes' cat, Pager pardes|off, and pty/run no longer waiting in one

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

1 files changed, 9 insertions, 9 deletions

diff --git a/docs/typ/setup.typ b/docs/typ/setup.typ
index 8cf8b091..4769eb49 100644
--- a/docs/typ/setup.typ
+++ b/docs/typ/setup.typ
@@ -75,15 +75,15 @@ command line with Ctrl-O in fish instead, add `bind ctrl-o edit_command_buffer`
 
 = A pager <pager>
 
-// PENDING: written to the 9P agent's pager design, which is not on main
-// yet; check every line against its change when it lands.
-`pardes -` reads its standard input into a `+Pager` pane. Terminal panes
-get `PAGER='pardes -'` and `GIT_PAGER='pardes -'` by themselves, unless
-your environment sets them, so `git log` or `man` output arrives as a pane
-to search and click in; command panes get `cat`. `Pager off` (on the root
-ctl, or a line in the startup file) turns it off, `Pager pardes` back on.
-To keep your own pager in pardes's terminals, set `PAGER` in your
-environment; to use pardes's outside them, set it to `pardes -` yourself.
+`pardes -` reads its standard input into a `+Pager` pane, escapes
+stripped. Terminals get `PAGER` and `GIT_PAGER` set to it (this pardes's
+own path, then `-`) by themselves unless your environment sets them, so
+`git log` or `man` output arrives as a pane to search and click in, and
+the terminal is back at once; command panes page through `cat`. To keep
+your own pager, either set `PAGER` in your environment, or put `Pager off`
+in the startup file (or write it to the root ctl); it applies to terminals
+started after it. Outside pardes, `PAGER='pardes -'` opens a new editor on
+the text.
 
 = yazi in a terminal pane <yazi>