column number wrong when utf-8 double-wide character is substituted after conceal about vim

[zeertzjq]

Related #4687

[girishji]

Related #4687

It appears that is a different issue, related to supporting string as substitute (instead of single character).

The issue I reported is a bug. Column numbers (based on byte count) should not change when some character is concealed or substituted. What happens on screen (how many cells a character occupies) should not affect byte position in a string/line.

[zeertzjq]

I don't think byte position is wrong. If you press ga you can see that the cursor is actually on the n after using cursor(1, 12), not the i.

[girishji]

I don't think byte position is wrong. If you press ga you can see that the cursor is actually on the n after using cursor(1, 12), not the i.

Good point, but the cursor (visual character on screen) is still on i. So there is a mismatch between where the cursor is visually on the screen vs what Vim thinks (according to ga). Now try to open a popup window at n (using what wincol() reports), it would be incorrectly shifted one cell to the left because of this mismatch.

You can also move the cursor to the right (across the hidden character) and watch column numbers increment on the ruler. They'd be wrong too.

[girishji]

Searching for a string also shows the bug. Say the cursor is on A, and If you search /nn, the cursor lands on in (of beg|in|ning) instead of nn. Line is set as At the beばinninば .

This bug is probably not of much interest since the scenario of substituting single-cell wide char with double-wide char is unlikely. Maybe of importance to non-English users.

[ronin49]

@girishji
i think we will not do it
conceal is just a graphic thing so all vim's mechanics don't care about it
those vim doesn't see what you see using conceal