From: Michael Haubenwallner <michael.haubenwallner@ssi-schaefer.com>
To: Takashi Yano <takashi.yano@nifty.ne.jp>
Cc: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] cygwin 3.1.0-0.6 (TEST)
Date: Wed, 02 Oct 2019 14:04:00 -0000 [thread overview]
Message-ID: <1e27eef9-930c-0441-3da3-8039c84206e8@ssi-schaefer.com> (raw)
In-Reply-To: <announce.20190922101035.2703-1-kbrown@cornell.edu>
Hi Takashi,
On 9/22/19 4:11 PM, Ken Brown wrote:
> There have been a lot of changes in the PTY code since
> cygwin-3.1.0-0.5. Please test!
seems there is another issue related to new PTY code:
* I'm logged into some Server 2012r2 box via Cygwin sshd from Linux xterm,
* export EDITOR=vim # but same problem with EDITOR=emacs
* cd to some git project
* git rebase -i HEAD^
* Ctrl-Z, to temporarily return to shell prompt
Both the editor and the git processes seem to be suspended, but the
shell does not react nor show the prompt in any way, although further
keyboard input characters are displayed.
In a different (ssh) session, with 'ps' I can see the 'git' and 'vim'
processes to be suspended, as in having a leading 'S':
$ ps | grep pty0
S 51349 51348 51346 27448 pty0 197609 14:37:21 /usr/bin/vim
S 51346 51176 51346 11280 pty0 197609 14:37:20 /usr/bin/git
51176 51174 51176 39632 pty0 197609 14:26:41 /usr/bin/bash
S 51348 51346 51346 30960 pty0 197609 14:37:21 /usr/libexec/git-core/git
Resuming these processes with 'kill -CONT 51349 51346 51348' seems to work so far,
but when quitting the editor (using :q), the vim process is gone, but both git
processes do consume 100% (one single cpu) each, without any further result.
Any idea?
Thanks!
/haubi/
--
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
next prev parent reply other threads:[~2019-10-02 14:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-22 16:24 Ken Brown
2019-09-24 7:38 ` Michael Haubenwallner
2019-09-24 12:50 ` Ken Brown
2019-09-24 23:05 ` Ken Brown
2019-09-25 18:30 ` Takashi Yano
2019-09-26 12:51 ` Takashi Yano
2019-09-26 14:38 ` Ken Brown
2019-10-02 14:04 ` Michael Haubenwallner [this message]
2019-10-02 18:24 ` Ken Brown
2019-10-03 10:44 ` Takashi Yano
2019-10-10 10:44 ` Michael Haubenwallner
2019-10-11 9:25 ` Takashi Yano
2019-10-14 11:07 ` Michael Haubenwallner
2019-10-16 12:32 ` Takashi Yano
2019-10-18 11:36 ` Takashi Yano
2019-10-16 14:34 ` Takashi Yano
2019-10-16 16:34 ` Michael Haubenwallner
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=1e27eef9-930c-0441-3da3-8039c84206e8@ssi-schaefer.com \
--to=michael.haubenwallner@ssi-schaefer.com \
--cc=cygwin@cygwin.com \
--cc=takashi.yano@nifty.ne.jp \
/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).