Since update history-beginning-search-backward not working

[artfulrobot]

Describe the bug

I just updated, (from c335940), and now my up-arrow behaviour is (a) different and (b) seems broken. My up-arrow key is bound to history-beginning-search-backward .

Before the update I could type ls hit ↑ and it would complete the line with the latest matching ls... from my history, repeated presses of ↑ went further throught the history lines starting with ls.

After the update two things happen

1. I get a !351 which means nothing to me on the command line, and a huge one item per line list of history matches. (or it seems that using the dev branch I get the actual command (nicer) but still get the massive list.)

2. If I select an entry with Enter I don't always get what I selected, as shown here where I select ls -la and get just ls:

I would prefer not to get the menu as it scrolls everything else off screen and requires pressing Enter.

I suspect (2) is something to do with my other plugins, and I note your README says

Note for Oh My Zsh, Prezto and Zimfw users: zsh-autocomplete works best if you use it instead of your framework's supplied completion module.

Which suggests I need to disable something in omz to use this but I don't know what/how.

Desktop

• OS + distribution: Debian 10
• Zsh version: 5.7.1
• Plugin version: master and also tried c1f1560

[marlonrichert]

I'm working on a better version of the history menu. Once it's ready, I'll push it to master, but you can already try it out on the dev branch.

[artfulrobot]

My experience on the dev branch is that selection is still broken - hit up a few times, hit Enter on selected item and the completion goes away.

[artfulrobot]

The last working version for me is fd16c5e

Actually it's 005da66 - it was commit c1f1560 that seemed to break things for me.

[artfulrobot]

@marlonrichert Hey these changes seem to have fixed things for me, thank you so much 👍

[artfulrobot]

...Although I notice that zstyle ':autocomplete:tab:*' completion cycle seems broken now - should I open a separate issue for that?

e.g. I type lsTab and it inserts the first entry instead.

[marlonrichert]

It's because I'm working on #82. Read the Readme in the dev branch. The syntax has changed.