Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consecutive win_move_statusline() calls don't work properly after printing multiline message #21014

Closed
zeertzjq opened this issue Nov 9, 2022 · 1 comment · Fixed by #21015
Labels
bug issues reporting wrong behavior ui
Milestone

Comments

@zeertzjq
Copy link
Member

zeertzjq commented Nov 9, 2022

Neovim version (nvim -v)

v0.9.0-dev-284+g0faf007a2

Vim (not Nvim) behaves the same?

No

Operating system/version

Arch Linux

Terminal name/version

kitty 0.26.5

$TERM environment variable

xterm-kitty

Installation

build from repo

How to reproduce the issue

  1. Run nvim --clean
  2. Source the following file:
echo "\n"
call win_move_statusline(0, -4)
call win_move_statusline(0, 4)
  1. Press Enter

Expected behavior

cmdheight is 1

Actual behavior

cmdheight is 4

@zeertzjq zeertzjq added bug issues reporting wrong behavior ui labels Nov 9, 2022
@zeertzjq
Copy link
Member Author

zeertzjq commented Nov 9, 2022

This is related to these lines in message.c:

neovim/src/nvim/message.c

Lines 199 to 204 in 0faf007

if (msg_grid.chars && cmdline_row < msg_grid_pos) {
// TODO(bfredl): this should already be the case, but fails in some
// "batched" executions where compute_cmdrow() use stale positions or
// something.
cmdline_row = msg_grid_pos;
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug issues reporting wrong behavior ui
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant