VonHeikemen/fine-cmdline.nvim

BUG: freezes vim with neovim nigthly on windows

Pandademic opened this issue · 3 comments

Pandademic commented

if you type nothing escape , vim will be frozen

VonHeikemen commented

It should be fixed now (55bd7f0).

I think is a neovim bug, I was calling <C-x><C-z> to stop a pending failed completion but that <C-z> was freezing the terminal. That should not happen, it works fine in 0.6.1 but is broken on nightly.

Anyway, I found another method so this bug should not happen anymore.

Edit:
You should definitely report this in the neovim repository. <C-z> is not working properly. We got two bugs here,

  1. <C-x><C-z> should not try to suspend the neovim process,
  2. <C-z> doesn't suspend the process in a proper way, it's freezing the terminal.

I don't use windows as my daily driver, and I don't use neovim nightly. So I would not be able to test a solution when they find one.

  • 👍1
Pandademic commented

reported in the neovim repo

VonHeikemen commented

So it turns out the freezing part of the bug is because windows can't properly restore a suspended process. And I believe the keys <C-x><C-z> were being send to the window below the input, and that was causing neovim to try to suspend. This is no longer the case, the plugin doesn't try to call <C-x><C-z> when the input closes.

If anyone wants to make sure this doesn't happen again remap <C-x><C-z> to <NOP> in normal mode.

With vimscript.

nnoremap <C-x><C-z> <NOP>

Or lua.

vim.api.nvim_set_keymap('n', '<C-x><C-z>', '<NOP>', {noremap = true})