From: "Tony O'Bryan" <aho450s AT nic DOT smsu DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Environment: OPTIONS\DIRECTORIES
Date: Sat, 20 Dec 1997 09:15:51 -0600
Organization: Southwest Missouri State University
Lines: 17
Message-ID: <349BE127.7504@nic.smsu.edu>
References: <349B12FF DOT 3C97D3DA AT mpinet DOT net>
Reply-To: aho450s AT nic DOT smsu DOT edu
NNTP-Posting-Host: sara.a11.smsu.edu
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

Ben wrote:

> 2) The above may or may-not work, but has some possible bugs:
> changing the (object) and (sources) to my choice... so I can always open
> to the appropriate dir & save my *.o and *.exe files to another
> directory, other than the default /bin directory, causes a problem. I
> cannot progress any further after compiling my *.c file. All subsequent
> commands (make/link/run) are all shaded out. Now, if I go back and
> remove any directory changes and let it default to it's own and restart.
> It works fine, but my *.o & *.exe file ends up in the \bin directory.
> Anybody have a solution?

	Which version of RHIDE are you using?  I have been unable to reproduce
the bug in version 1.4 where any appropriate commands are shaded out.  
	Whether you use a forward slash or a backslash in DJGPP doesn't
matter.  They are treated the same (except in source code where a
backslash must be escaped with another backslash).