Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!apple!snorkelwacker.mit.edu!paperboy!meissner From: meissner@osf.org (Michael Meissner) Newsgroups: comp.lang.perl Subject: Re: '~' in file names Message-ID: Date: 1 Mar 91 23:32:19 GMT References: <1991Feb28.151019.22944@uvaarpa.Virginia.EDU> <30953@shamash.cdc.com> <1991Mar1.000018.15048@frey.newcastle.edu.au> Sender: news@OSF.ORG Organization: Open Software Foundation Lines: 21 In-reply-to: alan@frey.newcastle.edu.au's message of 1 Mar 91 00:00:18 GMT In article <1991Mar1.000018.15048@frey.newcastle.edu.au> alan@frey.newcastle.edu.au (Alan Hargreaves) writes: | rrr@u02.svl.cdc.com (Rich Ragan) writes: | | >Agreed, the shell does this and it is very useful. Because we | >sometimes move users from one file system to another to balance | >disk usage, we strongly encourage users to employ ~ to avoid | >having to change absolute paths if they get moved. I have been | | so why not get them to use $HOME? For starters there are a few Standard | shells around that don't map ~ to $HOME. $HOME is much safer. But ~otheruser/foo does not work. I don't think it's unreasonable that perl do the ~ translation for all names in file contexts..... (as long as it's all places filenames are handled). -- Michael Meissner email: meissner@osf.org phone: 617-621-8861 Open Software Foundation, 11 Cambridge Center, Cambridge, MA, 02142 Considering the flames and intolerance, shouldn't USENET be spelled ABUSENET?