Every scripting and setup recipe runs as written: fmt-here finds the session itself, the recipes share one stated preamble, run a command waits for its tag, and setup says man reads MANPAGER first

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

1 files changed, 5 insertions, 2 deletions

diff --git a/docs/typ/setup.typ b/docs/typ/setup.typ
index 4769eb49..194156f8 100644
--- a/docs/typ/setup.typ
+++ b/docs/typ/setup.typ
@@ -79,8 +79,11 @@ command line with Ctrl-O in fish instead, add `bind ctrl-o edit_command_buffer`
 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`
+the terminal is back at once; command panes page through `cat`. `man`
+reads `MANPAGER` before `PAGER`, and pardes never sets `MANPAGER`, so a
+`MANPAGER` of yours sends man pages there. A `MANPAGER`, `PAGER` or
+`GIT_PAGER` of your own always wins over pardes's. 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.