Yes Samuel, I am sure, I just tried it now, and it's been a couple of Cygwin
restarts since last time.
I type a command "g geo" which runs 3 scripts deep to accomplish TGZipping,
FTPing and then SSHing as part of file upload process. During that time
(which happens during FTPing, the longest process) i type another command "g
answers" <enter>
When "g geo" completes I even press <enter> (again), but nothing is present
to take action, my up-key history confirms that indeed "g answers" never
registered as a command, even though it echoed as I originally typed.
It could be the 3 levels deep script mechanism that's losing the input, but
i believe that a regular Unix/Linux would keep the info present and execute
the new command upon first one's completion.
This is not the first time it happened, it's 100% consistent to fail.
-Robert
From: Samuel Thibault <[EMAIL PROTECTED]>
To: cygwin@cygwin.com
Subject: Re: "type ahead" bug with cygwin
Date: Sat, 10 Dec 2005 11:15:09 +0100
Robert Body, le Fri 09 Dec 2005 20:01:49 -0700, a écrit :
> During an ftp session, when the shell was tied up for 15 minutes, I
typed
> something, and of course it was echoed, but when the ftp session
completed,
> the commands I typed were lost, no action was taken.
Mmm, are you sure?
There is a little bug indeed, in that they aren't echoed on the next
prompt, but if you type one character more, you'll see all of them (the
previously typed and the one just typed) appear.
Regards,
Samuel
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
