Path: utzoo!mnetor!uunet!husc6!mit-eddie!ll-xn!ames!ucbcad!pasteur!ucbvax!ulysses!gsf
From: gsf@ulysses.homer.nj.att.com (Glenn Fowler[eww])
Newsgroups: comp.unix.questions
Subject: Re: Slave shell in nmake
Message-ID: <3342@ulysses.homer.nj.att.com>
Date: 15 Jan 88 18:12:28 GMT
References: <206@ksr.UUCP> <3325@ulysses.homer.nj.att.com> <367@dlhpedg.co.uk>
Organization: AT&T Bell Laboratories, Murray Hill
Lines: 14
Summary: nmake actions in sub-shell

In article <367@dlhpedg.co.uk>, cl@dlhpedg.UUCP writes:
> ... whether there should be one slave shell for the entire execution
> of nmake, or whether a separate shell should be spawned (and subsequently
> input-terminated) for each rule block.  ...

by default nmake actions are executed in sub-shells using {...}& so
environment changes (e.g., cd, export) affect the current action only

the action for a target with the .FOREGROUND attribute is executed directly
by the top level shell so in this case environment changes affect all actions
that follow
-- 
    Glenn Fowler                    AT&T Bell Laboratories, Murray Hill
    {ihnp4,allegra}!ulysses!gsf                          (201)-582-2195