Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!lavaca.uh.edu!menudo.uh.edu!sugar!peter From: peter@sugar.hackercorp.com (Peter da Silva) Newsgroups: comp.sys.amiga.tech Subject: Re: PIPES Message-ID: <7238@sugar.hackercorp.com> Date: 9 Dec 90 14:10:23 GMT References: <18788@ultima.socs.uts.edu.au> <7218@sugar.hackercorp.com> <1990Dec9.090708.20063@agate.berkeley.edu> Reply-To: peter@sugar.hackercorp.com (Peter da Silva) Organization: Sugar Land Unix - Houston Lines: 22 In article <1990Dec9.090708.20063@agate.berkeley.edu> pete@violet.berkeley.edu (Pete Goodeve) writes: > > I think it would be still better to have BOTH, I disagree: > so that you can let the user set his favourite once and forget it, Put it in his shell RC file, and then all his interactive shells will have it. That's effectively "global", without breaking scripts: > and still allow scripts their own special preference if they need it. No, batch scripts need to have a standard environment, particularly for things like metacharacters. If you have a global PIPECHAR variable, it needs to be ignored when not in interactive mode. (This is the MOST hosed feature of the C shell on UNIX, that scripts have to deal with whatever wacko stuff a user puts in their .cshrc) -- Peter da Silva. `-_-' .