![]() ++ compgen -f -X '!*.Initializing glyph cache. + COMPREPLY=($(compgen -f -X "$e" +o plusdirs - $c)) + case "$(complete -p $ 2> /dev/null)" in Run “set -x” and then “zypper TAB” and post output, may be there will be something obvious. As I already said - it is up to you to debug what happens. When people do not understand which process is in charge at which moment they will never understand why they run into trouble here. I am so pedantic about this, because I see connections with the misunderstanding that using the wild cards as defined in the zypper documentation must not be treated with care and shielded off from the shell by quoting (notwithstanding the fact that the man page warns for this in several places). ![]() And it is bash that then must decide that this apparenty in a command that has zypper the first word and thus no normal bash file name completion is needed, but the zypper helper must be asked. But it is the bash process that sees your input and your TAB hitting. ![]() I do not know how it is implemented nor if the packet/product bash-completion is involved. Completion for zypper does not use bash-completion at all and does not require it. It is not required to use bash completion, although some projects use its helpers and so require it. (But I do not see a zypplib related one in this list made on Leap 15.1).īash-completion is project that provides helpers to create your own completion function as well as completion functions for “common” programs. | zabbix-bash-completion | Zabbix bash completion | package I+ | youtube-dl-bash-completion | Bash completion for youtube-dl | package | you-get-bash-completion | Bash completion for you-get | package | vagrant-bash-completion | Vagrant bash autocompletion | package | systemd-mini-bash-completion | Bash completion support for systemd | package I | systemd-bash-completion | Bash completion support for systemd | package | subversion-bash-completion | Bash Completion for subversion | package | salt-bash-completion | Bash Completion for salt | package | ripgrep-bash-completion | Bash Completion for ripgrep | package | restic-bash-completion | Bash Completion for restic | package | rclone-bash-completion | Bash Completion for rclone | package | python3-buku-bash-completion | Bash completion for python3-buku | package | pyenv-bash-completion | Bash completion for pyenv | package I | pulseaudio-bash-completion | PulseAudio Bash completion | package | patool-bash-completion | Bash Completion for patool | package | mpv-bash-completion | Bash Completion for mpv | package I | mbimcli-bash-completion | Bash completion for mbimcli | package | lxd-bash-completion | Bash Completion for lxd | package | lxc-bash-completion | Bash Completion for lxc | package | libvirt-bash-completion | Bash completion script | package | ldc-bash-completion | LDC Bash completion | package | kopano-bash-completion | bash TAB completion for Kopano Core command-line utilities | package | kmod-bash-completion | Bash completion routines for the kmod utilities | package | iproute2-bash-completion | Bash completion for iproute | package | imgp-bash-completion | Bash Completion for imgp | package | herbstluftwm-bash-completion | Bash completion for herbstluftwm | package | flameshot-bash-completion | Bash Completion for flameshot | package | fd-bash-completion | Bash Completion for fd | package | docker-bash-completion | Bash Completion for docker | package | chocolate-doom-bash-completion | Chocolate Doom command line completion support for bash | package | calf-bash-completion | Bash completion for calf | package | cabal-install-bash-completion | Bash completion for cabal-install | package | bspwm-bash-completion | Bash Completion for bspwm | package | borgbackup-bash-completion | Bash Completion for borgbackup | package I | bash-completion | Programmable Completion for Bash | package | alacritty-bash-completion | Bash Completion for alacritty | package I | ModemManager-bash-completion | Bash completion for nmcli | package There are a lot: boven:~ # zypper se '*bash-completion' It must of course use some information about which packages exist,Īnd apparently bash can do context dependent completetion and one can provide plug-ins for the different contexts. Why not? it is bash you are typing in and only bash can do that completetion. However bash-completion doesn’t seem to be the right package.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |