From: "Paul Johnston" <johnston.p@worldnet.att.net>
To: "Cygwin" <cygwin@sourceware.cygnus.com>
Subject: Can't abort command line with Ctrl-C anymore...
Date: Sun, 24 Sep 2000 15:02:00 -0000 [thread overview]
Message-ID: <028201c02675$1b5ef150$db41480c@hxzcw> (raw)
Hi, I've just upgraded from B20 to net release 1.1.4 (latest, as of today).
Nice install! Anyway, when I type a command ctrl-c does not abort it.
Ctrl-C still works to interrupt a running process, but I can't bail out of a
command without using the backspace key. Is this a setting or has the
behavior of bash changed? I'm on NT4.
Thanks for your help on such a small issue,
Paul
---------------------------------------
Cygwin DLL version info:
dll major: 1001
dll minor: 4
dll epoch: 19
dll bad signal mask: 19005
dll old termios: 5
api major: 0
api minor: 26
shared data: 3
dll identifier: cygwin1
mount registry: 2
cygnus registry name: Cygnus Solutions
cygwin registry name: Cygwin
program options name: Program Options
cygwin mount registry name: mounts v2
build date: Thu Aug 3 20:53:46 EDT 2000
CVS tag: cygwin-1-1-4
shared id: cygwin1S3
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next reply other threads:[~2000-09-24 15:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-24 15:02 Paul Johnston [this message]
2000-09-25 1:09 ` [BASH] Backtick problem still NOTsolved!! (Win95b/CW1.1.4) Andreas Eibach
2000-09-25 2:00 ` Corinna Vinschen
2000-09-25 5:09 ` Andreas Eibach
2000-09-25 5:43 ` [BASH] Backtick problem still NOTsolved! [STRACE output inside] Andreas Eibach
2000-10-05 3:25 ` [BASH] Backtick problem still NOTsolved!! (Win95b/CW1.1.4) Corinna Vinschen
2000-10-05 3:33 ` Corinna Vinschen
2000-10-06 12:01 ` Andreas Eibach
2000-10-06 12:03 ` Andreas Eibach
2000-09-25 8:55 ` Can't abort command line with Ctrl-C anymore Chris Faylor
2000-09-26 5:14 Earnie Boyd
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='028201c02675$1b5ef150$db41480c@hxzcw' \
--to=johnston.p@worldnet.att.net \
--cc=cygwin@sourceware.cygnus.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).