X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=0.1 required=5.0	tests=AWL,BAYES_20,SPF_NEUTRAL,T_RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
Message-ID: <4D9F8BC8.7040303@cornell.edu>
Date: Fri, 08 Apr 2011 18:27:20 -0400
From: Ken Brown <kbrown AT cornell DOT edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: gnutls-cli / emacs daemon stops mintty window closing
References: <injp03$h8r$1 AT dough DOT gmane DOT org> <4D9DBB17 DOT 2090902 AT cornell DOT edu> <inn8ab$3q9$1 AT dough DOT gmane DOT org> <4D9F3570 DOT 2050603 AT cornell DOT edu>
In-Reply-To: <4D9F3570.2050603@cornell.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
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

On 4/8/2011 12:18 PM, Ken Brown wrote:
> On 4/8/2011 11:06 AM, Gary wrote:
>> Ken Brown wrote:
>>> On 4/7/2011 3:26 AM, Gary wrote:
>>>> If I start emacs using<<emacsclient -t --alternate-editor="">>   and
>>> that
>>>> emacs session uses gnutls, then after quitting emacs (or rather,
>>>> emacsclient - the emacs-nox process is, and should be, still running),
>>>> and then typing<<exit>>   the mintty window fails to close. Stopping the
>>>> emacs-nox process achieves nothing, but stopping the gnutls-cli
>>> process
>>>> results in the mintty window closing correct. The bash process ends in
>>>> any case.
>>>
>>> Since stopping emacs achieves nothing, I wonder if this has anything to
>>> do with emacs.
>>
>> I think it must be. I had the same problem at home, and noticed gnu-tls
>> wasn't involved but openssl was (in the same was as gnu-tls,
>> above). openssl was, as with gnu-tls, started via emacs.
>
> Whatever process emacs started, I still have the same questions as in my
> original reply.  (a) What happens if you start the process on the
> command line instead of via emacs?  (b) Are you sure that what you're
> seeing is not the expected behavior?
>
> Part of my problem in trying to help is that you haven't said exactly
> what you're doing, except that your emacs session used gnutls in one
> case and that openssl was involved in the other.  Can you give a
> detailed list of steps that someone might try to reproduce?

I found a simple way to reproduce this.  Start an emacsclient session in 
a mintty window as you did, start a shell within emacs, and then exit 
(with C-x C-c, not with M-x kill-emacs).  This leaves the emacs daemon 
running as well as the shell process, as I would expect.  Then the 
mintty window won't close until the shell process is killed.  Again, I'm 
not convinced this is a bug.  After all, the shell process is an 
interactive process associated with the terminal.  Wouldn't you expect 
to have to kill that process before the terminal window closes?

On the other hand, if you kill the emacs server in the normal way (via 
M-x kill-emacs, as explained in the server documentation), it also kills 
the shell process, and you can exit from mintty.

Incidentally, this has nothing to do with mintty.  The same thing 
happens in the Cygwin console.

Ken

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple