[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 w
On 16 Jul, To: [EMAIL PROTECTED] wrote:
> But if you hit TAB twice in quick succession, you'll find that no input
> appears (again), and that while you can use CTRL-C to get a fresh
> prompt, input no longer works in the rxvt window. You have to kill the
> window - it has become useless.
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.
If you then type, input is working again.
But if you hit TAB twice in quick succession, you'll find that
3 matches
Mail list logo