public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: Igor Peshansky <pechtcha@cs.nyu.edu>
To: The Cygwin-Talk Maiming List <cygwin-talk@cygwin.com>
Subject: Re: bash scripting nightmare.
Date: Thu, 10 Aug 2006 20:58:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.63.0608101657390.19545@access1.cims.nyu.edu> (raw)
In-Reply-To: <ebg5b6$5f2$1@sea.gmane.org>

On Thu, 10 Aug 2006, mwoehlke wrote:

> Dave Korn wrote:
> > On 10 August 2006 20:49, mwoehlke wrote:
> >
> > > > [snip examples]
> > > It sounds like you want to read up on arrays and "$@" (quotes
> > > included).
> >
> > > Does that help?
> >
> >   I haven't had time to try it yet, but yes, I'm sure that'll do the
> > trick. Thanks a bundle for the hints!
>
> Glad to help!
>
> (If you don't need the arrays, you can still be portable, too; I'm
> fairly sure "$@" is required by POSIX which means even most of the
> cruddy shells should support it. At any rate, I know *we* use it in
> portable scripts, and we run into a lot of cruddy shells :-).)

I was also initially thinking "arrays", but supposing that you *do* need
to embed everything in one parameter, the eval builtin is your friend.
HTH,
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_	    pechtcha@cs.nyu.edu | igor@watson.ibm.com
ZZZzz /,`.-'`'    -.  ;-;;,_		Igor Peshansky, Ph.D. (name changed!)
     |,4-  ) )-,_. ,\ (  `'-'		old name: Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"

  reply	other threads:[~2006-08-10 20:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-10 17:54 Dave Korn
2006-08-10 19:49 ` mwoehlke
2006-08-10 20:25   ` Dave Korn
2006-08-10 20:40     ` mwoehlke
2006-08-10 20:58       ` Igor Peshansky [this message]
2006-08-10 23:10 ` Scripting fun! :-) (was Re: bash scripting nightmare. ( ) Linda A. Walsh

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=Pine.GSO.4.63.0608101657390.19545@access1.cims.nyu.edu \
    --to=pechtcha@cs.nyu.edu \
    --cc=cygwin-talk@cygwin.com \
    /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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).