Path: utzoo!mnetor!uunet!husc6!think!rlk From: rlk@think.COM (Robert Krawitz) Newsgroups: comp.unix.wizards Subject: Re: PS1 and PWD in david korn's shell Message-ID: <13716@think.UUCP> Date: 15 Dec 87 14:57:37 GMT Sender: usenet@think.UUCP Reply-To: rlk@THINK.COM Distribution: na Organization: Thinking Machines Corporation, Cambridge, MA Lines: 25 In article <3@dropte.foobar.UUCP> tw@dropte.UUCP (Tom Walsh) writes: ]In article <7@ritcv.UUCP> ccs6277@ritcv.UUCP (PUT YOUR NAME HERE) writes: ]$PWD is maintained by korn shell. use it. it is cheaper than ]`pwd`... by a long shot. This brings me to a major complaint about the Korn shell. First of all, when setting my prompt in csh, I use `pwd` rather than $cwd, because $cwd is NOT the current working directory in many cases (symlinks most usually). Thus, I don't really know where I am. I want to know where I really am. Thus, if cd /usr actually takes me to /usr.MC68020, I want to know that. Of course, doing a cd .. from some fake path is going to lose big. Now, my complaint: ksh interprets pwd and cd .. itself. The former I can live with; I need merely use /bin/pwd. The latter I cannot live with. I won't go into the merits of varying interpretations of symlinks, since that issue was recently flamed to death; suffice it to say that I prefer a link to be a link, and a symlink to be a one-way pointer. I also could not find a way around this in the man page. I now ask: How can I turn this behavior off? harvard >>>>>> | bloom-beacon > |think!rlk Robert Krawitzihnp4 >>>>>>>> .