Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: why is SHINSTDIN an option?

X-seq: zsh-workers 919
From: Zefram <A.Main@xxxxxxxxxxxxxxxxx>
To: coleman@xxxxxxxxxxxxxxx (Richard J. Coleman)
Subject: Re: why is SHINSTDIN an option?
Date: Thu, 11 Apr 1996 06:10:32 +0100 (BST)
Cc: zsh-workers@xxxxxxxxxxxxxxx (Z Shell workers mailing list)
In-reply-to: <199604110413.AAA24507@xxxxxxxxxxxxxxxxxxxxxxxxx> from "Richard J. Coleman" at Apr 11, 96 00:13:51 am

>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

References:
- why is SHINSTDIN an option?
  - From: Richard J. Coleman

Messages sorted by: Reverse Date, Date, Thread, Author