Filter tasks with in bash tab-complete sample

[slimslenderslacks]

The .bashrc example could tab-complete task names if we filter
tasks using the current arg.

[borkdude]

what is bb-util?

[slimslenderslacks]

oops :)

[slimslenderslacks]

bb-util is a wrapper script (for running bb.edns in other directories). Sorry about that.

[borkdude]

My bash is not so good. Can you explain in lay man terms what this change means and how the behavior changes?

[slimslenderslacks]

In the new version, if you have 3 tasks (atask1, atask2, and btask1), and you type bb <tab>, you'll still see

12:56 $ bb
atask1       atask2    btask1

but then if you type bb a<tab>, you'll see the options reduced to two

12:56 $ bb a
atask1       atask2

and if you type bb b<tab> it should just auto-complete the whole btask1

So that compgen command is filtering the list of task names based on the current partially typed argument.

[slimslenderslacks]

I think ${COMP_WORDS[COMP_CWORD]} will always give you the last, potentially partially typed, argument on the command line.

[slimslenderslacks]

In a sense, I guess this is letting bash filter the set of tasks based on what you've partially typed and if you've typed enough to just auto-complete the word, then it completes the typing for you.
Not sure whether the other non-bash examples do the already.

[borkdude]

Neat! I'll try it locally.

[slimslenderslacks]

Another option could be to pass ${COMP_WORDS[COMP_CWORD]} to bb tasks to let bb filter the tasks. If the tasks were to one day support parameter metadata, you could auto-complete --param-names and even run param-values validators using I guess.