From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from euclid.skiles.gatech.edu (list@euclid.skiles.gatech.edu [130.207.146.50]) by melb.werple.net.au (8.7.5/8.7.3) with ESMTP id PAA09047 for ; Thu, 11 Apr 1996 15:16:16 +1000 (EST) Received: (from list@localhost) by euclid.skiles.gatech.edu (8.7.3/8.7.3) id BAA26530; Thu, 11 Apr 1996 01:10:46 -0400 (EDT) Resent-Date: Thu, 11 Apr 1996 01:10:46 -0400 (EDT) From: Zefram Message-Id: <27970.199604110510@stone.dcs.warwick.ac.uk> Subject: Re: why is SHINSTDIN an option? To: coleman@math.gatech.edu (Richard J. Coleman) Date: Thu, 11 Apr 1996 06:10:32 +0100 (BST) Cc: zsh-workers@math.gatech.edu (Z Shell workers mailing list) In-Reply-To: <199604110413.AAA24507@redwood.skiles.gatech.edu> from "Richard J. Coleman" at Apr 11, 96 00:13:51 am X-Loop: zefram@dcs.warwick.ac.uk X-Stardate: [-31]7336.07 X-US-Congress: Moronic fuckers MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Resent-Message-ID: <"DCPYj3.0.SU6.LH9Rn"@euclid> Resent-From: zsh-workers@math.gatech.edu X-Mailing-List: archive/latest/919 X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu >Is there any reason for SHINSTDIN to be an option? >In the code, it seems to primarily be used a global variable >keeping track of where the input stream is coming from. Since >the code changes it so often, is there any time where a user >would want to set this himself? I was wondering that myself. It doesn't actually seem to be very meaningful. Its only purpose seems to be to allow user code to test it, but I don't see why one would want to do that -- INTERACTIVE is a better test of interactiveness. But the corresponding command line option, -s, must remain, so I recommend that SHINSTDIN should stay. I think, however, it should become read-only, like INTERACTIVE. It is already read-only in the Bourne shell here. -zefram