From: Igor Peshansky <pechtcha@cs.nyu.edu>
To: The Cygwin-Talk Maiming List <cygwin-talk@cygwin.com>
Subject: RE: Scripting fun! :-) (was Re: bash scripting nightmare. ( )
Date: Fri, 11 Aug 2006 15:14:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.63.0608111113120.23078@access1.cims.nyu.edu> (raw)
In-Reply-To: <004c01c6bce4$3b479470$a501a8c0@CAM.ARTIMI.COM>
On Fri, 11 Aug 2006, Dave Korn wrote:
> On 11 August 2006 00:12, Linda Walsh wrote:
>
> > Dave Korn wrote:
> >
> >> Hey all, who's any good at bash scripting?
> >>
> > ---
> > You are doing correctly, mostly. The simplest way to get from
> > where you are, to where you want to be, is, well think of this:
> > You have created a "command line" all stuffed into 1 variable, right?
> > Ala: VAR="cvs co -D \"2006-08-10 15:00:00\" -P pci wimedia"
> > The value of VAR (putting everything between two vertical bars) is:
> > |cvs co -D "2006-08-10 15:00:00" -P pci wimedia|
> > You have a "literal" expression in "VAR", meaning the quotes are stored
> > as literals and have no special meaning. If you just try to use "execute"
> > the literal, the arguments are passed in literally.
> >
> > What you want is for the quotes to regain their special meaning, which
> > you can do by telling the shell to run it's "eval"uator over the expression
> > again before executing, as in "eval $VAR". In line 9 of your code below,
> > just add an "eval" before the argument.
>
> Thankyou thankyou thank you THANK YOU!
>
> That made it all seem so clear. I could see that the quote mark was
> getting attached to the first word and not keeping the two words as one
> arg, but I didn't know what it means or what to do with it. Eval'ing it
> worked perfectly, just like you said. Thanks for saving my sanity!
Not to sound defensive, but did you happen to see
<http://cygwin.com/ml/cygwin-talk/2006-q3/msg00138.html> from yesterday?
Just curious...
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"
next prev parent reply other threads:[~2006-08-11 15:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-10 23:12 Linda Walsh
2006-08-11 1:19 ` Dave Korn
2006-08-11 15:14 ` Igor Peshansky [this message]
2006-08-11 15:41 ` Dave Korn
-- strict thread matches above, loose matches on Subject: below --
2006-08-10 17:54 bash scripting nightmare Dave Korn
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.0608111113120.23078@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).