X-Spam-Check-By:	sourceware.org
Message-ID:	<2fc802c00603051313s72dd20e8ic644aa467209e2ed@mail.gmail.com>
Date:	Sun, 5 Mar 2006 21:13:07 +0000
From:	"David Picton" <djpicton AT gmail DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Bug: run emacs: fatal error reading the windows environment
MIME-Version:	1.0
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id k25LDERV029213

>    From: Kirk Hilliard <kirk at ghoti dot com>
>    Date: 03 Mar 2006 15:51:21 -0500

> On Mar  3 21:33, Corinna Vinschen wrote:
>> Is that a native Windows emacs?  A Cygwin emacs shouldn't have any
>> problem.
>
> No, it is the cygwin emacs.
>
>``run emacs'' fails with
>  12 [main] emacs 900 C:\cygwin\bin\emacs.exe: *** fatal error -
>  internal error reading the windows environment --
>  too many environment variables?
> but when run as ``emacs'' from an xterm it works fine.  What I first
> noticed is that it fails silently when launched from a shortcut that
> calls ``run emacs'', so I tried that from the xterm to see what was
> going on.
>
> I will be surprised if I turn out to be the only one this affects, as
> it occurs on two separate machines, one upgraded, the other
> re-installed fresh.  (Perhaps not so many people launch emacs from a
> shortcut.)
>
> Kirk

I also see the problem.  Emacs fails as described - it would appear
that there is a bug in the routine which converts the Windows
environment to the Cygwin environment.

As a temporary workaround, I changed the icon command to the following:

D:\cygwin\bin\run.exe -p /usr/bin:/usr/X11R6/bin bash -c 'emacs
-display 127.0.0.1:0.0'

This works OK.  It would appear that emacs is happy if it is started
by a Cygwin process - presumably it doesn't need to read the Windows
environment in this case but simply
inherits the Cygwin environment from its parent process.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -