summaryrefslogtreecommitdiff
path: root/src/tutor.txt
diff options
context:
space:
mode:
Diffstat (limited to 'src/tutor.txt')
-rw-r--r--src/tutor.txt25
1 files changed, 13 insertions, 12 deletions
diff --git a/src/tutor.txt b/src/tutor.txt
index ae22ede9..394a48a3 100644
--- a/src/tutor.txt
+++ b/src/tutor.txt
@@ -387,29 +387,30 @@ typed
pardes the 9P socket opens by default
- A directory per pane holding `body`, `tag`, `ctl`, `addr`, `data`,
- `event`, `pty/` and the rest, plus `index`, `cons` and `new/` at the
- top under /self. Every pane shell receives `$PARDES_9P` (the socket)
- and `$PARDES_PANE` (its serial). Use a 9P client to read and write:
+ A directory per pane holding `name`, `body`, `tag`, `ctl`, `addr`,
+ `data`, `sel`, `event`, `pty/` and the rest, plus `index`, `ctl`,
+ `new` and `log` at the root. Every pane shell receives `$PARDES_9P`
+ (the socket) and `$PARDES_PANE` (its serial). Use a 9P client:
- /self/pane/<serial>/body
- /self/index
- /self/new/ctl
+ /pane/<serial>/body
+ /index
+ /new reading it makes a pane, answers its serial
+ /ctl `look FILE:12` and `exec Save`, as the mouse does
A terminal pane also has `pty/`:
- /self/pane/3/pty/ctl winsize, sig
- /self/pane/3/pty/data terminal input/output
+ /pane/3/pty/ctl winsize, sig
+ /pane/3/pty/data terminal input/output
Over 9P the same tree answers plan9port, from anywhere:
9p -a $XDG_RUNTIME_DIR/pardes-9p-work.sock ls /
- 9p -a $XDG_RUNTIME_DIR/pardes-9p-work.sock read /self/index
+ 9p -a $XDG_RUNTIME_DIR/pardes-9p-work.sock read index
...and pardes is a 9P CLIENT too, so one session can read another's:
pardes --mount=peer=work
- /n/peer/self/pane/1/body Look opens the other session's body
+ /n/peer/pane/1/body Look opens the other session's body
TWO THINGS WORTH KNOWING. While a program holds a pane's `event` file
open, MIDDLE AND RIGHT CLICKS IN THAT PANE BELONG TO IT: pardes reports
@@ -467,7 +468,7 @@ typed
SPC is the leader (SPC ? lists every path)
SCRIPTING 9P is served by default on $PARDES_9P
- /self/pane/<id>/{body,tag,ctl,addr,data,event,pty/}
+ /pane/<id>/{name,body,tag,ctl,addr,data,sel,event,pty/}
a script holding `event` owns that pane's middle and right
clicks; writing a record back runs it