Neovide: Tab completion popup window in command mode has disappeared in newest neovim + neovide

[Hubro]

Describe the bug

Tab completing stuff in command mode doesn't bring up a popup window in Neovide. In nvim in the terminal, it works as expected.

To Reproduce
Steps to reproduce the behavior:

1. Open Neovide
2. Type :let g:neovide_
3. Press Tab a bunch of times
4. No popup appears

Expected behavior

I expected a popup to appear like in nvim.

Screenshots

Neovide:

Neovim:

Desktop (please complete the following information):

• OS: Arch Linux
• Neovide Version: main branch (2fc74f83ca2ac167df8607ed2e0f29122ec5f167)
• Neovim Version master branch (v0.5.0-dev+1459-g384f9870f)

Please run neovide --log and paste the contents of the .log file here:

https://gist.githubusercontent.com/Hubro/d53c69b04bb71035accc021790ffe1db/raw/066de6b886f69fa1bac5642660787bee5bfcb8f8/neovide_rCURRENT.log

[Kethku]

Do you have multgrid enabled? This works on my machine

[Hubro]

Do you have multgrid enabled? This works on my machine

Yep, it's enabled. I'm smooth scrolling in the same window. :thinking:

I'm running the same versions on my laptop and desktop, and the window is not popping up on either of them, so it's not a system configuration issue. The laptop has an Intel i7 with integrated graphics and intel vulkan drivers, the desktop has a Ryzen 5950X with a Radeon 5700 XT, RADV vulkan drivers.

[Hubro]

I just tried running with -u NONE to launch a completely vanilla nvim, still doesn't work. So it's not the fault of my plugins or vim config.

[Kethku]

Let me update to latest latest and see

[Kethku]

Ok you're absolutely right. That means in the last week or so a regression was introduced upstream.

[Hubro]

Ok you're absolutely right. That means in the last week or so a regression was introduced upstream.

Ok, glad you were able to reproduce it. Are you on top of reporting it? I have no idea where I would even start :sweat_smile:

[Kethku]

Well first step, I'm trying to find which commits look suspicious by reading commit messages. I don't have neovim building on my machine atm, so this may be a little difficult to triangulate where the problem is.

Once thats figured out I can then either determine if it was a bug fix and I was just programming to the bug or if its really a regression.

Do you have any ideas how we might find the problem commit upstream?

[Kethku]

https://github.com/neovim/neovim/pull/14137 This one looks suspicious. At least it has to do with the PUM which I believe is the completion menu used here.

[Hubro]

neovim/neovim#14137 This one looks suspicious. At least it has to do with the PUM which I believe is the completion menu used here.

I can probably build neovim in a jiffy, I'll test if that commit is the perpetrator.

[Kethku]

Nah I figured it out. Fix incoming

[Hubro]

Nah I figured it out. Fix incoming

Haha awesome :grin: Were you indeed relying on a bug that got fixed?

[Kethku]

Yeah funny enough this issue had been happening in reverse, so a couple of days ago I rammed my head through the wall and made a "fix" that just programmed to upstream behavior. Turns out the bug had already been fixed and I was just on an old version of master.

I just pushed a fix. Thanks for the report!

[Hubro]

Yeah funny enough this issue had been happening in reverse, so a couple of days ago I rammed my head through the wall and made a "fix" that just programmed to upstream behavior. Turns out the bug had already been fixed and I was just on an old version of master.

I just pushed a fix. Thanks for the report!

Awesome! Thanks for the quickest fix I've ever seen! :grin:

[Kethku]

We aim to please ;)