Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!mcvax!nikhefh!gert
From: gert@nikhefh.UUCP (Gert Poletiek)
Newsgroups: comp.sys.atari.st
Subject: Re: Correct use of _shell_p  (Csh-like shell, fast editor, make...)
Message-ID: <284@nikhefh.UUCP>
Date: Mon, 25-May-87 04:23:50 EDT
Article-I.D.: nikhefh.284
Posted: Mon May 25 04:23:50 1987
Date-Received: Tue, 26-May-87 00:49:16 EDT
References: <276@nikhefh.UUCP> <1019@viper.Lynx.MN.ORG> <279@nikhefh.UUCP> <1083@batcomputer.tn.cornell.edu>
Reply-To: gert@nikhefh.UUCP (Gert Poletiek)
Organization: Nikhef-H, Amsterdam (the Netherlands).
Lines: 25
Keywords: _shell_p, shell

In article <1083@batcomputer.tn.cornell.edu> braner@tcgould.tn.cornell.edu.UUCP (braner) writes:
>[]
>
>Gert's shell sounds very good.  But meanwhile, can some hackers out there
>(or perhaps the shell authors!) tell us how to hook into the command line
>interpreters of the commonly used shells?  (mCS, MWC, GULAM)
>
>- Moshe Braner


Sorry out of luck. None of the shells I know (except ofcourse my own) cannot
be called from a child process. The MWC development system provides a 
'system' call, but this merely starts a new shell, therefor using 'system'
with MWC seems to take forever.

My own shell is completely recursive to allow shell scrips to be run by 
the same instance of the shell that accepts keyboard commands. Only a slight
deviation  from complete recursiveness will make it impossible to implement
the system call interface as my shell does. 

As for mCS: it can't do what you have in mind.....



Gert Poletiek.