From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: INTERACTIVE vs. SHINSTDIN
Date: Sun, 25 Mar 2001 23:49:53 +0000 [thread overview]
Message-ID: <1010325234953.ZM11680@candle.brasslantern.com> (raw)
zagzig[514] Src/zsh -fis <<<'echo hi'
zagzig% read -e
echo hi
zagzig% cat
zagzig%
Hmm, so SHINSTDIN is true, but in fact the shell is not reading commands
from stdin ... yet commands started by the shell read from the actual stdin,
not from where the shell is reading commands from ... I suppose one can get
some interesting effects this way, but is it really the correct behavior?
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next reply other threads:[~2001-03-25 23:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-25 23:49 Bart Schaefer [this message]
2001-03-27 18:12 ` Zefram
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=1010325234953.ZM11680@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=zsh-workers@sunsite.dk \
/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).