From owner-freebsd-current Mon Oct 19 10:20:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA25899 for freebsd-current-outgoing; Mon, 19 Oct 1998 10:20:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dt053nb4.san.rr.com (dt053nb4.san.rr.com [204.210.34.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA25887 for ; Mon, 19 Oct 1998 10:20:20 -0700 (PDT) (envelope-from Studded@gorean.org) Received: from gorean.org (Studded@localhost [127.0.0.1]) by dt053nb4.san.rr.com (8.8.8/8.8.8) with ESMTP id KAA19351; Mon, 19 Oct 1998 10:19:51 -0700 (PDT) (envelope-from Studded@gorean.org) Message-ID: <362B74B6.B9B256B4@gorean.org> Date: Mon, 19 Oct 1998 10:19:50 -0700 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 2.2.7-STABLE-1015 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?=" CC: current@FreeBSD.ORG Subject: Re: sh and ~ expansion References: Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Dag-Erling C. Smørgrav" wrote: > > Why doesn't ~ expansion work in the following case: > > export GLORB=~ > > as it does in > > GLORB=~; export GLORB I've seen a couple of people complain about 'export foo=bar' causing problems in our implementation of sh. I haven't looked at why it's a problem but if it's any comfort, yes, it seems to be a bug. I've gotten into the habit of using 'foo=bar; export foo' when using sh anyway since it's more portable. Doug -- *** Chief Operations Officer, DALnet IRC network *** Go PADRES! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message