You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Setting extmarks in the on_lines event of nvim_buf_attach for the updated lines results in wrong results when lines are moved via the :m command (e.g. :m .+2). When "moving" the line by cutting and pasting these problems do not occur, so it seems like specifically related to the :m command.
Wrapping the code for clearing the namespace and setting the extmarks into vim.schedule(...) makes it work.
Problem
Setting extmarks in the
on_lines
event ofnvim_buf_attach
for the updated lines results in wrong results when lines are moved via the:m
command (e.g.:m .+2
). When "moving" the line by cutting and pasting these problems do not occur, so it seems like specifically related to the:m
command.Wrapping the code for clearing the namespace and setting the extmarks into
vim.schedule(...)
makes it work.Maybe this is related to #28107
Steps to reproduce
Use the following
minimal.lua
file:nvim -u NONE minimal.lua
minimal.lua
file usingsource %
:m
command (e.g.:m .+3
)Expected behavior
The extmarks are all updated correctly even when using the
:m
commandNeovim version (nvim -v)
0.10.0
Vim (not Nvim) behaves the same?
not applicable
Operating system/version
Ubuntu 20.04.6 LTS
Terminal name/version
GNOME Terminal 3.36.2
$TERM environment variable
xterm-256color
Installation
appimage
The text was updated successfully, but these errors were encountered: