clarify note on shell process creation

This commit is contained in:
Matthew Flatt 2010-07-04 09:53:12 -06:00
parent 608e228530
commit 39f57b23c4

View File

@ -274,7 +274,9 @@ Like @racket[system*], but returns the exit code like
input-port? input-port?
((or/c 'status 'wait 'interrupt 'kill) . -> . any))]{ ((or/c 'status 'wait 'interrupt 'kill) . -> . any))]{
Executes a shell command asynchronously. The result is a list of five values: Executes a shell command asynchronously (using @exec{sh} under Unix
and Mac OS X, @exec{cmd} under Windows). The result is a list of five
values:
@itemize[ @itemize[
@ -304,7 +306,13 @@ Executes a shell command asynchronously. The result is a list of five values:
@item{@racket['interrupt] sends the subprocess an interrupt signal @item{@racket['interrupt] sends the subprocess an interrupt signal
under @|AllUnix|, and takes no action under Windows. The result is under @|AllUnix|, and takes no action under Windows. The result is
@|void-const|.} @|void-const|.
@margin-note{Under Unix and Mac OS X, if @racket[command] runs a
single program, then @exec{sh} typically runs the program in
such a way that it replaces @exec{sh} in the same process. For
reliable and precise control over process creation, however, use
@racket[process*].}}
@item{@racket['kill] terminates the subprocess and returns @item{@racket['kill] terminates the subprocess and returns
@|void-const|. Note that the immediate process created by @|void-const|. Note that the immediate process created by