Re: Bug, or someone wanna explain to me why this is a POSIX feature?
From:
Davide Brini
Subject:
Re: Bug, or someone wanna explain to me why this is a POSIX feature?
Date:
Mon, 8 Aug 2011 21:40:39 +0200
User-agent:
On Mon, 8 Aug 2011 21:14:50 +0200, Davide Brini <dave_br@gmx.com> wrote:
> In fact, you could do the same thing with
>
> foo() { # hit tab here
>
> and I'm sure you wouldn't consider that an empty line.
I have to take that back: it looks like bash treats the above differently
depending on whether enter was pressed or not:
foo() { # hit tab here
Display all 2138 possibilities? (y or n)
foo() { # hit enter here
> # hit tab here
Display all 112 possibilities? (y or n)
The latter only attemps completion from names in the current directory.
On the other hand, with no_empty_cmd_completion set, no completion at all is
attempted in the first case, while the second case still attempts completion
from local names.
--
D.