Re: [PATCH] Simple update to bash completions to prevent unbound variable errors.

Ted Pavlic [off-list ref] writes:

quoted

quoted

+# __gitcomp_1 requires 2 arguments

... and $1 and $2 mean?

No clue. Patches are welcome.

To be absolutely honest, I think people with "set -u" in their interactive
environment are sick.  Bourne shells have been substituting unset
variables to empty string for eons, and this is not _my_ itch to scratch.

It seems to be yours, though, and I was merely trying to help.