Re: bash-completion, tab and ambiguous globs
On 2016-02-18, The Wanderer <wanderer@fastmail.fm> wrote:
>
> I'm not sure I understand. How is this different from basic tab
> completion, as opposed to the programmable completion which is provided
> via the bash-completion package and is being discussed in this thread?
>
> I wouldn't want to get by without tab completion either, but
> programmable completion as I've seen it implemented in packages provided
> by Debian seems to break some behaviors in the built-in tab completion
> on which I had come to rely, so I always turn it off on my machines.
>
I think we're confused. I don't know what "programmable completion" is
and kind of thought you were discussing what I call "tab completion,"
although I had some nagging doubts (which prevented me from chiming in
to say that I liked "it"--meaning tab completion).
So what is the difference, because a cursory examination of the web yields
no light on the matter?
Oh, I get it now:
curty@einstein:~$ apt-cache search bash-completion
<snip>
Description: programmable completion for the bash shell
bash completion extends bash's standard completion behavior to achieve
complex command lines with just a few keystrokes. This project was
conceived to produce programmable completion routines for the most
common Linux/UNIX commands, reducing the amount of typing sysadmins
and programmers need to do on a daily basis.
--
Hypertext--or should I say the ideology of hypertext?--is ultrademocratic and
so entirely in harmony with the demagogic appeals to cultural democracy that
accompany (and distract one’s attention from) the ever-tightening grip of plutocratic
capitalism. - Susan Sontag
Reply to: