Subject: sh backtick deficiency?
To: None <current-users@NetBSD.ORG>
From: Hubert Feyrer <firstname.lastname@example.org>
Date: 03/30/1998 10:37:15
What's the exact semantics on backtick expansion in /bin/sh? Up to a few
minutes ago, i was under the impression that whatever the command in the
backticks outputs is handed as _one_ argument, just as enclosed in double
Now our /bin/sh seems to pass every word as a single argument:
$ cat /tmp/cm
Network sniffer, via FreeBSD PR ports/6160.
$ cvs add -m `cat /tmp/cm` sniffit
cvs [add aborted]: no such directory `ports'
So, is it just me, or is it our shell? If the latter, tell me and I'll
Hubert Feyrer <email@example.com>