When autocompleting files starting with a . the first matches appear to be fuzzy rather than exact matches:
Environment
apple darwin21.0 /bin/zsh zsh zsh-5.8.1-0-g1a490c7
/Users/same/.antidote/functions/antidote-load:21
/Users/same/.antidote/functions/_antidote_main:23
/Users/same/.antidote/functions/antidote:48
/Users/same/.zshrc:72
5b0073d (grafted, HEAD -> main, origin/main, origin/HEAD) Check that `$ZSH_COMPDUMP` file can be read
As per the above shell session, when completing regular filenames, exact prefixes match first as you'd expect, but in the second example when I'm trying to autocomplete dotfiles, when starting with .z I get autosuggestions with .fzf.zsh as the first match rather than with .zhistory as the first match like I'd expect and like I get with regular files
This is intentional. When you type .thing, Autocomplete will match *.thing*, so you can easily get a list of all *.thing files even when there are .thing* files present.
When autocompleting files starting with a . the first matches appear to be fuzzy rather than exact matches:
Environment
Steps to reproduce
As per the above shell session, when completing regular filenames, exact prefixes match first as you'd expect, but in the second example when I'm trying to autocomplete dotfiles, when starting with
.z
I get autosuggestions with.fzf.zsh
as the first match rather than with.zhistory
as the first match like I'd expect and like I get with regular files