Re: Command history problem?

Re: Command history problem?

[Earnie Boyd]

--- Dan Herron <herron@informatik.uni-hamburg.de> wrote:
--8<--
> But, if I make the mistake of hitting the up-arrow key _while a command
> is executing_, when the command finishes, the system thrashes the hard
> drive for about 20 seconds to a minute, before finally dumping some
> control characters on the prompt line. Only then do I get my system back.
> (And I have, of course, tried to hit Control-C, etc, which probably only
> makes things worse in this case.)
> 
> Does anybody know what causes this? It's terribly frustrating, since I'm
> the type who executes command A, then command B, then command C, then A
> again..., and so I frequently have to sit there as my computer turns
> temporarily into an expensive paper-weight.
--8<--

What version of cygwin are you using?  I've noticed this event also but only
when bringing a window into focus and hitting the up-arrow before the system
has completed the focus instrutctions.  I'm using stock b20.1.

What I do to speed up the exit of this is to hit a series of ^C^Z^C.
===
"Earnie Boyd" < mailto:earnie_boyd@yahoo.com >
CYGWIN RELATED HELP:
 DOCUMENTATION: < http://sourceware.cygnus.com/cygwin/docs.html >
       DLLHELP: < http://www.xraylith.wisc.edu/~khan/software/gnu-win32/ >
ARCHIVE SEARCH: < http://www.delorie.com/archives/ > OR
                < http://www.eGroups.com/list/gnu-win32/ >
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Command history problem?

[Dan Herron]

At 07:15 AM 4/16/99 -0700, Earnie Boyd wrote:
>What version of cygwin are you using?  I've noticed this event also but only
>when bringing a window into focus and hitting the up-arrow before the system
>has completed the focus instrutctions.  I'm using stock b20.1.

I'm using a pretty-much stock version of 20.1. I vaguely remember
changing one of the DLL's (from Sergei's site, I think.) I don't think it
was anything pushing the bleeding-edge (I don't spend too much time
tinkering with the cygwin stuff), but it is NOT the exact stock version.

>What I do to speed up the exit of this is to hit a series of ^C^Z^C.

Yeah, I try that, and it seems to be that the system thrashes even harder
for every key you press...

Dan


Daniel Herron             Universitaet Hamburg / Fachbereich Informatik
phone: (49) 40 / 428 83 2519           AB Natuerlichsprachliche Systeme
fax:   (49) 40 / 428 83 2515                     Vogt-Koelln-Strasse 30
herron@informatik.uni-hamburg.de                        D-22527 Hamburg

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Command history problem?

[John Mullee]

Dan Herron wrote:
> Yeah, I try that, and it seems to be that the system thrashes even harder
> for every key you press...

FWIW, I experienced this with cygwin v 19, and also on redhat linux
5.0 (but not nearly as severe). So I guess it's a bash thing.

john

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Command history problem?

[John Mullee]

Dan Herron wrote:
> Yeah, I try that, and it seems to be that the system thrashes even harder
> for every key you press...

FWIW, I experienced this with cygwin v 19, and also on redhat linux
5.0 (but not nearly as severe). So I guess it's a bash thing.

john

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Command history problem?

[Dan Herron]

At 07:15 AM 4/16/99 -0700, Earnie Boyd wrote:
>What version of cygwin are you using?  I've noticed this event also but only
>when bringing a window into focus and hitting the up-arrow before the system
>has completed the focus instrutctions.  I'm using stock b20.1.

I'm using a pretty-much stock version of 20.1. I vaguely remember
changing one of the DLL's (from Sergei's site, I think.) I don't think it
was anything pushing the bleeding-edge (I don't spend too much time
tinkering with the cygwin stuff), but it is NOT the exact stock version.

>What I do to speed up the exit of this is to hit a series of ^C^Z^C.

Yeah, I try that, and it seems to be that the system thrashes even harder
for every key you press...

Dan


Daniel Herron             Universitaet Hamburg / Fachbereich Informatik
phone: (49) 40 / 428 83 2519           AB Natuerlichsprachliche Systeme
fax:   (49) 40 / 428 83 2515                     Vogt-Koelln-Strasse 30
herron@informatik.uni-hamburg.de                        D-22527 Hamburg

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Command history problem?

[Earnie Boyd]

--- Dan Herron <herron@informatik.uni-hamburg.de> wrote:
--8<--
> But, if I make the mistake of hitting the up-arrow key _while a command
> is executing_, when the command finishes, the system thrashes the hard
> drive for about 20 seconds to a minute, before finally dumping some
> control characters on the prompt line. Only then do I get my system back.
> (And I have, of course, tried to hit Control-C, etc, which probably only
> makes things worse in this case.)
> 
> Does anybody know what causes this? It's terribly frustrating, since I'm
> the type who executes command A, then command B, then command C, then A
> again..., and so I frequently have to sit there as my computer turns
> temporarily into an expensive paper-weight.
--8<--

What version of cygwin are you using?  I've noticed this event also but only
when bringing a window into focus and hitting the up-arrow before the system
has completed the focus instrutctions.  I'm using stock b20.1.

What I do to speed up the exit of this is to hit a series of ^C^Z^C.
===
"Earnie Boyd" < mailto:earnie_boyd@yahoo.com >
CYGWIN RELATED HELP:
 DOCUMENTATION: < http://sourceware.cygnus.com/cygwin/docs.html >
       DLLHELP: < http://www.xraylith.wisc.edu/~khan/software/gnu-win32/ >
ARCHIVE SEARCH: < http://www.delorie.com/archives/ > OR
                < http://www.eGroups.com/list/gnu-win32/ >
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Command history problem?

[Dan Herron]

Hi,

Just like in a 'normal' bash shell, I can scroll up and down in my
command history with the arrow keys (with the current CygWin setup,
running on NT, using the normal command window on NT, not rxvt or
anything else.)

But, if I make the mistake of hitting the up-arrow key _while a command
is executing_, when the command finishes, the system thrashes the hard
drive for about 20 seconds to a minute, before finally dumping some
control characters on the prompt line. Only then do I get my system back.
(And I have, of course, tried to hit Control-C, etc, which probably only
makes things worse in this case.)

Does anybody know what causes this? It's terribly frustrating, since I'm
the type who executes command A, then command B, then command C, then A
again..., and so I frequently have to sit there as my computer turns
temporarily into an expensive paper-weight.

thanks for any ideas,
Dan


Daniel Herron             Universitaet Hamburg / Fachbereich Informatik
phone: (49) 40 / 428 83 2519           AB Natuerlichsprachliche Systeme
fax:   (49) 40 / 428 83 2515                     Vogt-Koelln-Strasse 30
herron@informatik.uni-hamburg.de                        D-22527 Hamburg

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Command history problem?

[Dan Herron]

Hi,

Just like in a 'normal' bash shell, I can scroll up and down in my
command history with the arrow keys (with the current CygWin setup,
running on NT, using the normal command window on NT, not rxvt or
anything else.)

But, if I make the mistake of hitting the up-arrow key _while a command
is executing_, when the command finishes, the system thrashes the hard
drive for about 20 seconds to a minute, before finally dumping some
control characters on the prompt line. Only then do I get my system back.
(And I have, of course, tried to hit Control-C, etc, which probably only
makes things worse in this case.)

Does anybody know what causes this? It's terribly frustrating, since I'm
the type who executes command A, then command B, then command C, then A
again..., and so I frequently have to sit there as my computer turns
temporarily into an expensive paper-weight.

thanks for any ideas,
Dan


Daniel Herron             Universitaet Hamburg / Fachbereich Informatik
phone: (49) 40 / 428 83 2519           AB Natuerlichsprachliche Systeme
fax:   (49) 40 / 428 83 2515                     Vogt-Koelln-Strasse 30
herron@informatik.uni-hamburg.de                        D-22527 Hamburg

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com