[EMAIL PROTECTED] wrote: > If at a fresh bash prompt in an rxvt window (non-X) you type a TAB, > nothing happens, and no input from the keyboard appears thereafter, > until you use CTRL-C to interrupt whatever has blocked.
Putting shopt -s no_empty_cmd_completion in your .bash_profile is a good way to avoid this. I don't know what's up with your other comment about weird interaction between multiple presses of TAB and CTRL-C, but I would tend to guess it's not a Cygwin issue. Robert -- 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/
