Date: Sun, 16 Mar 1997 16:22:22 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: mtc AT acsu DOT buffalo DOT edu
cc: djgpp AT delorie DOT com
Subject: Re: Emacs
In-Reply-To: <332AFE72.7753@cs.buffalo.edu>
Message-ID: <Pine.SUN.3.91.970316162145.12150j-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Sat, 15 Mar 1997 mtc AT acsu DOT buffalo DOT edu wrote:

> I am having a problem using emacs with djgpp. I am running win95 and
> when then I have the statement SET DJGPP=d:\DJGPP\DJGPP.ENV in my
> autoexec emacs won't run. When I type emacs it just returns to the
> command line.

That's most probably because your DJGPP.ENV disables long filenames
support, and Emacs needs access to long filenames to find some of the
packages it loads at startup.  You have two alternatives to deal with
that:

	1) Set LFN=y in the DOS box where you run Emacs.  You can put
that setting into the batch file that is run when the DOS box is
started (this is set up in the DOS box property sheets).  (The same
can be achieved by editing DJGPP.ENV, but I don't recommend it,
because DJGPP.ENV has a complex syntax, and editing it can break some
of DJGPP programs.)

	2) If you need to disable long filenames support, you will
have to make sure that Emacs distribution is unzipped with the
NameNumericTail property of Windows 95 DISABLED, so that long
filenames don't get the ~1 tails tackled onto them.  The DJGPP FAQ
list has the details about this in section 8.2.

> When I remove the statement it works but then I can't
> compile programs. Any ideas ?

If the problem with compilation doesn't go away when you solve the
above problem, please post the details: what exactly goes wrong when
you try to compile, and what Emacs commands do you use to compile?

> Also when I type gxx from a dos box in
> win95 it says "This program can not be run in dos mode"

Does this happen with gcc or any other DJGPP programs?  One possible
problem is that you have another (non-DJGPP) cpp.exe lurking on your
PATH and gxx invokes it instead of its own cpp.exe.  If this doesn't
help, add -v to the gxx command line, then post everything it prints.

> Do I need to
> load the cswdpi as a tsr ? I thought windows would take care of this ?

You are right, you don't need CWSDPMI on Windows 95.  CWSDPMI won't
even load there.