With zdharma/fast-syntax-highlighting active, no completion menu shows when removing typed a command without executing and then typing something new. Opening the history menu with the up or down arrow seems to unstuck it.
Issue does not seem to occur with I actually can reproduce it with zsh-users/zsh-syntax-highlighting.zsh-users/zsh-syntax-highlighting as well, just not as consistently.
$ cd $(mktemp -d)
$ ZDOTDIR=$PWD HOME=$PWD zsh -df
% git clone [email protected]:marlonrichert/zsh-autocomplete.git
% source zsh-autocomplete/zsh-autocomplete.plugin.zsh
% git clone [email protected]:zdharma/fast-syntax-highlighting.git
% source fast-syntax-highlighting/fast-syntax-highlighting.plugin.zsh
cd but do not hit enter/return - Autocomplete menu now shows as it shouldbackspacesleep process to stop - Important step because typing immediately after clearing the line will not cause the bugcd again and no autocompletions will show - AKA 'the bug'When zdharma/fast-syntax-highlighting is loaded and I type a command but then remove it without executing, and wait for some time before entering a new command, the completion menu should just display again.
When zdharma/fast-syntax-highlighting is loaded and I type a command but then remove it without executing, and wait for some time before entering a new command, the completion menu does not display.
5.8marlonrichert/zsh-autocomplete: 0de4c97eb77da4a5605a616ccb4053bfce559b06zdharma/fast-syntax-highlighting: a47b5088636c3678c7baa22710d10b0c45bc9265This same problem does not occur when following the reproduction steps but substitute the highlighter with the non-fast alternative See intro.zsh-users/zsh-syntax-highlighting at 62c5575848f1f0a96161243d18497c247c9f52df.
I had the same problem before. But I solved the problem by loading fast-syntax-highlighting before zsh-autocomplete.
Give it a try.
I had the same problem before. But I solved the problem by loading fast-syntax-highlighting before zsh-autocomplete.
Give it a try.
Thanks, tried that earlier but the issue persists. Forgot to mention in the original report 馃槕
@yutakatay @pcjmfranken Does this problem also occur when you use the dev branch?
@marlonrichert Fixed in dev, nice!
Should be fixed now on master with fbb82dfbe1e5d8fe04e8bef2a968b971acdfd5a3
Most helpful comment
Should be fixed now on
masterwith fbb82dfbe1e5d8fe04e8bef2a968b971acdfd5a3