If I use the <tab> completion while typing in command mode, the full results listing will display above the commandline for just a moment, but then almost immediately disappear. If I hit tab again, the results will display, but only with the single line listing within the statusline, not in the "full" menu that showed before.
I've tried using :profile but after typing :colo <tab> to bring up the menu and then completing the profile commands, the resulting file is blank.
:profile start ~/profile.log | :profile func * | :profile file *
<do stuff>
:profile pause
:noautocmd qall!
Is there anything else I can use to see what may be happening in the background?
I also tried :verbose au, but that output doesn't seem related. (Or maybe it does show what I'm after and I'm not reading it properly?)
options.lua
wildmenu = true,
wildmode = "list:longest,list:full",
This does not happen when launching with nvim -u NONE so I suspect it's likely something on my end, either related to a plugin or to something in my config/keymaps/etc.
nvim -u NONE -c "set wildmenu | set wildmode=list:longest,list:full"and seems to be working fine: i.imgur.com/pJjhTkp.gifcmap,cnoremap, or autocommands that could be the real culprit. If that doesn't work, post a minimal, reproducible example (no plugins and only relevant settings enabled). I wasn't able to replicate this behavior in the latest neovim (v0.8.0-dev-784), by the way.:sourceexecutes commands in a file; you need (Neo)Vim to "forget" all of the current state. It sounds like you found the issue, so I'm going to close this