From: Andrew Main <zefram@tao.co.uk>
To: sweth@astaroth.nit.gwu.edu (Sweth Chandramouli)
Cc: zsh-users@math.gatech.edu
Subject: Re: zsh lists being used for spam-gathering?
Date: Fri, 12 Dec 1997 19:19:22 +0000 (GMT) [thread overview]
Message-ID: <199712121919.TAA21800@taos.demon.co.uk> (raw)
In-Reply-To: <19971212134934.13866@astaroth.nit.gwu.edu> from "Sweth Chandramouli" at Dec 12, 97 01:49:34 pm
Sweth Chandramouli wrote:
> i've been playing recently with the parameter expansion features of ls
ls doesn't do any parameter expansion.
>in zsh, and have been totally blown away by them. as far as i can tell, they do
>almost everything that find can do
I suppose you must be talking about zsh globbing?
>using them (in backquotes) as the input for a for-do loop),
I'm not sure precisely what you mean here, but if you're doing something
like
for f in `ls *(wibble)`
then you should change it to
for f in *(wibble)
which saves a process, and a pipe, and will handle special characters
properly.
>the faster execution of the ls verison be offset by the time to load zsh if i
>were to make all of my ksh scriptfiles into zsh verisons instead?
Not if you link zsh statically and set its sticky bit.
Really, with demand-loading, particularly if you use zsh's module feature
(3.1+), there shouldn't be a great deal of difference. I suggest you
experiment.
-zefram
next prev parent reply other threads:[~1997-12-12 19:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-12 17:42 Timothy Luoma
1997-12-12 18:20 ` Bruce Stephens
1997-12-12 18:49 ` Sweth Chandramouli
1997-12-12 19:19 ` Andrew Main [this message]
1997-12-12 20:20 ` Mirar
1997-12-12 20:26 ` Andrew Main
1997-12-12 20:31 ` Mirar
1997-12-12 20:59 ` Andrew Main
1997-12-12 21:06 ` Mirar
1997-12-14 23:03 ` completion hacking Mirar
1997-12-15 11:18 ` Andrew Main
1997-12-15 10:06 ` zsh lists being used for spam-gathering? Bruce Stephens
1997-12-12 21:42 ` Richard Coleman
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=199712121919.TAA21800@taos.demon.co.uk \
--to=zefram@tao.co.uk \
--cc=sweth@astaroth.nit.gwu.edu \
--cc=zsh-users@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).