From: "Thomas Köhler" <jean-luc@picard.franken.de>
To: zsh-users@sunsite.auc.dk
Cc: zsh-workers@sunsite.auc.dk
Subject: Re: rm -r
Date: Wed, 22 Dec 1999 10:58:57 +0100 [thread overview]
Message-ID: <19991222105856.A2667@picard.franken.de> (raw)
In-Reply-To: <m2vh5s5doy.fsf@toy.mandrakesoft.com>; from francis@mandrakesoft.com on Tue, Dec 21, 1999 at 07:52:29PM +0100
On Tue, Dec 21, 1999 at 07:52:29PM +0100,
fg <francis@mandrakesoft.com> wrote:
>
> Andre Pang <andrep-ml@vjolnir.org> writes:
>
> >
> > rm -f **/*.o(^/) will work if you've doing 'setopt EXTENDED_GLOB', too.
> > (That'll remove all files which end in .o recursively, and exclude all *.o
> > files which are directories).
> >
>
> Gee, this makes me look at "find" like an easy-to-use program ;)
I'd say
ls **/*(.)
is much easier than
find . -type f -exec ls {} \;
You just need a little bit of experience with zsh's extended globbing.
(I hardly use find any more)
YMMV :)
> BTW, whats the argument limit for zsh?
jean-luc@picard (tty11) ~> /bin/echo $(repeat 32766 echo -n "x " )
[lots of "x x x x "]
jean-luc@picard (tty11) ~> /bin/echo $(repeat 32767 echo -n "x " )
zsh: argument list too long: /bin/echo
Ah, the limit is at 32766 arguments. (On Linux-i386)
Here's the few situations where I need find again... :)
Question to zsh-workers (Cc-ed):
Is there a special reason why only 32766 arguments are allowed? (that
is, 32766+1, the executable name, so - an unsigned short seems to be
used for counting the arguments - why not an int? Would be 2147483646
arguments on Linux)
(I currently don't read zsh-workers, so please Cc me or zsh-users if you
reply to this question. thanks)
CU,
Thomas
--
Thomas Köhler Email: jean-luc@picard.franken.de | LCARS - Linux for
<>< WWW: http://home.pages.de/~jeanluc/ | Computers on All
IRC: jeanluc | Real Starships
PGP public key: http://www.mayn.de/users/jean-luc/PGP-Public.asc
next prev parent reply other threads:[~1999-12-22 10:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-20 15:31 Claus Alboege
1999-12-20 15:41 ` Vincent Lefevre
1999-12-20 15:43 ` Clint Adams
1999-12-20 16:13 ` Pascal Byrne
1999-12-20 16:28 ` fg
1999-12-21 14:31 ` Andre Pang
1999-12-21 18:52 ` fg
1999-12-22 3:51 ` Andre Pang
1999-12-22 9:58 ` Thomas Köhler [this message]
1999-12-22 13:12 ` Alexandre Duret-Lutz
1999-12-22 13:24 ` Thomas Köhler
1999-12-23 0:15 ` Geoff Wing
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=19991222105856.A2667@picard.franken.de \
--to=jean-luc@picard.franken.de \
--cc=zsh-users@sunsite.auc.dk \
--cc=zsh-workers@sunsite.auc.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).