Bug report: command mode mapping does not work very well for some case. #1136

[kgfly]

local opts = { noremap = true, silent = true }
vim.keymap.set({'c'}, '<c-v>', '<c-r>*', opts)

does not work very well.

Observed:
I yank a dummy string, eg "adsfadsfasdf"
In command mode, I press c-v, tring to paste. I see.

The pasted string is actually there. But the issue is: it is not visible.

I press entry key. It prompted

, which means it has been pasted, but it's invisible.

[akiyosi]

@kgfly
Thanks for reporting the issue.
Could you please let me know what font and colorscheme you are using?

[kgfly]

Thanks for getting back. font/colorscheme do not matter. Just above mini 2 lines can repro the issue. I think this is a common issue for the QT based gui. nvim-qt has similar issue. I reported here: equalsraf/neovim-qt#1136

nvim/neovide do not have this issue.

[akiyosi]

@kgfly
I suspect the issue is caused by the text not fitting within the bounds of the drawing area rectangle. I’ve encountered similar problems before due to this.

In goneovim, layout calculations are based on the width of the “w” glyph of the specified font. Although goneovim expects fonts to be monospaced, we’ve observed that when some monospaced fonts are used in Qt, the width of certain glyphs may vary—either inherently or when the font is rendered in bold—even though they’re supposed to be fixed-width.

That’s why I checked the fonts and colorschemes to help identify the cause.

While nvim-qt and goneovim use different rendering logic, they share the fact that both rely on Qt and base layout calculations on the width of specific glyphs.

nvim-qt uses “W” width: https://github.com/equalsraf/neovim-qt/blob/6c506094f5d0e9663a3a907622d5aef8e19de85f/src/gui/shellwidget/shellwidget.cpp#L116

[kgfly]

Thanks. The color scheme I used is https://github.com/tomasiser/vim-code-dark. Font is: https://www.programmingfonts.org/#hack. JFYI

[akiyosi]

@kgfly
I was able to reproduce this problem.
It seems to be a neovim issue as it reproduces in neovide as well.
I will continue to investigate.

[kgfly]

Thanks.

It seems to be a neovim issue as it reproduces in neovide as well.
->
No, neither for neovide. There is nvim under Windows Termminal.

The string is copied by pressing <c-v>

[akiyosi]

@kgfly
I reproduce this problem with neovide in my Windows environment.
I have confirmed that it is not reproduced in the environment where I run nvim at the command prompt.

[kgfly]

Thanks.

JFYI. This is my neovide on Windows, which does not repro.

The string is copied by pressing <c-v>

[akiyosi]

@kgfly
Hmmm, I wonder if there are any conditions...
By the way, could you tell me what versions of nvim and neovide you use?

[kgfly]

neovide: 0.15.0
nvim: 0.10.4

Thanks

[akiyosi]

@kgfly
After investigating the issue, I believe this is not a bug in the GUI, but expected behavior based on how Neovim is designed to work. I have confirmed the following:

• The Neovim GUI handles UI events from Neovim and performs the drawing process, but when is performed after :cnoremap <silent> <some-keymap> <c-r>* is done, no events are emitted to draw on the command line.

• If :cnoremap <some-keymap> <c-r>* is used (without <silent>), the pasted string is drawn on the command line.

• The same event occurs in other CUI App(e.g. kitty) when <c-n> is mapped instead of <c-v>, and <c-n> is typed on the command line. This may indicate that <c-v> works because it is a function of the terminal application.

[kgfly]

Thanks. Do you have thoughts why neovide works?

[akiyosi]

@kgfly
Neovide might be treating specially, just like terminal applications do.