[vim/vim] Window screen gets wrong when a virtual text is placed on 'above' or 'below' on an empty line (Issue #11959)
rickhowe
Steps to reproduce
On the following window:
Run the following script to place '---' above and '+++' below on each line:
let vt = 'test'
call prop_type_delete(vt)
call prop_type_add(vt, {'highlight': 'ToDo'})
for ln in range(1, line('$'))
call prop_add(ln, 0, {'type': vt, 'text': '---', 'text_align': 'above'})
call prop_add(ln, 0, {'type': vt, 'text': '+++', 'text_align': 'below'})
endfor
The empty lines on both line 2 and 4 are gone. Then the line number appears on the virtual text and the cursor appears out of last line 5.
Expected behaviour
The empty lines should be left displayed as well.
Version of Vim
9.0.1291
Environment
Windows 10
Logs and stack traces
No response
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Bram Moolenaar
Closed #11959 as completed via 9d9a20e.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
rickhowe
Thank you for your immediate fixing, but I still see some problem.
- When &list is on, eol ($) does not appear on the empty line but on the "above" virtual lines.
- If we do not use "below" but use "above" only, the screen looks OK, but the cursor can not move to line 3, 4, and 5.
Then &list is set, the screen gets corrupted.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
rickhowe
Thanks again, but I still see another problem.
If text is a single character and draw the "below" virtual line.
Then &list is set, all the virtual lines are gone.
If "above", looks like no problem.
And if "below", the problem happens only if text is 1 or 2 characters.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Bram Moolenaar
I'll have a look at the other problems when I have time.
Note that this issue is already closed, adding more problems to it is confusing.
Next time please open a new issue, with reproduction steps.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Bram Moolenaar
Re-opening for the remaining problem mentioned.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Bram Moolenaar
Reopened #11959.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Christian Brabandt
Closed #11959 as completed via da0c913.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.