In #15442, we introduce the -o default argument which allows bash completion to fall back to the default completion when there are no suggestions. In dbuenzli/cmdliner#275 it was pointed out that this collapses two semantically distinct cases: Falling back vs no completions.
Even once we add completion support for every command and argument, this will mean when there are no suggestions we end up suggesting files.
We should therefore keep in mind that -o default is temporary and should be removed in the future once the completion support is improved. An alternative in the meantime is to improve the script so that we can distinguish the two cases, but I don't see a way to do that at the moment.
In #15442, we introduce the
-o defaultargument which allows bash completion to fall back to the default completion when there are no suggestions. In dbuenzli/cmdliner#275 it was pointed out that this collapses two semantically distinct cases: Falling back vs no completions.Even once we add completion support for every command and argument, this will mean when there are no suggestions we end up suggesting files.
We should therefore keep in mind that
-o defaultis temporary and should be removed in the future once the completion support is improved. An alternative in the meantime is to improve the script so that we can distinguish the two cases, but I don't see a way to do that at the moment.