Closed Aetherall closed 3 years ago
Bisection revealed the faulty commit: [2a838cb6ef05c9912569cf9f899087f02ecf0c87] Reintroduce fully fuzzy matching as a fallback
Tried a naive fix but did not succeed ( just switched from fish, zsh is new for me )
I'm switching back to the parent of the faulty commit c7426be9e859e049747114818fa9107ecebe11b9
I will keep posting symptoms to help diagnose if i stubble upon another one :)
Sorry, but I'm not at all sure what you're trying to report here. What should I do to see the bug and what exactly am I supposed to see?
Sorry I've not been really precise
I noticed a strange behavior when moving my cursor backward when correcting a curl command.
The behavior was the insertion of ^D
characters when navigating across a header argument (-H)
I was able to reproduce it when typing ls - H - H
in my terminal, and I noticed that when typing the second -H
, zsh tried to look for possible matches within $PATH, and a key press on the arrow key inserted the key char into the prompt input
I tried on a clean Ubuntu docker image, with only zsh, git, and zsh-autocomplete, no zsh config
I will post a gif this weekend demonstrating the issue
Closing this. If you can give me a working test case, I will reopen it.
zsh-autocomplete
version: 76ff7df91c9ec436d8f1c5b519d91fc426eae801From there you can see two strange behaviours For them to show up, type this command manually
ls -H -H
The unwanted behaviour is the not-found prompt, which make navigating difficult ( curl command edition etc)