Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!jarthur!sburke
From: sburke@jarthur.Claremont.EDU (Scott Burke)
Newsgroups: comp.sys.handhelds
Subject: Re: specifying paths w/variables & progs
Message-ID: <11547@jarthur.Claremont.EDU>
Date: 4 Apr 91 20:47:58 GMT
References: <231b3618.670790994@fergvax> <1991Apr4.200847.12538@usenet.ins.cwru.edu>
Organization: Harvey Mudd College, Claremont, CA 91711
Lines: 28


Way back when there was a lot of talk about setting up a Work directory, so
that all the miscellaneous useful utilities could be left in the HOME
directory.  Others have gone to libraries, so that their utilities were
available anywhere.  Here's a simple alternative, which was touched upon in
the original post to which I am responding:

Put this program in HOME:

EXEC
\<<
  PATH \-> path
  \<<
    HOME EVAL path EVAL
  \>>
\>>

Then, make CST do all the work by storing softkey definitions such as:

{ "SEE" \<< { UTILS SEE } EXEC \>> }

This executes EXEC, which requires something to do on the stack--in this
case, a list providing the path to the utility SEE inside the HOME UTILS
sub-directory.  EXEC is polite and returns you to your original directory
after executing the chosen utility, unless that utility somehow badly 
crashes.

Scott.