From: Geoff Wing <mason@werple.net.au>
To: zsh-workers@math.gatech.edu (zsh-list)
Subject: Re: zsh arg list too long
Date: Tue, 13 Feb 1996 18:32:06 +1100 (EST) [thread overview]
Message-ID: <199602130732.SAA23081@werple.net.au> (raw)
In-Reply-To: <199602121217.NAA09795@jagor.srce.hr> from "Hrvoje Niksic" at Feb 12, 96 01:17:20 pm
jarausch@igpm.rwth-aachen.de (Helmut Jarausch) wrote:
:Sorry, I could find it in the FAQs althoug it should be a common problem.
:On my machine (SGI,IRIX6.1) I often get the error "zsh arg list too long".
:Last time I only tried rm ~/.netscape-cache/*
:and it failed because there were (only) 576 files (filename length 24)
:Is this a general restrictions of my OS or is ZSH configurable to allow
:longer parameter lists?
Hrvoje.Niksic@public.srce.hr (Hrvoje Niksic) replied:
:I noticed it too. It should not be OS restriction, since it works in other
:shells. I am afraid it is a zsh bug.
The limitation is imposed by the OS. You can usually find it in
/usr/include/sys/syslimits.h as something like ARG_MAX (256Kb on my machine)
According to POSIX: "The number of bytes available for the combined
argument list and environment list is given by ARG_MAX macro in <limits.h>"
Look through the /usr/include/**/*limit* files or try something like:
% fgrep ARG_ /usr/include/**/*.h
Zoltan mentioned that the builtin echo wasn't limited thus, so maybe you
could do
% echo ~/.netscape-cache/* | xargs rm
or maybe this will work if there aren't too many
% (cd ~/.netscape-cache; echo *)
--
Mason [G.C.W] mason@werple.mira.net.au "Hurt...Agony...Pain...LOVE-IT"
prev parent reply other threads:[~1996-02-13 8:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-02-09 9:26 Helmut Jarausch
1996-02-12 12:17 ` Hrvoje Niksic
1996-02-12 12:49 ` Zoltan Hidvegi
1996-02-13 7:32 ` Geoff Wing [this message]
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=199602130732.SAA23081@werple.net.au \
--to=mason@werple.net.au \
--cc=zsh-workers@math.gatech.edu \
/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).