public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: saltnlight5 <saltnlight5@gmail.com>
To: cygwin@cygwin.com
Subject: RE: CTRL+C is not working with java on latest cygwin 1.7.15
Date: Thu, 12 Jul 2012 21:39:00 -0000	[thread overview]
Message-ID: <34153436.post@talk.nabble.com> (raw)
In-Reply-To: <001e01cd606a$c0b37a40$421a6ec0$@motionview3d.com>


Thanks for the tips James, however, I tried the lastest snaphost
cygwin1-20120708.dll.bz2 it still not working.


James Johnston-5 wrote:
> 
>> -----Original Message-----
>> Sent: Wednesday, July 11, 2012 20:07
>> Subject: Re: CTRL+C is not working with java on latest cygwin 1.7.15
>> 
>> 
>> Thanks for the reply "K Stahl", but it didn't work for me. I ran the same
> Test,
>> then press CTRL+C. But the cygwin terminal did nothing. It did not stop
> the
>> java process, and it did not print any thing further. I must manually
> terminate
>> the process by going into Windows TaskManager.
>> 
>> Again, here is my cygwin version:
>> $ uname -srv
>> CYGWIN_NT-5.1 1.7.15(0.260/5/3) 2012-05-09 10:25
>> 
>> Am I on the latest version as you said? Did I miss any other config?
> 
> Actually, not so much on the latest version.  Did you try the most recent
> Cygwin snapshot?  Version 1.7.15 has some problems with hanging when
> running
> non-Cygwin programs but this was fixed in a later snapshot, perhaps this
> is
> related?
> 
> 
> --
> 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
> 
> 
> 


-----
----
Zemian Deng
-- 
View this message in context: http://old.nabble.com/CTRL%2BC-is-not-working-with-java-on-latest-cygwin-1.7.15-tp34147441p34153436.html
Sent from the Cygwin list mailing list archive at Nabble.com.


--
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:[~2012-07-12 21:39 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-11 18:47 saltnlight5
2012-07-11 19:18 ` K Stahl
     [not found]   ` <1355306723156-63181.post@n5.nabble.com>
2012-07-11 19:55   ` saltnlight5
2012-07-11 20:06     ` K Stahl
2012-07-11 20:07     ` saltnlight5
2012-07-11 20:17       ` K Stahl
2012-07-11 20:26         ` saltnlight5
2012-07-11 20:34           ` K Stahl
2012-07-11 20:37             ` K Stahl
2012-07-12  1:40             ` Earnie Boyd
2012-07-12 13:02               ` saltnlight5
2012-07-12 13:23                 ` K Stahl
2012-07-12 15:39                 ` Earnie Boyd
2012-07-12 20:13       ` James Johnston
2012-07-12 21:39         ` saltnlight5 [this message]
2012-08-02 17:31       ` Roger K. Wells
2012-12-12 10:05         ` erik56d
2012-12-12 14:06           ` Aaron Schneider
2012-12-12 17:26             ` erik56d
2012-07-12 14:24   ` Aaron Schneider
2012-07-12 21:57 ` saltnlight5

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=34153436.post@talk.nabble.com \
    --to=saltnlight5@gmail.com \
    --cc=cygwin@cygwin.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).