From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from gatech.edu (gatech.edu [130.207.244.244]) by werple.mira.net.au (8.6.12/8.6.9) with SMTP id BAA12924 for <mason@werple.mira.net.au>; Sat, 17 Jun 1995 01:03:06 +1000
Received: from math (math.skiles.gatech.edu) by gatech.edu with SMTP id AA05978
  (5.65c/Gatech-10.0-IDA for <mason@werple.mira.net.au>); Fri, 16 Jun 1995 10:55:45 -0400
Received: by math (5.x/SMI-SVR4)
	id AA18460; Fri, 16 Jun 1995 10:51:59 -0400
Resent-Date: Fri, 16 Jun 95 15:49:23 +0100
Old-Return-Path: <P.Stephenson@swansea.ac.uk>
Message-Id: <30420.9506161449@pyro.swan.ac.uk>
To: zsh-workers@math.gatech.edu (Zsh hackers list)
Subject: Re: interact
In-Reply-To: "Anthony.Iano-Fletcher@maths.nott.ac.uk"'s message of "Fri, 16 Jun 95 13:32:08 BST." <9506161232.AA01701@guinness>
Date: Fri, 16 Jun 95 15:49:23 +0100
From: P.Stephenson@swansea.ac.uk
X-Mts: smtp
Resent-Message-Id: <"5qX_C1.0.IW4.DgPul"@math>
Resent-From: zsh-workers@math.gatech.edu
X-Mailing-List: <zsh-workers@math.gatech.edu> archive/latest/108
X-Loop: zsh-workers@math.gatech.edu
Precedence: list
Resent-Sender: zsh-workers-request@math.gatech.edu

Anthony.Iano-Fletcher@maths.nott.ac.uk wrote:
> > In principle, you could move the
> > setting of the interactive option into the code I just adapted to be
> > run both when the shell starts up and after `exec <...', which already
> > checks for a tty.  You probably have to wait a bit for that code to
> > show up.
> 
> Fine I can wait...... Would this allow for the zsh script to call for
> more that one interactive sessions? or to continue executing after
> the exec?  Surely if I do 
> 
> 		exec < /dev/tty
> 
> and the user types control-D then the shell will exit.

I looked at this a little more closely --- it turns out it's not
ksh-compatible: running ksh on a file containing

print this is before
exec <file
print this is after

shows that it doesn't change command input to stdin, only input for
'read' etc.

It might therefore be better to implement this a more specific way,
like handling `setopt interactive' specially, then passing initio() or
whatever a flag saying whether it has to switch to using stdin for
input.  This is certainly feasible, though probably it ought to wait:
it looks like being a bigger change than I'd hoped to do it properly.
If done properly, though, interactive sessions should be able to
behave just like they usually do.

-- 
Peter Stephenson <P.Stephenson@swansea.ac.uk>  Tel: +44 1792 205678 extn. 4461
WWW:  http://python.swan.ac.uk/~pypeters/      Fax: +44 1792 295324
Department of Physics, University of Wales, Swansea,
Singleton Park, Swansea, SA2 8PP, U.K.