Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!sdd.hp.com!spool.mu.edu!uunet!comp.vuw.ac.nz!actrix!templar!jbickers
From: jbickers@templar.actrix.gen.nz (John Bickers)
Newsgroups: comp.sys.amiga.advocacy
Subject: Re: How to improve Workbench 2.0!
Message-ID: <10961.tnews@templar.actrix.gen.nz>
Date: 5 Feb 91 23:37:36 GMT
References: <779@caslon.cs.arizona.edu> <1991Feb4.134336.23501@ux1.cso.uiuc.edu> <1991Feb4.151637.5868@mintaka.lcs.mit.edu>
Organization: TAP, NZAmigaUG.
Lines: 27

Quoted from <1991Feb4.151637.5868@mintaka.lcs.mit.edu> by rjc@geech.ai.mit.edu (Ray Cromwell):
>  What are the benifits of env vars? How many times has a program
> assumed the path of a program. Like a picture file looking for 'myhd:picviewer'

    One problem is that programs often assume the arguments a sub-program
    will take, as well as it's name.

> The tooltype of pictures/music/textfiles, etc would have to execute
> s:envexpand which would GetEnv the var and execute it.
> 
>  Any ideas?

    I do the following to set up a path, a resident list, and an alias
    list when I start Workbench:

        'wb-back'
        'wb-resi dh0:utils/ty dh0:utils/mostra'
        'wb-alias more ty less ty muchmore ty most ty'
        'wb-alias viewilbm mostra seeall mostra show mostra display mostra\
            superview mostra showpics mostra'
        'wb-path dh0:utils'

    I'd prefer a built-in alias/path system like the CLI uses, that could
    access the same lists.
--
*** John Bickers, TAP, NZAmigaUG.        jbickers@templar.actrix.gen.nz ***
***         "Patterns multiplying, re-direct our view" - Devo.          ***