[vim/vim] those code in new sms or spk option seems missed something? (Issue #11282)

Shane-XB-Qian

unread,

Oct 4, 2022, 10:51:14 AM10/4/22

to vim/vim, Subscribed

Steps to reproduce

1, vim --clean foo.md
2, vnew
3, move j/k some

// the screen became mess after so..

the foo.md:
// something like this, i do not understand those 'words' meaning, supposed no sensitive words

<kbd>[<img title="Limba Română" alt="Limba Română" src="foo" width="22">](translations/README.ro.md)</kbd>

<kbd>[<img title="မြန်မာ" alt="မြန်မာ" src="foo" width="22">](translations/README.mm_unicode.md)</kbd>

<kbd>[<img title="Македонски" alt="Македонски" src="foo" width="22">](translations/README.mk.md)</kbd>

<kbd>[<img title="Español de México" alt="Español de México" src="foo" width="22">](translations/README.mx.md)</kbd>

<kbd>[<img title="Bahasa Melayu / بهاس ملايو‎ / Malay" alt="Bahasa Melayu / بهاس ملايو‎ / Malay" src="foo" width="22">](translations/README.my.md)</kbd>

<kbd>[<img title="Dutch" alt="Dutch" src="foo" width="22">](translations/README.nl.md)</kbd>

Expected behaviour

no stray chars

Version of Vim

v9.0.656

Environment

linux
xfce-term

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.

Shane-XB-Qian

unread,

Oct 4, 2022, 10:59:03 AM10/4/22

to vim/vim, Subscribed

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

Bram Moolenaar

unread,

Oct 4, 2022, 5:43:56 PM10/4/22

to vim/vim, Subscribed

I cannot follow these reproduction steps. Can you check if patch 9.0.0662 has fixed this?
If not, please try to give a simpler example.

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

Shane-XB-Qian

unread,

Oct 4, 2022, 11:14:05 PM10/4/22

to vim/vim, Subscribed

how about this:

vim --clean foo.md -c 'exe "normal ggVGyppp" | vnew | wincmd l | rightbelow vsp | wincmd h | normal ggjjjjjjjjjjjjjjjjjjjjkkkkkjjjjjjjjkkkkkkkkkkk'

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

Bram Moolenaar

unread,

Oct 5, 2022, 11:53:21 AM10/5/22

to vim/vim, Subscribed

I can reproduce a problem in xterm with just one line and a vertical split.
The problem appears to be that Vim considers character 4156 (0x103c) to be a composing character, but the terminal doesn't.
The text then takes more space and overflows to the next line.

I think this is a mistake in the unicode table, "spacing combining" take up space, thus should not be considered "composing" characters.

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

Shane-XB-Qian

unread,

Oct 5, 2022, 12:07:15 PM10/5/22

to vim/vim, Subscribed

tried with xterm(372), even set nowrap (i was thinking that was a matter), but looks worse..

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

Shane-XB-Qian

unread,

Oct 5, 2022, 12:10:06 PM10/5/22

to vim/vim, Subscribed

except english and chinese, no idea those words meaning, but i do guess that was the matter too
but not sure which one.. :-) out of my knowledge... :-(

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

Bram Moolenaar

unread,

Oct 5, 2022, 1:03:43 PM10/5/22

to vim/vim, Subscribed

Closed #11282 as completed via 7beaf6a.

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

Bram Moolenaar

unread,

Oct 5, 2022, 1:04:53 PM10/5/22

to vim/vim, Subscribed

Fixed with patch 9.0.0666
That character is from Myanmar.

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

Bram Moolenaar

unread,

Oct 5, 2022, 1:04:55 PM10/5/22

to vim/vim, Subscribed

Closed #11282 as completed.

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

Shane-XB-Qian

unread,

Oct 5, 2022, 1:48:26 PM10/5/22

to vim/vim, Subscribed

seems partially fixed, but:

// seems worse:
if running within a gun-screen

// seems not fixed:
if file name is those chars, (and tabline or stl was set to show its filename)

#10523
// seems related, though maybe more about was a gnu-screen issue.

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

Bram Moolenaar

unread,

Oct 5, 2022, 4:09:19 PM10/5/22

to vim/vim, Subscribed

The "screen" program indeed makes this look bad. Since it only happens with "screen" I can only assume this is a problem in "screen". tmux works fine.

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

Shane-XB-Qian

unread,

Oct 5, 2022, 4:50:59 PM10/5/22

to vim/vim, Subscribed

but looks this made the file which having multiple width chars in filename (would be set to display at tabline or stl, specially had long name) and/or content be more easier displaying with stray chars.
// had to wait Gun-screen fix this? but seems that's a very inactive proj.

--
shane.xb.qian