X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Message-ID:	<47D75882.347EC96C@dessent.net>
Date:	Tue, 11 Mar 2008 21:13:54 -0700
From:	Brian Dessent <brian AT dessent DOT net>
X-Mailer:	Mozilla 4.79 [en] (Windows NT 5.0; U)
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: emacs 21.3 does work while 22.1 works: Why 21.3 is default in cygwin setup
References:	<20080312015639 DOT 83950 DOT qmail AT web3312 DOT mail DOT ogk DOT yahoo DOT co DOT jp>
X-IsSubscribed:	yes
Reply-To:	cygwin AT cygwin DOT com
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
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

Tatsuro MATSUOKA wrote:

> After that I cannot execute
> $ emacs
> Nothing happend
> Only
> $ emacs -nw
> worked.
> This happens both in home and university.

That can happen either a) you have $DISPLAY set but you aren't running
an X11 server or b) you are running an X11 server but $DISPLAY is not
set correctly to refer to it.  In either case emacs will sit there
trying to connect to something that doesn't exist.  It should time out
after several minutes though, which you can check to see if that is the
case.  If so, fix your setting of DISPLAY.

The other possibility is the issue of a rebased cygncurses7 that causes
emacs to go into a 100% cpu spinloop at startup, for some as-yet
unidentified reason.  However if emacs -nw works then that more or less
rules out this possibility.

Brian

--
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 -