On Mon, Jan 29, 2024 at 01:51:19PM -0600, David Wright wrote: > On Mon 29 Jan 2024 at 19:31:50 (+0100), Michael Kiermaier wrote: > > Thank you for your responses! After 'complete -r' the problem > > disappears. I should add that I never touched the autocomplete settings. > > No, but you lose your so-called component (2) filtering. > > For me, a better workaround is, when the directory path gets "stuck": > > . Press HOME, > . Type any letter that makes a "wrong" command name (eg aokular), > . Press END, > . Press TAB and carry on using completion for directory/filenames, > . Once you reach the right directory, and if you need filtering, > press HOME DELETE END and you've got filtering back again. > . Obviously press HOME DELETE if you didn't do the previous step. > > > I will submit a bug report for the package bash-completion.
complete -r isn't intended as a workaround. It's intended as a diagnostic step. Seeing the problem go away when completion goes away means that the problem is *in* the completion. Thus, he knows which package to file a bug report against.
