From: Aaron Davies <agdavi01@louisville.edu>
To: zsh-users@sunsite.dk
Subject: Re: Slightly OT: Error-Handling in a Pipeline, preferably non-zsh
Date: Mon, 16 Aug 2004 08:40:17 -0400 [thread overview]
Message-ID: <6D7144FA-EF81-11D8-83BE-000502631FBD@louisville.edu> (raw)
In-Reply-To: <Pine.LNX.4.61.0408160032060.21654@toltec.zanshin.com>
On Monday, August 16, 2004, at 03:41 AM, Bart Schaefer wrote:
> On Sun, 15 Aug 2004, Aaron Davies wrote:
>
>>> As a final note, you probably want "$@" in double quotes.
>>
>> Really? I used it with multi-word commands (like "kill -9") with no
>> problems.
>
> What happens when one of the arguments of the command is a quoted word
> containing spaces? E.g. supposing your "generalized killall" is named
> "runcommandonpidof" (since you've never told us what it _is_ called),
> try
It's called "toall".
> sleep 30 &
> runcommandonpidof sleep print -l "this should be on one line"
>
> (and try it in a non-zsh shell, where word splitting applies; no
> cheating by letting zsh preserve the quoting for you, you asked for
> portability).
What is "print"? There doesn't seem to be an executable of that name on
my (OS X 10.3) box, and printf doesn't have a "-l" option. I tried
something similar with echo, and saw no difference.
toall sleep echo "this is one line"
produces
this is one line 19980
whether or not $@ is in quotes. (I was invoking the script from sh,
which I think on this box is actually bash running in sh-mode.)
--
__ __
/ ) / )
/--/ __. .__ ______ / / __. , __o _ _
/ (_(_/|_/ (_(_) / (_ (__/_(_/|_\/ <__</_/_)_
next prev parent reply other threads:[~2004-08-16 12:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-16 1:04 Aaron Davies
2004-08-16 2:42 ` Bart Schaefer
2004-08-16 3:33 ` Aaron Davies
2004-08-16 7:41 ` Bart Schaefer
2004-08-16 12:40 ` Aaron Davies [this message]
2004-08-16 14:53 ` DervishD
2004-08-17 3:06 ` Bart Schaefer
2004-08-16 3:03 ` Philippe Troin
2004-08-16 3:30 ` Aaron Davies
2004-08-16 7:51 ` Bart Schaefer
2004-08-16 12:41 ` Aaron Davies
2004-08-16 16:08 ` Dan Nelson
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=6D7144FA-EF81-11D8-83BE-000502631FBD@louisville.edu \
--to=agdavi01@louisville.edu \
--cc=zsh-users@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).