vscode-neovim: bug: Weird virtual characters

Did you check docs and existing issues?

  • I have read all the vscode-neovim docs
  • I have searched the existing issues of vscode-neovim
  • I can reproduce the issue with an empty init.vim/init.lua and no other vscode extensions (when applicable)

Neovim version (nvim -v)

NVIM v0.9.1

Operating system/version

Pop!_OS 22.04 LTS x86_64

Describe the bug

when I enter visual mode and select some lines I find some weird characters at the end of some lines.

as you see in the following picture

bug

NOTE I did not face this bug in version 0.3.2

Steps To Reproduce

  1. go to visual mode
  2. just select some lines
  3. sometimes these characters appear and sometimes not, so try step 1 and 2 until you find them

Expected Behavior

What I expect to find that when I go to visual mode and select some lines, I do not find these weird characters

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Reactions: 19
  • Comments: 18 (1 by maintainers)

Most upvoted comments

Still happening image

I’m using: NVIM v0.10.0 Build type: Release LuaJIT 2.1.1713484068 VSCode 1.91.1

Can reproduce on both Mac Sonoma and Win 11. I use lazy.nvim and only have vim-sneak as a plugin.

This is still very much happening in macOS - not sure if extension is to blame or if Cursor is. In any case, the repro is trivial, pretty much every time I do a /<...> search and navigate with n I get the ghost characters everywhere.

Image

I’ve been able to re-create with PHP, JS, and a txt file. Was not able to re-create in Rust, Python, Perl, C, or JSON. I don’t have any Go code handy to test on.

The txt file has ANSI terminal escapes in it though (results from grep --color=always intended to be played back with less -R), so I don’t know how much of the issue with this file is due to vscode/nvim trying to parse through those.

I have noticed that I struggle to re-create this in my smaller files ( x < 100 lines), though I’m not sure how much of this is luck. I also found that restarting vscode can cause this issue to go away for a bit.