delorie.com/archives/browse.cgi | search |
X-Spam-Check-By: | sourceware.org |
To: | cygwin AT cygwin DOT com |
Subject: | Re: Bug: run emacs: fatal error reading the windows environment |
From: | Kirk Hilliard <kirk AT ghoti DOT com> |
Date: | 03 Mar 2006 15:51:21 -0500 |
Message-ID: | <8764mv9rqu.fsf@ghoti.com> |
Lines: | 21 |
User-Agent: | Gnus/5.09 (Gnus v5.9.0) Emacs/21.4 |
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 |
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 -- 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/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |