Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!uunet!munnari.oz.au!bruce!monu0.cc.monash.edu.au!vaxc.cc.monash.edu.au!hadgraft
From: hadgraft@vaxc.cc.monash.edu.au (Hadgraft)
Newsgroups: comp.windows.ms
Subject: Re: PATH for Windows applications
Message-ID: <1991Jun11.093230.86868@vaxc.cc.monash.edu.au>
Date: 10 Jun 91 23:32:30 GMT
References: <1991Jun6.095516.86840@vaxc.cc.monash.edu.au> <1991Jun6.184053.12028@cs.uoregon.edu>
Organization: Civil Engineering, Monash University, Australia
Lines: 32

>
> I don't have this problem, and here is why...
>
> I'll try and describe my setup with Excel and Winword as examples.
> Some directory info:
>
> Windows       d:\windows
> Winword               d:\winword
> Excel         e:\excel
>
> Note that this does not include either winword or excel
>
> On the other hand, I do have a problem with memacs, which insists on
> being in the path, and grumbles about not being able to find its
> various .cmd files if it isn't in the path.
>
Yes. Excel and WinWord don't seem to need to be in the PATH, but others do.
GUIDE (hypertext), for example, can't find its files unless it's in the PATH.
Why can't they be sensible like Excel etc? What is also annoying is that the
manuals for these packages do not make it clear whether the package REALLY needs
to be on the PATH or not.

I'm convinced that the developers of these packages think that everyone only
uses one or two packages.
--
  +--------------------------------------+
  |  Roger Hadgraft                 +----------------------------------+
  |  Senior Lecturer                |  hadgraft@civeng.monash.edu.au   |
  |  Dept of Civil Engineering      |  phone:  +61 3 565 4983          |
  |  Monash University              |  fax:    +61 3 565 4944 or 3409  |
  |  Clayton, Vic. 3168. Australia. +----------------------------------+
  +--------------------------------------+