From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16370 invoked by alias); 26 Oct 2011 22:45:23 -0000 Received: (qmail 16358 invoked by uid 22791); 26 Oct 2011 22:45:22 -0000 X-SWARE-Spam-Status: No, hits=-1.3 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_NEUTRAL X-Spam-Check-By: sourceware.org Received: from granite1.mail.cornell.edu (HELO authusersmtp.mail.cornell.edu) (128.253.83.141) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 26 Oct 2011 22:45:07 +0000 Received: from [192.168.1.4] (cpe-67-249-194-47.twcny.res.rr.com [67.249.194.47]) (authenticated bits=0) by authusersmtp.mail.cornell.edu (8.14.4/8.12.10) with ESMTP id p9QMj07O015881 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Wed, 26 Oct 2011 18:45:06 -0400 (EDT) Message-ID: <4EA88D6D.1040005@cornell.edu> Date: Thu, 27 Oct 2011 18:22:00 -0000 From: Ken Brown User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 MIME-Version: 1.0 To: cygwin-xfree Subject: Re: Cygwin xterm and emacs-X11 broken in Windows 7 References: <1319659701.62695.YahooMailRC@web80701.mail.mud.yahoo.com> In-Reply-To: <1319659701.62695.YahooMailRC@web80701.mail.mud.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-xfree-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-xfree-owner@cygwin.com Reply-To: cygwin-xfree@cygwin.com Mail-Followup-To: cygwin-xfree@cygwin.com X-SW-Source: 2011-10/txt/msg00055.txt.bz2 [Removing the cygwin list from the CC.} On 10/26/2011 4:08 PM, Zdzislaw Meglicki wrote: [...] > Perhaps related: in emacs-X11 entering the shell mode (M-x shell) kills the > shell. I just get a prompt, then "exit" and a message > > > Process shell finished > > This does *not* happen in emacs-nox, neither does this happen in xemacs. It works fine for me, so my best guess is that this is related to your other X problems. But you might try a recent Cygwin snapshot, on the off chance that that helps. There have been several changes that have an impact on processes running under emacs. Ken -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/