home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!mcsun!Germany.EU.net!math.fu-berlin.de!Sirius.dfn.de!darwin.sura.net!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!ames!pacbell.com!charon.amdahl.com!amdahl!veritas!amdcad!weitek!pyramid!ctnews!risky!israel
- From: israel@risky.Convergent.COM (Paul Israel)
- Newsgroups: comp.unix.aux
- Subject: Re: csh is screwed up
- Message-ID: <10932@risky.Convergent.COM>
- Date: 28 Aug 92 16:31:23 GMT
- References: <1992Aug27.171503.794@colorado.edu>
- Organization: Unisys Unix Systems Group, San Jose, CA
- Lines: 24
-
- From article <1992Aug27.171503.794@colorado.edu>, by powellb@samwise.colorado.edu (Brian Powell):
- >
- > Does anyone know why the csh included with A/UX 3.0 is so screwed up?
- > This simple example here does not work under the A/UX csh; however, it works on
- > Sun, DEC, HP, IBM, and SGI. Here it is:
- >
- > #!/bin/csh
- > set test = `pwd`
- > echo $test
- > exit
- >
- > This program will not echo anything because the scripting with csh will
- > not execute the program pwd as it is supposed to. Does anyone know a work
- > around to this (beside tcsh)? I can't use tcsh for the application I am
- > applying this to.
-
- Say, you don't have your pwd command aliased to anything in your
- .cshrc file, do you? That sometimes causes problems with `` notation
- when you run it from a command line, although I'm not sure what would
- happen from inside a shell script. Good luck!
- --
- Paul Israel ----------------- israel@risky.convergent.com
- Senior Smartypants ----------- Unisys Corporation, San Jose, California
- Disclaimer: "Who, me? I wasn't even there!"
-