On Wed, 7 Dec 2016 07:48:42 -0500, Tom Horsley wrote: > On Wed, 7 Dec 2016 12:39:13 +0100 > Andras Simon wrote: > > > Are you sure about this? It seems to work here with > > bash-completion-2.1-8.20150513git1950590.fc23.noarch > > I suppose they could have fixed it at some point, but > dnf (or maybe it was still yum at the time) was actually > the final straw that led me to track down the existence > of the bash completion nonsense and eradicate it > from my system. > > It also goes rather insane in certain complicated > circumstances involving bash aliases which invoke eval > to generate a command. > > Plus, of course, never having any idea what TAB might > actually do depending on the random characters you have typed > previously is just utterly wrong and against the > natural order of the universe :-). It has messed up multiple commands for me for a long time. Have reported some of them, have opened threads on mailing-lists, but it hasn't lead to anything. $ cd some-srpms-dir $ dnf builddep foo<TAB> $ dnf builddep foo<TAB><TAB> It doesn't complete anything. No matter how often I press TAB. Compared with: $ yum-builddep foo<TAB> It queries the RPM database, which is something I don't want, and only then shows multiple pages of local files and installed packages, asking me to page through them, so I may add refine my completion request. If I uninstall bash-completion package, at least both commands behave the same, and "dnf builddep ..." becomes usable again. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
