From c9c845b95d586fdefd9dd631a20f74a01873d4d5 Mon Sep 17 00:00:00 2001 From: ram <ram> Date: Tue, 1 Oct 1991 18:02:11 +0000 Subject: [PATCH] Documented "Typescript Slave Status". --- docs/hem/user/lisp.mss | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/docs/hem/user/lisp.mss b/docs/hem/user/lisp.mss index 07093b4f1..fc749caa9 100644 --- a/docs/hem/user/lisp.mss +++ b/docs/hem/user/lisp.mss @@ -296,6 +296,7 @@ which buffer is waiting for input. @defcom[com "Typescript Slave BREAK", bind (Typescript: H-b)] @defcom1[com "Typescript Slave to Top Level", bind (Typescript: H-g)] +@defcom1[com "Typescript Slave Status", bind (Typescript: H-s)] Some typescripts have associated information which these commands access allowing @hemlock to control the process which uses the typescript. @@ -306,6 +307,16 @@ or @f[^\] in the editor process). @hid[Typescript Slave to Top Level] causes the current process to throw to the top-level @f[read-eval-print] loop. This is similar in effect to a quit signal (@f[^\]). + +@hid[Typescript Slave Status] causes the current process to print status +information on @var[error-output]: +@lisp +; Used 0:06:03, 3851 faults. In: SYSTEM:SERVE-EVENT +@endlisp +The message displays the process run-time, the total number of page faults and +the name of the currently running function. This command is useful for +determining whether the slave is in an infinite loop, waiting for input, or +whatever. @enddefcom -- GitLab