Re: bash-completion, tab and ambiguous globs
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, Feb 17, 2016 at 09:57:30AM +0100, Anders Andersson wrote:
> On Tue, Feb 16, 2016 at 11:15 AM, Jean-Baptiste Thomas
> <cau2jeaf1honoq@laposte.net> wrote:
> > In bash, typing, say, "ls x*y" then tab lists all the possible
> > expansions of "x*y" on the next line, then prints the command
> > line anew with "x*y" replaced by longest common stem.
> >
> > With bash-completion installed, "x*y" is summarily replaced by
> > its first match.
>
> Thank you! I just pondered this today, and I remember that it used to
> work much better. Now I at least know the culprit.
>
> Seriously, when does bash-completion actually help someone on the
> command line? The only time I notice it is when a pattern is buggy and
> doesn't let me complete a filename even when it's completely valid.
It can be creepily smart, like knowing the branches in your project
when you do git checkout bla<TAB> or things like that. Not bad.
That said, it always was a bit on the heavy (or overdone) side for my
taste, so I ended ditching it. But I can well understand someone
liking it.
- -- t
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlbEMGsACgkQBcgs9XrR2kb4AgCdFipMv2LE3aoZ3QAEHd5eXxyl
69MAnjf6rg2PMmALYCmBHm0UbKUphG7+
=pmve
-----END PGP SIGNATURE-----
Reply to: