From ecc760cfb353b7ee858974e60f730fd01ae4374c Mon Sep 17 00:00:00 2001
From: mainzelm <mainzelm>
Date: Sun, 21 Apr 2002 16:35:04 +0000
Subject: [PATCH] Documented optional continue-threads argument for fork/pipe
 and fork/pipe+.

---
 doc/scsh-manual/syscalls.tex | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/doc/scsh-manual/syscalls.tex b/doc/scsh-manual/syscalls.tex
index 8fbc189..848b018 100644
--- a/doc/scsh-manual/syscalls.tex
+++ b/doc/scsh-manual/syscalls.tex
@@ -1823,8 +1823,8 @@ Suspend the current process with a SIGSTOP signal.
   not.  The default is \sharpf.
 \end{desc}
 
-\defun {fork/pipe}  {[thunk]} {proc or \sharpf}
-\defunx{\%fork/pipe} {[thunk]} {proc or \sharpf}
+\defun {fork/pipe}  {[thunk] [continue-threads?]} {proc or \sharpf}
+\defunx{\%fork/pipe} {[thunk] [continue-threads?]} {proc or \sharpf}
 \begin{desc}
     Like \ex{fork} and \ex{\%fork}, but the parent and child communicate via a
     pipe connecting the parent's stdin to the child's stdout. These procedures
@@ -1875,7 +1875,7 @@ Suspend the current process with a SIGSTOP signal.
              (with-current-output-port (fdes->outport 1)
                (display "Hello, world.\\n"))))
 
-(set-current-input-port! (fdes->inport 0)
+(set-current-input-port! (fdes->inport 0))
 (read-line)     ; Read the string output by the child.\end{code}
 None of this is necessary when the I/O is performed by an exec'd
 program in the child or parent process, only when the pipe will
@@ -1883,8 +1883,8 @@ be referenced by Scheme code through one of the default current I/O
 ports.
 \end{desc}
 
-\defun  {fork/pipe+}  {conns [thunk]} {proc or \sharpf}
-\defunx {\%fork/pipe+} {conns [thunk]} {proc or \sharpf}
+\defun  {fork/pipe+}  {conns [thunk] [continue-threads?]} {proc or \sharpf}
+\defunx {\%fork/pipe+} {conns [thunk] [continue-threads?]} {proc or \sharpf}
 \begin{desc}
     Like \ex{fork/pipe}, but the pipe connections between the child and parent
     are specified by the connection list \var{conns}.