Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!rpi!ispd-newsserver!garden.ssd.kodak.com!weimer
From: weimer@garden.ssd.kodak.com (Gary Weimer (253-7796))
Newsgroups: comp.unix.questions
Subject: Re: Apostrophe woes
Message-ID: <1991Jun17.141944.272@ssd.kodak.com>
Date: 17 Jun 91 14:19:44 GMT
References: <16829@leadsv.UUCP>
Sender: news@ssd.kodak.com
Reply-To: weimer@ssd.kodak.com
Organization: Eastman Kodak Co.; Rochester, NY
Lines: 28


In article <16829@leadsv.UUCP>, schip@sgi400.msd.lmsc.lockheed.com (Jan
Schipmolder) writes:
|> I don't know why your system is giving you problems. But, on my
|> system, the following two commands have the same identical effect:
|> 
|> echo `date`
|> date
|> 
|> Since they both have the same effect, why insist on using one and not the
|> other?

Unfortunately:

    date;echo ":ERROR routine error"
and
    echo `date`":ERROR routine error"

do not have the same affect. Fortunately, Unix always has more that one
way to do things. So we can do the following:

    (date;echo ":ERROR routine error")|awk '{str=str $0}END{print str}' -

NOTE: if you must flame this because you're humor impared and you think
it's a serious post, at least substitute awk with something with a shorter
start-up time before flaming...

weimer@ssd.kodak.com ( Gary Weimer )