Re: Re[2]: [clisp-list] Separate Unix error stream keyword for ext:run-shell-command

[Adam W. <li...@co...>]

On Thu, 2003-06-05 at 02:51, Arseny Slobodjuck wrote:
> >> In August last year a missing error stream keyword for
> >> ext:run-shell-command was discussed and Marco Baringer said he'd be
> >> "happy to take a whack at" implementing it. Did this ever get
> >> implemented in the CVS version of CLISP?
> 
> > Arseny is working on this - see EXT::LAUNCH (internal!)
> 
> I'm slighltly confused about making it user-level. It is very similar
> to run-program and run-shell-command but it is more `direct' and does
> slightly more. But old ones are available on OS/2 (I'm not sure
> whether current clisp is still compileable on OS/2). Well, I'll
> document it and make user level. This is short description for
> discussion. BTW, Sam, did you changed default behavior to `don\'t wait'
> intentionally ?
> 
> /* (LAUNCH executable [:arguments] [:wait] [:input] [:output] [:error])
>    Launches a program.
>    :arguments : a list of strings
>    :wait - nullp/not nullp - whether to wait for process to finish
>    :priority : on windows : HIGH/LOW/NORMAL on UNIX : fixnum - see nice(2)
>    :input, :output, :error - i/o/e streams for process. basically file-streams
>      or terminal-streams. see stream_lend_handle() in stream.d for full list
>      of supported streams
>      returns: exit code (zero when (nullp wait))  */

Looks great. I'll be able to eliminate all the unnecessary but verbose
messages currently clutering up my Apache logs (e.g. every time ls
"fails" by not finding a particular wildcard match--Note that I do know
about other file location options).

Thanks,
Adam