zsh-autocomplete: Cursor position incorrect when "unambiguous" substring is inserted
zsh-autocomplete
version: 3f938bb7b4e36c05fcae172360c20c9dfa6e7bb5- Zsh version: zsh-5.8-0-g77d203f
- Framework: none
- Plugin manager: none
$ zstyle ':autocomplete:tab:*' insert-unambiguous yes
$ source path/to/zsh-autocomplete.plugin.zsh
When insert-unambiguous
is set and non-alphanumerical characters in the file names suggested, all similar parts are inserted upon the <TAB>.
touch qwe-123-rty qwe-456-rty
file q<TAB> -> file qwe--rty
In the example above, since 123
and 456
are the only different parts of the file names, only those are excluded from what is inserted.
file q<TAB>1<TAB>
# should make
file qwe-
file qwe-123-rty
# but actually makes
file qwe--rty
file qwe--rty1
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 20 (8 by maintainers)
Commits related to this issue
- Preserve `compstate[unambiguous_cursor]` Also, if `insert-unambiguous`, highlight all `unambiguous` substrings, instead of just the first one. Fixes issue #177. — committed to marlonrichert/zsh-autocomplete by marlonrichert 3 years ago
- Make initial matcher less greedy Fixes the second part of issue #177. — committed to marlonrichert/zsh-autocomplete by marlonrichert 3 years ago
I agree. The only problem is i deleted all cache file and unless i missed any cache file, i t shouldn’t happen. Anyhow the problem is fixed, everything is good, the plugin is ready to go 😄