[Pkg-zsh-devel] Bug#898619: zsh autocompletion does not deal gracefully with upgrades in the background
Philipp Kern
pkern at debian.org
Mon May 14 11:35:17 BST 2018
Package: zsh-common
Version: 5.5.1-1
When zsh is upgraded behind the scenes, running shells will fail to
autocomplete. When you press <tab> you end up with this spam and no
completion:
_setup:8: failed to load module `zsh/complist':
/usr/lib/x86_64-linux-gnu/zsh/5.4.2/zsh/complist.so: cannot open shared
object file: No such file or directory
_main_complete:112: failed to load module `zsh/complist':
/usr/lib/x86_64-linux-gnu/zsh/5.4.2/zsh/complist.so: cannot open shared
object file: No such file or directory
_main_complete:116: failed to load module `zsh/complist':
/usr/lib/x86_64-linux-gnu/zsh/5.4.2/zsh/complist.so: cannot open shared
object file: No such file or directory
_tags:36: failed to load module `zsh/computil':
/usr/lib/x86_64-linux-gnu/zsh/5.4.2/zsh/computil.so: cannot open shared
object file: No such file or directory
_tags:55: failed to load module `zsh/computil':
/usr/lib/x86_64-linux-gnu/zsh/5.4.2/zsh/computil.so: cannot open shared
object file: No such file or directory
[...]
My gut feeling is that this is because I did not autocomplete in the old
shell yet but now the module is gone. At least with a new shell
complist.so is only in /proc/$$/maps after an attempted completion.
Would it be possible to make sure that the autocompletion system loads
the module on startup rather than on-demand? Is there a drawback to this
approach?
Kind regards and thanks
Philipp Kern
More information about the Pkg-zsh-devel
mailing list