From: Stephane Chazelas <stephane.chazelas@gmail.com>
To: Peter Stephenson <p.w.stephenson@ntlworld.com>
Cc: "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: Problems with zargs (Was: xargs should be a builtin)
Date: Thu, 12 Apr 2012 10:28:22 +0100 [thread overview]
Message-ID: <20120412092822.GA13041@chaz.gmail.com> (raw)
In-Reply-To: <20120411171539.4a09da6a@pws-pc.ntlworld.com>
2012-04-11 17:15:39 +0100, Peter Stephenson:
> On Wed, 11 Apr 2012 11:06:42 +0100
> Stephane Chazelas <stephane.chazelas@gmail.com> wrote:
> > By the way, there seems to be some issues with zargs:
> >
> > ~$ zargs a b '' -- print -rl
> > a
> > b
> > ~$ zargs a -- print -rl ''
> > a
> > ~$ zargs -e a '' print -rl
> > a print -rl
> > ~$ zargs --eof= a '' print -rl
> > a
>
> It helps if everyone always says explicitly what the problem actually
> is, it saves lots of guesswork.
Sorry about that. Wrote in a rush.
> I've come up with the following for the problems I understand, but I'm
> sure it could do with a bit more prodding.
[...]
Thanks. That seems to do the trick.
May I knitpick:
~$ ''() echo X "$@"
~$ zargs 1 2 -- ''
1 2
~$ zargs 1 2 -- '' ''
X 1 2
--- zargs.old 2012-04-12 10:26:20.658633028 +0100
+++ /usr/share/zsh/functions/Misc/zargs 2012-04-12 10:27:20.709077765 +0100
@@ -174,7 +174,7 @@
else set -- "${(@)argv[1,end-1]}"
fi
-if [[ -n $command ]]
+if (($#command))
then (( c = $#command - 1 ))
else command=( print -r -- )
fi
--
Stephane
next prev parent reply other threads:[~2012-04-12 9:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 7:31 xargs should be a builtin Dave Yost
2012-04-11 7:44 ` Frank Terbeck
2012-04-11 10:06 ` Problems with zargs (Was: xargs should be a builtin) Stephane Chazelas
2012-04-11 16:15 ` Peter Stephenson
2012-04-12 9:28 ` Stephane Chazelas [this message]
2012-04-12 19:33 ` Peter Stephenson
[not found] ` <CAH+w=7Z5pUmqxpURyHMA5FX3hMGoyQeYwbC1N7AO6Ow-D=P-gw@mail.gmail.com>
[not found] ` <20120413201325.64cfcd1f@pws-pc.ntlworld.com>
2012-04-14 17:01 ` Bart Schaefer
2012-04-12 23:05 ` Bart 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=20120412092822.GA13041@chaz.gmail.com \
--to=stephane.chazelas@gmail.com \
--cc=p.w.stephenson@ntlworld.com \
--cc=zsh-workers@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).