It seems that while true do ... end and vim.fn.getchar will cause some problem with lazy.nvim?

[nyngwang]

Let me explain the title:

1. I used to have a simple VimScript plugin https://github.com/simeji/winresizer, but it doesn't work after I migrated to lazy.nvim from packer.nvim
2. I thought there is some problem with VimScript, so I did some rewrite/refactor and put the result into https://github.com/nyngwang/NeoMove. (The repo is very small and simple, so it should be very easy to debug. I did try to debug it but I cannot find the reason...)
3. To reproduce what's wrong, here is the config of NeoMove:

   use {
     'nyngwang/NeoMove', enabled = true,
     config = function ()
       require('neo-move').setup {
         finish_with_escape = true,
       }
     end
   }

4. Now if I call require('neo-move').moveCommands.right(), then there is no problem: it will swap the buf at the current window with the one at the right-hand side window.
5. Buf If I use the command NeoMove, i.e. I will enter the while-loop(https://github.com/nyngwang/NeoMove/blob/main/lua/neo-move.lua#L65-L87), then some very strange behavior will be shown: vim.fn.getchar() seems to get many "ghost keys"(I didn't press enter, but the loop detected it.)

Finally, I'm not sure whether this is indeed a problem with lazy.nvim, so please don't take this discussion offensive... I'm also considering this might be related to some upstream commits.

[folke]

Sorry, but this has 100% nothing to do with lazy...

[nyngwang]

Thanks for your immediate reply. I just confirmed that this can also be reproduced with packer.nvim. I have reported this to winresizer.vim, and sorry for posting it here...!