Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!ub!uhura.cc.rochester.edu!rochester!kodak!uupsi!sunic!kuling!cia.docs.uu.se!bqt
From: bqt@cia.docs.uu.se (Johnny Billquist)
Newsgroups: comp.sys.handhelds
Subject: Re: specifying paths w/variables & progs
Keywords: path, hp48sx
Message-ID: <bqt.672615256@cia.docs.uu.se>
Date: 25 Apr 91 21:34:16 GMT
References: <231b3618.670790994@fergvax> <1523@tau.sm.luth.se> <1617@fs1.ee.ubc.ca>
Sender: news@kuling.UUCP
Distribution: comp.sys.handhelds
Lines: 44

In <1617@fs1.ee.ubc.ca> jthornto@ee.ubc.ca (Johan Thornton) writes:

>In article <1523@tau.sm.luth.se> d89-mlt@sm.luth.se (Morgan Lindqvist) writes:
[stuff deleted...]
>This is not a bad idea.  Not much overhead at all.  But note that you
>don't have to explicitly say HOME when switching to the BINP directory.
>Since that subdirectory is in HOME, it's always in the path.

>Likewise for 2), above -- to go to the BINP subdir just execute BINP.

Not neccesaryily true!

Suppode your directory structure looks like this:

HOME
 |
FOO
 |
FOO
 |
BAR

and you are currently in {HOME FOO FOO BAR}

{FOO} EVAL
and
{HOME FOO} EVAL
does not give the same result.

Not to mention if you have a variable in the current directory with
the same name as the directory you want to switch to.
There are some more possible ways to foul up, so keep sticking to
{HOME ... } when you want to specify a directory.

======================================================================
Everybody know that the DECstation	- I'm on a bus
is a pdp8, which is a RISC, but		- on a psychodelic trip,
where did MIPS computers get into it?	- reading murder books
					- and tryin' to stay hip.

	- Johnny Billquist		- Billy Idol

D89.JOHNNY-BILLQUIST@AIDA.CSD.UU.SE
======================================================================