Prev: Virtualbox and kernel 2.6.30.5 (Slackware64)
Next: Montreal wins Grey Cup 28-27
From: Jim Diamond on 29 Nov 2009 20:19
On 2009-11-29 at 06:21 AST, root <NoEMail(a)home.org> wrote:
> I do almost all my work using the command line and I
> have noticed a difference in type-ahead: when I enter
> the next command while a previous command is still
> running the new command is ignored. The version of
> bash is the same as in 12.2, I have not re-compiled
> the particular applications I am using, so the difference
> must come from the change in the kernel?
>
> Any way I can revert to the old behavior?

I see the same behaviour... sometimes. I haven't been able to figure
out yet what the conditions are, and until your message I was
beginning to wonder whether it was just me. After I saw your message
I did a few more tests, and in my case it happens if the previous
command terminates with an error, my shell executes a command which
seems to eat type-ahead.

I don't recall this happening in 12.2, I'll have to reboot into 12.2
and give it a try.

I use tcsh for my shell, so I doubt it is a bash-ism in your case,
unless you have something analogous set up.

Jim
First  |  Prev  | 
Pages: 1 2
Prev: Virtualbox and kernel 2.6.30.5 (Slackware64)
Next: Montreal wins Grey Cup 28-27