Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!pasteur!ames!coherent!mrspoc!itkin
From: itkin@mrspoc.UUCP (Steven M. List)
Newsgroups: comp.databases
Subject: Interactive shells from ACCELL (WAS: Re: Accell 1.3 & Unify 4.0...)
Message-ID: <6000@mrspoc.UUCP>
Date: 16 Mar 89 08:20:25 GMT
References: <198125@hrc.UUCP> <13452@ncoast.ORG>
Reply-To: itkin@mrspoc (Steven List)
Organization: Transact Software, Inc., Mt. View, CA
Lines: 21

In article <13452@ncoast.ORG> allbery@ncoast.UUCP (Brandon S. Allbery) writes:
> I use csh as my shell (one of those old csh's from the PDP-11, pre-job
> control, under System V).  When I shell out from Accell via push_shell$() or
> selecting the menu option from the Development Environment, it prints a
> prompt but doesn't maintain history; i.e. it's only *partially* interactive.
> Adding a wrapper to the shell-out sequence (I save the original value of
> $SHELL in $ACLENV_SHELL and set $SHELL to a program which repairs stderr and
> execs $ACLENV_SHELL) does NOT fix this.  Any ideas?

After reading this, I tried the same thing with an application of mine.
This application allows me to specify the command line to be executed and
then executes it with the ACCELL 1.4 system$() function call.  When I just
called "csh", I had the same problem as Brandon.  When I changed the call
to "csh -i", however, I got history and everything!  It's certainly possible
to invoke a wrapper program, as Brandon did, that would add the "-i" option
to the shell command.
-- 
:  Steven List @ Transact Software, Inc. :^>~
:  Chairman, Unify User Group of Northern California
:  {apple,coherent,limbo,mips,pyramid,ubvax}!mrspoc!itkin
:  Voice: (415) 961-6112