public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrey Repin <anrdaemon@yandex.ru>
To: Dani Moncayo <dmoncayo@gmail.com>, cygwin@cygwin.com
Subject: Re: Mintty does not close after "exit" command
Date: Wed, 24 May 2017 11:32:00 -0000	[thread overview]
Message-ID: <498347636.20170524130547@yandex.ru> (raw)
In-Reply-To: <CAH8Pv0iiRvbGcd1_BYTXT+jRmUs_oYMLezVqT5Q6iFN-1QeL4g@mail.gmail.com>

Greetings, Dani Moncayo!

> Hi,

> subject line says it all.

> I've been experiencing this problem for some months, on windows 10.
> But the problem does not appear in another windows 8.1 system I use.

> To reproduce the problem, just open the standard cygwin terminal (e.g.
> by double-clicking the desktop icon), an then type the "exit" command
> in the bash shell.

> I see a "logout" message for a fraction of a second, then the terminal
> becomes empty (without text), but the mintty window remains visible
> but unresponsive, with the title bar showing "~ (Not Responding)".

Anything suspicious in logout script?
One known cause if it could be reproduced fairly easy with ssh to a remote
host. Once ssh session ends, MinTTY will stick after exit, until you press
Enter.


-- 
With best regards,
Andrey Repin
Wednesday, May 24, 2017 13:04:08

Sorry for my terrible english...


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

  reply	other threads:[~2017-05-24 10:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-24  9:27 Dani Moncayo
2017-05-24 11:32 ` Andrey Repin [this message]
2017-05-24 12:54   ` Dani Moncayo
2017-05-25  9:57 ` Sky Diver

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=498347636.20170524130547@yandex.ru \
    --to=anrdaemon@yandex.ru \
    --cc=cygwin@cygwin.com \
    --cc=dmoncayo@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).