Homebrew-core: Neovim 0.4.2 spits out odd stderr messages

Created on 16 Sep 2019 · 9Comments · Source: Homebrew/homebrew-core

Please note we will close your issue without comment if you delete, do not read or do not fill out the issue checklist below and provide ALL the requested information. If you repeatedly fail to use the issue template, we will block you from ever submitting issues to Homebrew again.

[x] are reporting a bug others will be able to reproduce and not asking a question or requesting software. If you're not sure or want to ask a question do so on our Discourse: https://discourse.brew.sh. To get software added or changed in Homebrew please file a Pull Request
[x] have a problem with brew install (or upgrade, reinstall) a single, Homebrew/homebrew-core formula (not cask) on macOS? If it's a general brew problem please file this issue at Homebrew/brew: https://github.com/Homebrew/brew/issues/new/choose. If it's a Linux problem please file this issue at https://github.com/Homebrew/linuxbrew-core/issues/new/choose. If it's a brew cask problem please file this issue at https://github.com/Homebrew/homebrew-cask/issues/new/choose. If it's a tap (e.g. Homebrew/homebrew-php) problem please file this issue at the tap.
[x] ran brew update and can still reproduce the problem?
[x] ran brew doctor, fixed all issues and can still reproduce the problem?
[x] ran brew gist-logs <formula> (where <formula> is the name of the formula that failed) and included the output link?
[x] if brew gist-logs didn't work: ran brew config and brew doctor and included their output with your issue?

To help us debug your issue please explain:

What you were trying to do (and why)
Upgrade neovim to 0.4.x, now that 0.4.2 is released.
What happened (include command output)
When running Neovim commands that involved opening a new "split" from a full-screen buffer (like editing a file that fills the screen, then opening :Termdebug), messages like this get dumped into a seemingly-random place on the screen until a Ctrl-L terminal force-redraw is issued:

resize_buffer[0]: start oldrow=0 newrow=17
  Copying oldrow=0 to newrow=17
  Ran out of content to fill screen; we should pop scrollback 16 rows
  Ran out of content to fill screen; we should move 1 rows from 17 to 0
resize_buffer[1]: start oldrow=0 newrow=17
  Copying oldrow=0 to newrow=17
  Ran out of content to fill screen; we should pop scrollback 16 rows
  Ran out of content to fill screen; we should move 1 rows from 17 to 0

Running nvim 2>/dev/null as the command to launch neovim prevents this, suggesting that the messages are supposed to be sent to stderr. When using binaries obtained directly from Neovim's own "releases" page, this behavior does not occur.

What you expected to happen
The behavior should be the same as with binaries obtained from Neovim's releases page (no stderr messages appearing at random spots)
Step-by-step reproduction instructions (by running brew install commands)
brew install neovim
nvim some-file-that-will-fill-the-screen
In neovim, :packadd termdebug
In neovim :Termdebug
The stderr messages will appear:

outdated

Source

spencerwi

👍4 🎉1

Most helpful comment

@fxcoudert Yep, I did brew reinstall neovim and it updated to libvterm 0.1.1 and all is working correctly now.

kule on 17 Sep 2019

👍9

All 9 comments

I have also observed this, specifically when using fzf-vim's :Files command. As the OP points out, starting neovim with 2> /dev/null prevents the issue.