X-Spam-Check-By: sourceware.org Date: Fri, 3 Mar 2006 21:33:38 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Bug: run emacs: fatal error reading the windows environment Message-ID: <20060303203338.GE3184@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <87bqwnwk4p DOT fsf AT ghoti DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87bqwnwk4p.fsf@ghoti.com> User-Agent: Mutt/1.4.2i Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , 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 11:47, Kirk Hilliard wrote: > Hi All, > > After upgrading cygwin, my emacs shortcut stopped working and I > discovered that ``run emacs'' yielded the error: > > 12 [main] emacs 900 C:\cygwin\bin\emacs.exe: *** fatal error - > internal error reading the windows environment -- > too many environment variables? Is that a native Windows emacs? A Cygwin emacs shouldn't have any problem. Otherwise, if it's a native Windows emacs, could you try with the latest version of the "cygstart" tool instead of "run"? Alexander, does the latest "run" version have the stuff added to regenerate the Windows environment before calling CreateProcess, like cygstart has? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/