% cd $(mktemp -d)
% git clone --depth 1 -- https://github.com/marlonrichert/zsh-autocomplete.git
Cloning into 'zsh-autocomplete'...
remote: Enumerating objects: 53, done.
remote: Counting objects: 100% (53/53), done.
remote: Compressing objects: 100% (51/51), done.
remote: Total 53 (delta 0), reused 28 (delta 0), pack-reused 0
Receiving objects: 100% (53/53), 1.64 MiB | 4.22 MiB/s, done.
% git clone --depth=1 -- https://github.com/romkatv/powerlevel10k.git
Cloning into 'powerlevel10k'...
remote: Enumerating objects: 92, done.
remote: Counting objects: 100% (92/92), done.
remote: Compressing objects: 100% (75/75), done.
remote: Total 92 (delta 18), reused 75 (delta 13), pack-reused 0
Receiving objects: 100% (92/92), 349.61 KiB | 1.92 MiB/s, done.
Resolving deltas: 100% (18/18), done.
% > .zshrc <<EOF
setopt interactivecomments transientrprompt
PS1='%# '
PS2=
RPS2='%^'
source $PWD/zsh-autocomplete/zsh-autocomplete.plugin.zsh
source $PWD/powerlevel10k/powerlevel10k.zsh-theme
EOF
% env -i HOME=$PWD PATH=$PATH TERM=$TERM ${TERMINFO:+TERMINFO=$TERMINFO} zsh -d
# At this point the config for powerlevel10k will come up. Complete the config and it will drop you to a prompt.
# I did the following answers y y y y 3 1 1 3 2 5 2 3 4 4 1 2 2 y 1 y
% ls
powerlevel10k zsh-autocomplete
% ls
powerlevel10k zsh-autocomplete
% kubectl version
Client Version: v1.29.0
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.25.16-eks-adc7111
WARNING: version difference between client (1.29) and server (1.25) exceeds the supported minor version skew of +/-1
% ls
powerlevel10k zsh-autocomplete
# At this point press the up arrow to bring up the history menu and press up one more time to select
# kubectl version and you will notice the menu mostly disappears. This is due to the fact that selecting the kubectl
# command changes the input to the prompt which in turn triggers the kubecontext plugin in powerlevel10k which
# then redraws the prompt to include the kube context.
Contents of ~autocomplete-log/2024-05-21.log (click to expand)
This also occurs with the aws plugin. It can be worked around by disabling those plugins but I would prefer to be able to use them and autocomplete at the same time.
Environment
Steps to reproduce
Contents of
~autocomplete-log/2024-05-21.log
(click to expand)