Path: utzoo!utgpu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!julius.cs.uiuc.edu!psuvax1!ukma!usenet.ins.cwru.edu!odin!chet From: chet@odin.INS.CWRU.Edu (Chet Ramey) Newsgroups: alt.sources.d Subject: Re: Multiple executables in path (Was: NON-SOURCE POSTINGS CONSIDERED HARMFUL!) Message-ID: <1991Jan22.220246.9920@usenet.ins.cwru.edu> Date: 22 Jan 91 22:02:46 GMT References: <1991Jan22.053747.14144@convex.com> <5570@idunno.Princeton.EDU> Sender: news@usenet.ins.cwru.edu Reply-To: chet@po.CWRU.Edu Organization: Case Western Reserve Univ. Cleveland, Ohio, (USA) Lines: 28 Nntp-Posting-Host: odin.ins.cwru.edu In article <5570@idunno.Princeton.EDU> pfalstad@phoenix.Princeton.EDU (Paul Falstad) writes: >tchrist@convex.COM (Tom Christiansen) wrote: >>From the keyboard of kaul@icarus.eng.ohio-state.edu (Rich Kaul): >>:with bash, where you can have a PATH with unexpanded ~ references in >>That's odd -- if you have unexpanded tildes in your environment, >>I wonder how you get system, popen, and execlp to work without >>changing the C library. > >You don't, it seems. At least it didn't work for me. This is probably >a bug in bash. You should use $HOME instead of ~ when you define >your PATH. It's not a bug in bash. It's bash doing something useful with what would otherwise be useless. You have to go through special pains to get an unexpanded tilde in your PATH, since tilde expansion is performed on the rhs of assignment statements. The only way you can get a tilde into your path is to surround it with quotes. It might be a bug that double quotes can inhibit the expansion. Chet -- Chet Ramey ``There's just no surf in Network Services Group Cleveland, U.S.A. ...'' Case Western Reserve University chet@ins.CWRU.Edu My opinions are just those, and mine alone.