On 6/26/20 12:42 AM, Jan Kratochvil wrote:
On Fri, 26 Jun 2020 03:31:10 +0200, Samuel Sieb wrote:
> But regardless, that's something to fix in the dnf bash completion scripts,
> not a reason to completely disable completion as the earlier poster said.
TL;DR it regresses the original bash completion feature.
This will be always a catch up play. To make it working each completion script
would need to be part of the package it is implementing completion for.
Additionally it would need to be integrated into the program's commandline
parsing as otherwise it will never be 100% matching. There were efforts to
I have no idea what you're talking about. The bash completion scripts
are generally supplied by the package that they are for:
# rpm -qf /usr/share/bash-completion/completions/dnf
I have shown just 'dnf' but if you really want I can find
arbitrary number of
other such programs and bugs where the completion script implements things
differently than the program itself.
The dnf one works fine. But if you don't like how specific ones work,
then file bugs.
This is why IMHO bash-completion is only an experimental unfinished
and it should not be the default.
It's a very useful feature for most people. If you don't like it, then
Btw, in the case of dnf or similar situations, you can force file
completion by pressing ALT-/