From: Mike Castle <dalgoda@ix.netcom.com>
To: Jeffrey Holle <jeff.holle@verizon.net>
Cc: linux-console@vger.kernel.org
Subject: Re: feeding a script from standard input
Date: Wed, 28 Jan 2004 23:30:16 -0800 [thread overview]
Message-ID: <20040129073016.GA370@thune.mrc-home.com> (raw)
In-Reply-To: <bv96ha$88v$1@sea.gmane.org>
On Wed, Jan 28, 2004 at 12:34:17PM -0800, Jeffrey Holle wrote:
> Thanks for this, works without the quotes!
Better to use "$@".
Otherwise if you do something like *.foo and any of those names has spaces
in it, it would fail. Only "$@" will get that case right.
Even the people who designed that feature call it magic.
mrc
--
Mike Castle dalgoda@ix.netcom.com www.netcom.com/~dalgoda/
We are all of us living in the shadow of Manhattan. -- Watchmen
fatal ("You are in a maze of twisty compiler features, all different"); -- gcc
next prev parent reply other threads:[~2004-01-29 7:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-27 6:04 feeding a script from standard input Jeffrey Holle
2004-01-28 14:05 ` Jan-Benedict Glaw
2004-01-28 20:34 ` Jeffrey Holle
2004-01-29 7:30 ` Mike Castle [this message]
2004-01-30 15:30 ` Jan-Benedict Glaw
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=20040129073016.GA370@thune.mrc-home.com \
--to=dalgoda@ix.netcom.com \
--cc=jeff.holle@verizon.net \
--cc=linux-console@vger.kernel.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.
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).