vim --version:
VIM - Vi IMproved 9.2 (2026 Feb 14, compiled Mar 23 2026 19:02:24)
Included patches: 1-204
mini.vim:
set nocompatible nowrap linebreak norm 30Ix norm yyp call prop_type_add("foo", {}) call prop_add(1, 5, #{text:"foo: ",type:"foo"}) call prop_add(2, 5, #{text:"bar: ",type:"foo"})
reproduction steps:
vim -u mini.vim"foo: "<c-v> jExpected to highlight visual text, but actually did not
When set nolinebreak, the behavior meets expectations
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
This seems to affect unprintable characters (displayed as <xxxx> etc.) as well. With 'linebreak', only the first cell of unprintable characters at the end of a blockwise Visual selection is highlighted.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
Ref: https://groups.google.com/g/vim_dev/c/FUjx06xTM60/
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
There also seems to be another bug. When a blockwise Visual selection comes after 'linebreak', the characters changed by operators doesn't match the displayed Visual selection. Fixing that may be a bit more complicated.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()