zsh-users
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@brasslantern.com>
To: r.hooft@euromail.net (Rob Hooft), zsh-users@sunsite.auc.dk
Subject: Re: Parameter expansion
Date: Wed, 31 Mar 1999 23:33:10 -0800	[thread overview]
Message-ID: <990331233310.ZM27967@candle.brasslantern.com> (raw)
In-Reply-To: <14083.4141.374266.213229@octopus.chem.uu.nl>

On Apr 1,  8:20am, Rob Hooft wrote:
} Subject: Re: Parameter expansion
}
} I understand this is a zsh mailinglist, but I find the shell-independent
} 
}   xargs zip backup.zip < index.txt
} 
} more readable, and it gracefully handles the case where index.txt is too
} long for the command line....

Zsh can handle VERY long command lines ... much longer than required to
hold the number of arguments xargs will pass to a single command by
default.  Does

	zip backup.zip file1 file2 ... fileN
	zip backup.zip fileN+1 fileN+2 ... file2N

really do the right thing?  Because that's roughly what'll get executed
if there are enough lines in index.txt.  Even if zip does the right thing
in that case, "xargs tar zcf backup.tar" is a recipe for disaster.

Finally, the whole point of the question was that index.txt contains
file _patterns_, not file names; xargs, by design, won't expand file
patterns, so your solution would fail completely.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com


  parent reply	other threads:[~1999-04-01 22:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-31 14:35 Mircea Damian
1999-03-31 14:54 ` Geoff Wing
1999-03-31 15:04   ` Mircea Damian
1999-03-31 15:51     ` Bart Schaefer
1999-04-01  6:20       ` Rob Hooft
1999-04-01  7:30         ` Geoff Wing
1999-04-01  7:33         ` Bart Schaefer [this message]
1999-05-17  9:39 Roland Jesse
1999-05-17  9:23 ` Peter Stephenson
2017-08-13 22:58 Parameter Expansion Clint Priest
2017-08-13 23:51 ` Bart Schaefer
2017-08-14  0:07   ` Bart Schaefer
2017-08-14  1:16     ` Clint Priest

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=990331233310.ZM27967@candle.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=r.hooft@euromail.net \
    --cc=zsh-users@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).