Date:	Sun, 8 Sep 1996 09:53:37 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To:	Mark Habersack <grendel AT ananke DOT amu DOT edu DOT pl>
Cc:	djgpp AT delorie DOT com
Subject:	Re: Emacs 19.34 again
In-Reply-To:	<Pine.NEB.3.95.960906130108.4367B-100000@ananke.amu.edu.pl>
Message-Id:	<Pine.SUN.3.91.960908094743.5416U-100000@is>
Mime-Version:	1.0

On Fri, 6 Sep 1996, Mark Habersack wrote:

> I have this strange problem with Emacs 19.34. After applying all the patches
> to my libc I have compiled the sources without any problems. Everything works
> OK but only under DOS. When, however, I try to run emacs from under Loose95
> (oops, Win95 ;-)) it starts, shows the invitation screen but just for a short
> while. After that the screen flashes and I back to the command prompt. What
> might be the cause of this problem?

Try setting LFN=y and LFN=n explicitly in the environment and see if any
of these two make Emacs work on Windows 95.  Depending on which one works,
I might guess what's wrong and suggest a solution. 

Which program did you use to unzip the .tar.gz distribution?

> task. AFAIK GDB can run as a debugging server alongside with it's frontend.
> The frontend task is to interpret messages and strings passed from GDB and
> respond to them in appropriate way, either by sending back some message to GDB
> or showing the user what's going on. Why isn't it possible under MS-DOG (I
> mean it is possible, but not from under Emacs).

This is not how the debugger interface in Emacs works.  The way it is 
written, it runs the debugger as an asynchronous process, and that just 
doesn't work on MSDOS.

- Raw text -