Date: Fri, 21 Jan 2000 00:17:56 +0000 From: Ben Smithurst <ben@scientia.demon.co.uk> To: cjclark@home.com Cc: freebsd-questions@FreeBSD.ORG Subject: Re: sh(1) Messing with My Mind Message-ID: <20000121001756.A25494@strontium.scientia.demon.co.uk> In-Reply-To: <20000120175518.F72914@cc942873-a.ewndsr1.nj.home.com> References: <867h6j$1kk4$1@atlantis.rz.tu-clausthal.de> <200001202140.WAA05161@dorifer.heim3.tu-clausthal.de> <20000120175518.F72914@cc942873-a.ewndsr1.nj.home.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Crist J. Clark wrote:
> And although it does not impact me, there is another reason, and one
> of the best ones, that someone would rather pipe to read than
> backtick,
>
> (3) The backticked argument cannot have nested backticks.
ben@strontium:~$ echo `ls \`pwd\``
.ICEauthority .KillLog .MsgLog .Xauthority .Xresources [snip]
oh yes it can. :-) Of course, the $() form would be clearer, i.e. echo
$(ls $(pwd)), especially with more than one level of nesting (which I've
never even attempted).
> Anyway, I guess I need to find a workaround. I figured I was missing
> something obvious (something I already knew). Thanks for pointing it
> out.
hmm.. if the output is like "4 Fri 21 Jan 2000 00:15:59 GMT" as you say,
then how about
DATA=`awk whatever`
set -- $DATA
NUM=$1
shift; DATE="$*"
would that work?
--
Ben Smithurst | PGP: 0x99392F7D
ben@scientia.demon.co.uk | key available from keyservers and
| ben+pgp@scientia.demon.co.uk
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000121001756.A25494>