On Wed, 2018-03-07 at 21:44 -0300, Gabriel F. T. Gomes wrote:
> While I understand that this patch in launchpad fixes the reported
> behaviour, I don't understand why upstream did not want to accept it.
> Could there be unintended/undesired side-effects?
Uhm.. to be honest I haven't even noticed that upstream doesn't want to
accept it? :-D
At least I think to remember that this wasn't always buggy... it only
happened in <admittedly long ago and I was probably too lazy for years
to investigate&report ^^>.
I cannot really say for sure whether there are undesired side
effects... I mean bash-completion should anyway only be active in
interactive sessions, right? So scripts shouldn't take any harm.
And for interactive sessions (or such who kinda hack a script to behave
like in an interactive one)... people must always expect that such
changes occur in new versions.
> I could definitely apply this to the Debian package, but I want to
> this questioning upstream first. It's been a long time, and maybe
> have a better understanding of the problem, now.
Thanks a lot for taking the effort :-)
What I personally would probably even like more was, if * is just not
completed at all... but completing it only to one "random" match is