home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.sys.amiga.programmer:19236 comp.sys.amiga.misc:20535
- Newsgroups: comp.sys.amiga.programmer,comp.sys.amiga.misc
- Path: sparky!uunet!ukma!darwin.sura.net!haven.umd.edu!wam.umd.edu!walrus
- From: walrus@wam.umd.edu (Udo K Schuermann)
- Subject: Re: Stupid Workbench 2.1 and path command!
- Message-ID: <1993Jan28.003007.8899@wam.umd.edu>
- Sender: usenet@wam.umd.edu (USENET News system)
- Nntp-Posting-Host: rac3.wam.umd.edu
- Organization: University of Maryland, College Park
- References: <1993Jan27.010659.63232@cc.usu.edu> <1993Jan27.010849.63233@cc.usu.edu> <1993Jan27.232328.9775@ugle.unit.no>
- Date: Thu, 28 Jan 1993 00:30:07 GMT
- Lines: 16
-
- In article <1993Jan27.232328.9775@ugle.unit.no> ammm@Lise.Unit.NO (Marius Mortensen) writes:
- >In article <1993Jan27.010849.63233@cc.usu.edu>, slhmz@cc.usu.edu writes:
- >>
- >> What's the deal? I _NEED_ those path assignments.
- >> They don't work while in a script! Not even in "user-startup"
- >
- >Put the path description in shell-startup instead. (Or preferably both in
- >user-startupo and shell-startup. the startup-sequence should not be altered).
-
- I store all path commands in S:myPaths and have both in user-startup and
- shell-startup the command execute S:myPaths so that I never need to
- modify more than one file to alter the paths for either Workbench or the
- shell.
-
- ._. Udo Schuermann
- ( ) walrus@wam.umd.edu
-