From: arkane Newsgroups: comp.os.msdos.djgpp Subject: Re: Setting env variables Date: Wed, 17 Dec 1997 08:18:01 -0500 Organization: University of New Hampshire - Durham, NH Lines: 43 Message-ID: References: <6783jr$gv2 AT freenet-news DOT carleton DOT ca> NNTP-Posting-Host: christa.unh.edu Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII In-Reply-To: <6783jr$gv2@freenet-news.carleton.ca> To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Precedence: bulk I don't remember that command ever coming with DOS. I think that 'set' is part of the command.com shell. Somebody tell me I am wrong here. Jeese the things you forget when you start working with better shells like BASH. On the other hand we could always search the web for implementations of this command. I think I remember a couple at simtelnet, don't remember much else though. arkane On 17 Dec 1997, Paul Derbyshire wrote: > Date: 17 Dec 1997 08:47:55 GMT > From: Paul Derbyshire > Newsgroups: comp.os.msdos.djgpp > Subject: Setting env variables > > > > > Firstly if PUTENV only affects the environment within the calling program > why use it? Why not use a variable? > > Secondly, maybe someone can decompile the set.com (or whatever it is) that > comes with DOS to see how to modify the parent environment. The SET > command works nicely for this: > > > set djgpp=c:/foo/bar/blah ; In Autoexec.bat, gets done at startup > > gcc -o foo.exe foo.c ; This works, ergo the above changed DJGPP not > ; just for SET but for the parent DOS session > -- > .*. Friendship, companionship, love, and having fun are the reasons for > -() < life. All else; sex, money, fame, etc.; are just to get/express these. > `*' Send any and all mail with attachments to the hotmail address please. > Paul Derbyshire ao950 AT freenet DOT carleton DOT ca pgd73 AT hotmail DOT com > > .rorrim a tuohtiw erutangis siht daer nac uoy nehw keeg a era uoy wonk uoY .erutangis siht esrever ot margorp a etirw uoy nehw rekcah a era uoy wonk uoY