vscode-neovim: bug: Undo pops up Output window

Check the following:

  • I have checked the behavior after setting “vscode-neovim.neovimClean” in VSCode settings.
  • I have read the vscode-neovim docs.
  • I have searched existing issues.

Neovim version (nvim -v)

0.9.4

Operating system/version

Ubuntu 22.04

Describe the bug

In the latest release v1.71.1 clicking on u in normal mode brings the output window of vs code into focus. When i downgraded to v1.71.0 the problem is not seen.

Steps To Reproduce

Upgrade to v1.71.1 and make changes. and the click on u in normal mode. If the output is out of focus , it comes into focus

Expected Behavior

The output window does should not come to focus like previous version.

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 1
  • Comments: 16

Most upvoted comments

In my case, even cmdheight=3 wasn’t enough when using VimSneak. This would happen when I searched through VimSneak for a non-present string (eg. no), in which case the message manager would encounter output from VimSneak like this ['>', '>n', '>no', 'not found']. This output has length 4 which exceeded cmdheight=3 and would therefore display the output.

So at least for me, the quick fix was (Lua)

vim.o.cmdheight=4

Though I can’t tell all the implications right now as this number already feels quite high and arbitrary.

I am using neovim 0.10 version and setting the below at the beginning of my init.lua helped me to resolve this

if vim.g.vscode then
  cmdheight = 1 -- This is the extra config I added
  return
end

-- rest of the lua config

I’m using pounce.nvim and no matter what I set cmdheight to, the output window still appears. Is this because pounce can add output in new lines indefinitely? Can I somehow suppress the output of a specific plugin?

cmdheight

I just have it in my init.vim

set cmdheight=3

I left a comment there saying it’s related to https://github.com/spf13/spf13-vim/issues/540