To: cygwin@cygwin.com
Subject: Re: xemacs -nw  problem
References: <200705021455.18980.andrew@walrond.org> 	<82d51cy9s1.fsf@vzell-de.de.oracle.com> <463FE8C4.5040004@byu.net>
From: "Dr. Volker Zell" <Dr.Volker.Zell@oracle.com>
Date: Tue, 08 May 2007 15:50:53 +0200
In-Reply-To: <463FE8C4.5040004@byu.net> (Eric Blake's message of "Mon, 07 May 2007 21:04:36 -0600")
Message-ID: <82ejlrh1aa.fsf@vzell-de.de.oracle.com>
User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4.20 (cygwin32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

>>>>> Eric Blake writes:

    > According to Dr. Volker Zell on 5/7/2007 8:43 AM:
    >>>>>>> Andrew Walrond writes:
    >> 
    >> > A minor problem (possible bug): If I try to run xemacs in the cygwin terminal,  
    >> > without an X window, via the -nw option, its behaviour is a little stange:
    >> 
    >> > Ctrl-x ctrl-c does not exit, merely prints "Quit" on the bottom (command?) 
    >> > line.
    >> 
    >> Works for me.

    > Could it be a matter of your terminal settings?  If you use cmd.com
    > (instead of rxvt or bash), and have CYGWIN=notty (default) instead of
    > CYGWIN=tty, then ctrl-c is not captured properly by xemacs, making key
    > sequences such as ctrl-x ctrl-c impossible to type.

I just had a chance to install cygwin on a new machine.
Under the default bash shell the CYGWIN environment variable is not
exported. In that case I can reproduce Andrews xemacs problems.

Exporting CYGWIN=tty resolves the issues.

Ciao
  Volker


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