From: Benjamin Cao <becao@progress.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: CTRL-C not working in sh login mode?
Date: Mon, 16 Nov 2015 19:29:00 -0000 [thread overview]
Message-ID: <393ce3c74d914e0e9d1ace4262830a10@ntmaexbe03.bedford.progress.com> (raw)
-----Original Message-----
From: Benjamin Cao
Sent: Friday, November 13, 2015 3:46 PM
To: 'cygwin@cygwin.com'
Subject: CTRL-C not working in sh login mode?
Hi,
We invoke a shell using a *.bat file doing sh --login.
We have discovered that when wanting to kill a long running process with CTRL-C, it does not work.
Is this expected behavior?
I've found that to be the same even if I am doing bash --login -i in my *.bat file.
Any guidance would be greatly appreciated.
Hi,
Just wanted to provide some additional information to make things a bit clearer.
Running either "sh -login" or "bash --login -I" from a *.bat file will cause some commands to not be broken with CTRL-C.
For example, this test loop cannot be broken with CTRL-C when I start Cygwin up from the *.bat file.
echo foo | perl -e 'while(1) {sleep 60;}'
Or if I do "cat <file_name> | more", CTRL-C does not work in that case.
Again, is that expected behavior?
Thanks,
Ben Cao
--
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 reply other threads:[~2015-11-16 19:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 19:29 Benjamin Cao [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-11-13 20:46 Benjamin Cao
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=393ce3c74d914e0e9d1ace4262830a10@ntmaexbe03.bedford.progress.com \
--to=becao@progress.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).