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 OAA08233 for ; Thu, 11 Apr 1996 14:25:03 +1000 (EST) Received: (from list@localhost) by euclid.skiles.gatech.edu (8.7.3/8.7.3) id AAA25938; Thu, 11 Apr 1996 00:15:27 -0400 (EDT) Resent-Date: Thu, 11 Apr 1996 00:15:27 -0400 (EDT) Message-Id: <199604110413.AAA24507@redwood.skiles.gatech.edu> X-Mailer: exmh version 1.6.6 3/24/96 To: zsh-workers@math.gatech.edu Subject: why is SHINSTDIN an option? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 11 Apr 1996 00:13:51 -0400 From: "Richard J. Coleman" Resent-Message-ID: <"JxNLD1.0.9L6.TT8Rn"@euclid> Resent-From: zsh-workers@math.gatech.edu X-Mailing-List: archive/latest/918 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? rc