[Bashburn-info] Fw: Dodgy BUG

[Nick W. <ni...@li...>]

Begin forwarded message:

Date: Fri, 26 Sep 2008 07:33:17 +0100
From: Nick Warne <ni...@li...>
To: "Steven W. Orr" <st...@sy...>
Cc: bashburn <bas...@li...>
Subject: Re: [Bashburn-info] Dodgy BUG


On Thu, 25 Sep 2008 21:32:04 -0400 (EDT)
"Steven W. Orr" <st...@sy...> wrote:

> =>> As it sits now, it has nothingh to do with bb.
> =>
> =>OK.  Is/could it be a problem though?  Is there no way to catch the
> =>escape key?
> =>
> =>I mean, who would press escape key 3 or 4 times other than a moron
> like =>me :-)
> 
> I'm actually slightly intrigued  by this because I don't see where
> the definition is. The bash man page gives all of the function
> definitions and all of their default bindings. None of the default
> bindings correspond to M-<ESC>. (BTW, to activate it, you don't need
> to hit it three or four times. Exactly two will do it. Or hold the
> Alt key while hitting escape.)
> 
> Intrigued, but not intrigued enough to chase it. ;-)

OK, I found out what this is - file name completion.

The same issue happens in BB if you hit the TAB key twice.  Basically,
as there is no file name specified, the command (cleverly) asks if you
want to see all the files.

Nick
-- 
Free Software Foundation Associate Member 5508

-- 
Free Software Foundation Associate Member 5508