From: Zefram <A.Main@dcs.warwick.ac.uk>
To: coleman@math.gatech.edu (Richard J. Coleman)
Cc: zsh-workers@math.gatech.edu (Z Shell workers mailing list)
Subject: Re: why is SHINSTDIN an option?
Date: Thu, 11 Apr 1996 06:10:32 +0100 (BST) [thread overview]
Message-ID: <27970.199604110510@stone.dcs.warwick.ac.uk> (raw)
In-Reply-To: <199604110413.AAA24507@redwood.skiles.gatech.edu> 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
next prev parent reply other threads:[~1996-04-11 5:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-04-11 4:13 Richard J. Coleman
1996-04-11 5:10 ` Zefram [this message]
1996-04-11 5:17 ` Barton E. Schaefer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=27970.199604110510@stone.dcs.warwick.ac.uk \
--to=a.main@dcs.warwick.ac.uk \
--cc=coleman@math.gatech.edu \
--cc=zsh-workers@math.gatech.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).