From: Roman Neuhauser <neuhauser@sigpipe.cz>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: zsh-users@zsh.org
Subject: Re: set -F kills read -t
Date: Wed, 19 Mar 2014 18:22:13 +0100 [thread overview]
Message-ID: <20140319172213.GE53100@isis.sigpipe.cz> (raw)
In-Reply-To: <5329CF1C.5020109@eastlink.ca>
# rayandrews@eastlink.ca / 2014-03-19 10:08:44 -0700:
> I thought I was expecting this to work:
>
> $ y () { echo "$1, $2, $3 "; }
>
> $ y one two three
> one, two, three
>
> $ echo "one two three" | y
> , , << :-(
what would you expect to happen in
$ echo "one two three" | y foo bar baz
> So grep is doing the 'switcheroo' here--going from reading arguments, to
> reading stdin, and the pipe is the de facto 'stdin', and piped input
> does NOT become arguments :-)
de facto? stdin is stdin no matter what 'file' the descriptor names.
--
roman
next prev parent reply other threads:[~2014-03-19 17:22 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-02 14:26 implementing a control for completing filenames with a defined list of tokens Eric Smith
2013-12-02 15:58 ` Bart Schaefer
2014-03-16 14:13 ` Eric Smith
2014-03-16 19:27 ` Bart Schaefer
2014-03-16 20:13 ` Bart Schaefer
2014-03-18 3:10 ` set -F kills read -t Ray Andrews
2014-03-18 6:50 ` Bart Schaefer
2014-03-18 16:22 ` Ray Andrews
2014-03-18 16:47 ` Peter Stephenson
2014-03-18 17:45 ` Bart Schaefer
2014-03-18 22:08 ` Ray Andrews
2014-03-18 23:12 ` Jan Larres
2014-03-19 4:06 ` Ray Andrews
2014-03-19 5:30 ` Jan Larres
2014-03-19 15:23 ` Ray Andrews
2014-03-19 20:00 ` Bart Schaefer
2014-03-20 1:47 ` Ray Andrews
2014-03-19 1:17 ` Bart Schaefer
2014-03-19 5:00 ` Ray Andrews
2014-03-19 6:37 ` Bart Schaefer
2014-03-19 17:08 ` Ray Andrews
2014-03-19 17:22 ` Roman Neuhauser [this message]
2014-03-19 22:21 ` Bart Schaefer
2014-03-20 1:46 ` Ray Andrews
2014-03-20 4:21 ` Bart Schaefer
2014-03-20 15:49 ` Ray Andrews
2014-03-20 16:08 ` Bart Schaefer
2014-03-20 21:27 ` Ray Andrews
2014-03-19 10:00 ` Roman Neuhauser
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=20140319172213.GE53100@isis.sigpipe.cz \
--to=neuhauser@sigpipe.cz \
--cc=rayandrews@eastlink.ca \
--cc=zsh-users@zsh.org \
/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).