Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!cbatt!cblpf!cblpe!feb
From: feb@cblpe.UUCP
Newsgroups: comp.sys.amiga
Subject: Re: The PATH that was missing experience
Message-ID: <497@cblpe.UUCP>
Date: Tue, 7-Apr-87 17:36:06 EST
Article-I.D.: cblpe.497
Posted: Tue Apr  7 17:36:06 1987
Date-Received: Sat, 11-Apr-87 00:34:11 EST
References: <536@madvax.UUCP>
Reply-To: feb@cblpe.UUCP (55216-Franco Barber)
Organization: AT&T Bell Laboratories - Columbus
Lines: 25
Keywords: PATH command

In article <536@madvax.UUCP> richc@madvax.UUCP (Rich Commins) writes:
>
...[edited]...
>I thought a path command should specify a search path for the computer, not
>just for the current CLI.  Is this a bug with the path command or a feature.
...[edited]...
>
>	Thanks in advance
>-- 
>-- 
>Rich Commins   (415)939-2400				          \  /\
>Varian Instruments, 2700 Mitchell Drive, Walnut Creek, CA 94598    \/--\
>{ptsfa,lll-crg,zehntel,dual,amd,fortune,ista,rtech,csi,normac}varian!richc


In my humble opinion,

the PATH set in a certain CLI (shell) (Unix influence showing here) should be
used by that CLI (shell) and any new CLIs (shells) run from that CLI (shell)
only. The reason is that different tasks running in different CLIs (shells)
should be able to get at the commands they need, in the order they need them,
regardless of other tasks running on the machine.
-- 
Franco Barber    AT&T Bell Laboratories, Columbus, Ohio
..!cbatt!cbplf!cblpe!feb                 (614) 860-7803