zsh-autocomplete: Up arrow key not displaying previously run command

  • zsh-autocomplete version: 6284119
  • Zsh version: zsh-5.8-0-g77d203f
  • Framework: Oh My Zsh
  • Plugin manager: โ€œnoneโ€
 ~/.oh-my-zsh/custom/plugins/zsh-autocomplete  main  > cd $(mktemp -d)                                                                                           
 /var/folders/9t/0pvv38nd4kxff89szytt53mm0000gr/T/tmp.ACv97Ehd > ZDOTDIR=$PWD HOME=$PWD exec zsh -f                                                                  
3c22fb686d64% pwd
/var/folders/9t/0pvv38nd4kxff89szytt53mm0000gr/T/tmp.ACv97Ehd
3c22fb686d64% source /Users/XYZ/.oh-my-zsh/custom/plugins/zsh-autocomplete
3c22fb686d64% source /Users/XYZ/.oh-my-zsh/custom/plugins/zsh-autocomplete/zsh-autocomplete.plugin.zsh
3c22fb686d64%
No suffix alias found.

Pressing the up arrow key after using auto complete to run a command returns the following error instead of typing out the previously run command. But this issue does not occur if I use only zsh-autocomplete.

.autocomplete._main_complete:135: command not found: _autocomplete.history_lines _autocomplete._main_complete.post:11: command not found: _autocomplete.unambiguous

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 22 (12 by maintainers)

Commits related to this issue

Most upvoted comments

I pushed in a potential fix. Please remove compinit from your .zshrc file and try again.

I removed the autoload -U compinit; compinit and opened a new terminal, looks good so far. I was both able to fetch the last command without an error and tab for completion also works.

Itโ€™s probably a caching issue. Next time you run into problem like this, try

% rm $_comp_dumpfile

then restart your terminal. ๐Ÿ™‚

Which is strange since I had just pulled this morning.

Itโ€™s not that strange if you consider I had pushed in new commits just seconds before you filed your issue. ๐Ÿ˜‰

Got it! This is such an amazing plugin. I am recommending it to everyone! ๐Ÿ˜„

I think the git pull fixed this issue. Not getting this issue with all plugins running anymore.