From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-user <zsh-users@zsh.org>
Subject: Re: question about zargs
Date: Wed, 31 Oct 2012 09:30:17 -0700 [thread overview]
Message-ID: <121031093018.ZM11752@torch.brasslantern.com> (raw)
In-Reply-To: <20121031142546.529e1709@pwslap01u.europe.root.pri>
Preface for Han Pingtian: If the command you're going to run is external
to the shell, then I recommend you use xargs. However, in some cases it
may be desirable to get xargs-like behavior when passing arguments to a
shell function or builtin, which is why there is zargs.
On Oct 31, 2:25pm, Peter Stephenson wrote:
} Subject: Re: question about zargs
}
} Hmm... in principle, you can do:
}
} zargs -n2 **/* -- ls
}
} so that it executes ls and one additional argument each time. This is
} equivalent to the -n1 you gave to xargs.
Well, yes and no. zargs -n2 is not "equivalent to" xargs -n1 in the
general case. In the previous thread about this, it was pointed out that
zargs -n2 **/* -- ls -l
is equivalent to
zlargs -l1 **/* -- ls -l
But the only reason you need -n2 is because of the "-l" that is already
trailing the "ls" command. If there are no trailing arguments (that is,
the command is a name only) then -n1 and -l1 are equivalent.
} However, with a lot of iles this is running incredibly slowly for me and
} after a few dozen files have been processed I hit:
}
} 279: mem.c:1180: MEM: allocation error at sbrk, size 589824.
} zargs:279: fatal error: out of memory
Hmm, "a few dozen" isn't nearly enough to trigger this for me, though if
I run it on a sufficiently large set of files I can watch the memory
usage of the shell grow steadily throughout.
And yes, it can be slow.
If I try
zlargs -l1 **/* -- print > /dev/null
the memory use jumps much faster, probably because no forking is involved.
--
Barton E. Schaefer
next prev parent reply other threads:[~2012-10-31 16:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 13:40 Han Pingtian
2012-10-31 14:25 ` Peter Stephenson
2012-10-31 16:30 ` Bart Schaefer [this message]
2012-10-31 22:32 ` Han Pingtian
2012-11-01 0:10 ` delete key :( Ray Andrews
2012-11-01 12:54 ` Peter Stephenson
2012-11-01 15:21 ` Ray Andrews
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=121031093018.ZM11752@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--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).