[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: System Calls from CLISP
- To: <firstname.lastname@example.org>
- Subject: Re: System Calls from CLISP
- From: Bruno Haible <email@example.com>
- Date: Tue, 24 Jun 1997 15:03:23 +0200 (MET DST)
- >received: from halles.ilog.fr (halles.ilog.fr [172.16.1.96]) by ilog.ilog.fr (8.8.6/8.7.3) with ESMTP id PAA14102; Tue, 24 Jun 1997 15:03:25 +0200 (MET DST)
- In-reply-to: <9706231317.ZM19532@bs724.comm.mot.com>
- References: <9706231317.ZM19532@bs724.comm.mot.com>
Art Nuzzo <firstname.lastname@example.org>:
> Probably for what I am doing 'run-shell-command' or `run-program' ('SHELL' or
> EXECUTE) would be sufficient since I would be calling standard UNIX system
> commands (such as ps or who or ping, etc). Is there any way to capture the
> unix command output in a variable so it can be processed?
Yes, you can do this with `run-shell-command' and `run-program'.
Documentation for these two functions, as for any CLISP specific stuff,
is in impnotes.txt (if you got a binary distribution) or _impnotes.txt (if
you got the source).