* Re: Interupting screen dump
@ 1999-09-14 12:28 Clark Sims
1999-09-19 16:48 ` Michael Hirmke
1999-09-30 23:42 ` Clark Sims
0 siblings, 2 replies; 6+ messages in thread
From: Clark Sims @ 1999-09-14 12:28 UTC (permalink / raw)
To: cygwin AT sourceware.cygnus.com
--
On Mon, 13 Sep 1999 12:05:12 Clark Sims wrote:
>How do I interupt a large screen dump, when I have jobs in background, without
>killing the background jobs? Ctrl-c kills everything, sometimes even bash.
>I just want to stop the screen from scrolling, ie. kill the most recent command
>which is dumping to screen.
>
>
>Thanks in Advance,
>
>Clark Sims
>
>
On page 25 of "Learning the bash shell", it says that ctrl-c should stop the current command. So this should do what I want, and it does sometimes. It looks like there is a small bug in this version of bash( bash 2.02.1(2) in Cygwin 20.1), because sometimes, to many commands get killed, including bash itself.
Should I report this as a bug?
>
>--== Sent via Deja.com http://www.deja.com/ ==--
>Share what you know. Learn what you don't.
>
>--
>Want to unsubscribe from this list?
>Send a message to cygwin-unsubscribe@sourceware.cygnus.com
>
>
--== Sent via Deja.com http://www.deja.com/ ==--
Share what you know. Learn what you don't.
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Interupting screen dump
1999-09-14 12:28 Interupting screen dump Clark Sims
@ 1999-09-19 16:48 ` Michael Hirmke
1999-09-30 23:42 ` Michael Hirmke
1999-09-30 23:42 ` Clark Sims
1 sibling, 1 reply; 6+ messages in thread
From: Michael Hirmke @ 1999-09-19 16:48 UTC (permalink / raw)
To: cygwin
Clark Sims [clarksimsgnu@my-Deja.com] wrote:
[...]
>On page 25 of "Learning the bash shell", it says that ctrl-c should stop the
>current command. So this should do what I want, and it does sometimes. It
>looks like there is a small bug in this version of bash( bash 2.02.1(2) in
>Cygwin 20.1), because somet imes, to many commands get killed, including bash
>itself.
>
>Should I report this as a bug?
Remember - this can't be the same behaviour as for bash on U*ix systems.
It all depends on the terminal handling of the underlying OS.
The terminal handling of Cygwin is far from being perfect, so you may
experience things that won't work or work different from what you read
in the docs for bash on a real Unix system.
Nevertheless try setting CYGWIN=tty - this significantly changes the
behaviour of terminal handling. Perhaps things will work better for you
then. You have to set this *before* the first Cygwin process gets
started.
Bye.
Michael.
--
Michael Hirmke | Telefon +49 (911) 557999
Georg-Strobel-Strasse 81 | FAX +49 (911) 557664
90489 Nuernberg | E-Mail mailto:mh@mike.franken.de
| WWW http://aquarius.franken.de/
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Interupting screen dump
1999-09-19 16:48 ` Michael Hirmke
@ 1999-09-30 23:42 ` Michael Hirmke
0 siblings, 0 replies; 6+ messages in thread
From: Michael Hirmke @ 1999-09-30 23:42 UTC (permalink / raw)
To: cygwin
Clark Sims [clarksimsgnu@my-Deja.com] wrote:
[...]
>On page 25 of "Learning the bash shell", it says that ctrl-c should stop the
>current command. So this should do what I want, and it does sometimes. It
>looks like there is a small bug in this version of bash( bash 2.02.1(2) in
>Cygwin 20.1), because somet imes, to many commands get killed, including bash
>itself.
>
>Should I report this as a bug?
Remember - this can't be the same behaviour as for bash on U*ix systems.
It all depends on the terminal handling of the underlying OS.
The terminal handling of Cygwin is far from being perfect, so you may
experience things that won't work or work different from what you read
in the docs for bash on a real Unix system.
Nevertheless try setting CYGWIN=tty - this significantly changes the
behaviour of terminal handling. Perhaps things will work better for you
then. You have to set this *before* the first Cygwin process gets
started.
Bye.
Michael.
--
Michael Hirmke | Telefon +49 (911) 557999
Georg-Strobel-Strasse 81 | FAX +49 (911) 557664
90489 Nuernberg | E-Mail mailto:mh@mike.franken.de
| WWW http://aquarius.franken.de/
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Interupting screen dump
1999-09-14 12:28 Interupting screen dump Clark Sims
1999-09-19 16:48 ` Michael Hirmke
@ 1999-09-30 23:42 ` Clark Sims
1 sibling, 0 replies; 6+ messages in thread
From: Clark Sims @ 1999-09-30 23:42 UTC (permalink / raw)
To: cygwin
--
On Mon, 13 Sep 1999 12:05:12 Clark Sims wrote:
>How do I interupt a large screen dump, when I have jobs in background, without
>killing the background jobs? Ctrl-c kills everything, sometimes even bash.
>I just want to stop the screen from scrolling, ie. kill the most recent command
>which is dumping to screen.
>
>
>Thanks in Advance,
>
>Clark Sims
>
>
On page 25 of "Learning the bash shell", it says that ctrl-c should stop the current command. So this should do what I want, and it does sometimes. It looks like there is a small bug in this version of bash( bash 2.02.1(2) in Cygwin 20.1), because sometimes, to many commands get killed, including bash itself.
Should I report this as a bug?
>
>--== Sent via Deja.com http://www.deja.com/ ==--
>Share what you know. Learn what you don't.
>
>--
>Want to unsubscribe from this list?
>Send a message to cygwin-unsubscribe@sourceware.cygnus.com
>
>
--== Sent via Deja.com http://www.deja.com/ ==--
Share what you know. Learn what you don't.
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 6+ messages in thread
* Interupting screen dump
1999-09-13 12:05 Clark Sims
@ 1999-09-30 23:42 ` Clark Sims
0 siblings, 0 replies; 6+ messages in thread
From: Clark Sims @ 1999-09-30 23:42 UTC (permalink / raw)
To: cygwin
How do I interupt a large screen dump, when I have jobs in background, without
killing the background jobs? Ctrl-c kills everything, sometimes even bash.
I just want to stop the screen from scrolling, ie. kill the most recent command
which is dumping to screen.
Thanks in Advance,
Clark Sims
--== Sent via Deja.com http://www.deja.com/ ==--
Share what you know. Learn what you don't.
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 6+ messages in thread
* Interupting screen dump
@ 1999-09-13 12:05 Clark Sims
1999-09-30 23:42 ` Clark Sims
0 siblings, 1 reply; 6+ messages in thread
From: Clark Sims @ 1999-09-13 12:05 UTC (permalink / raw)
To: cygwin AT sourceware.cygnus -dot- com
How do I interupt a large screen dump, when I have jobs in background, without
killing the background jobs? Ctrl-c kills everything, sometimes even bash.
I just want to stop the screen from scrolling, ie. kill the most recent command
which is dumping to screen.
Thanks in Advance,
Clark Sims
--== Sent via Deja.com http://www.deja.com/ ==--
Share what you know. Learn what you don't.
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~1999-09-30 23:42 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1999-09-14 12:28 Interupting screen dump Clark Sims
1999-09-19 16:48 ` Michael Hirmke
1999-09-30 23:42 ` Michael Hirmke
1999-09-30 23:42 ` Clark Sims
-- strict thread matches above, loose matches on Subject: below --
1999-09-13 12:05 Clark Sims
1999-09-30 23:42 ` Clark Sims
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).