Moving the cursor on the screen breaks 2-cell characters #1008

Open
opened 2026-01-30 22:13:52 +00:00 by claunia · 6 comments
Owner

Originally created by @ghost on GitHub (May 12, 2019).

The lower left area of the window from the lower left of the cursor, the two-cell character is broken.
It is difficult to establish this condition in the console window. As an example, upload Vim's free cursor mode ":set virtualedit=all".

capt

Originally created by @ghost on GitHub (May 12, 2019). The lower left area of the window from the lower left of the cursor, the two-cell character is broken. It is difficult to establish this condition in the console window. As an example, upload Vim's free cursor mode ":set virtualedit=all". ![capt](https://user-images.githubusercontent.com/44701315/57586783-d47a1d80-7535-11e9-8388-591976a10639.gif)
claunia added the Product-ConhostArea-RenderingIssue-BugPriority-2 labels 2026-01-30 22:13:52 +00:00
Author
Owner

@ghost commented on GitHub (May 12, 2019):

I made a mistake on the issue. Close.

@ghost commented on GitHub (May 12, 2019): I made a mistake on the issue. Close.
Author
Owner

@ghost commented on GitHub (May 12, 2019):

Hmm? URI redirected? Reopen it.

@ghost commented on GitHub (May 12, 2019): Hmm? URI redirected? Reopen it.
Author
Owner

@zadjii-msft commented on GitHub (May 13, 2019):

@DHowett-MSFT Didn't you see something like this before, but with breaking ligatures? I feel like there's an internal bug tracking this...

EDIT: Though, now I'm seeing this is conhost, not Terminal, so this is probably GDI related, if it's anything.

@zadjii-msft commented on GitHub (May 13, 2019): @DHowett-MSFT Didn't you see something like this before, but with breaking ligatures? I feel like there's an internal bug tracking this... EDIT: Though, now I'm seeing this is conhost, not Terminal, so this is probably GDI related, if it's anything.
Author
Owner

@DHowett-MSFT commented on GitHub (May 13, 2019):

Right, that was a different issue.
@ntak What version of Windows is this?

@DHowett-MSFT commented on GitHub (May 13, 2019): Right, that was a different issue. @ntak What version of Windows is this?
Author
Owner

@ghost commented on GitHub (May 14, 2019):

Windows 10 Pro Insider Preview
Build 18895.rs_prerelease.190507-2033.

It has been occurring since about when Skip ahead joined the Fast ring.
Did not raise a problem for a long time, I misplaced?

I think you already know that basic reporting has been delayed. I'm sorry.

@ghost commented on GitHub (May 14, 2019): Windows 10 Pro Insider Preview Build 18895.rs_prerelease.190507-2033. It has been occurring since about when Skip ahead joined the Fast ring. Did not raise a problem for a long time, I misplaced? I think you already know that basic reporting has been delayed. I'm sorry.
Author
Owner

@ghost commented on GitHub (Sep 27, 2019):

With SetConsoleCursorPosition(), it appears that the cursor first moves in the Y direction and then moves in the X direction.
As the Y axis moves, the right half of the two-cell character at that coordinate collapses.

In the video in this issue, every time the cursor moves to the right, Vim displays the “character of key pressed” near the bottom right of the screen, so the cursor moves to the bottom right.

@ghost commented on GitHub (Sep 27, 2019): With SetConsoleCursorPosition(), it appears that the cursor first moves in the Y direction and then moves in the X direction. As the Y axis moves, the right half of the two-cell character at that coordinate collapses. In the video in this issue, every time the cursor moves to the right, Vim displays the “character of key pressed” near the bottom right of the screen, so the cursor moves to the bottom right.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#1008