Text is not being rendered properly while running Emacs on WSL #526

Closed
opened 2026-01-30 21:54:22 +00:00 by claunia · 4 comments
Owner

Originally created by @utsavgupta on GitHub (Jan 19, 2019).

Originally assigned to: @zadjii-msft on GitHub.

  • Your Windows build number: 10.0.17763.253

  • What you're doing and what's happening: After upgrading to this version of Windows, Emacs seems to have been broken. The text is not being rendered correctly. Kindly have a look at the minibuffer in the attached screenshot. This issue was reproducible on command line, cmder, and hyperjs.

emacs-wsl

Originally created by @utsavgupta on GitHub (Jan 19, 2019). Originally assigned to: @zadjii-msft on GitHub. * Your Windows build number: 10.0.17763.253 * What you're doing and what's happening: After upgrading to this version of Windows, Emacs seems to have been broken. The text is not being rendered correctly. Kindly have a look at the minibuffer in the attached screenshot. This issue was reproducible on command line, cmder, and hyperjs. ![emacs-wsl](https://user-images.githubusercontent.com/291183/51427220-44793680-1c1b-11e9-8425-3283627a92bb.png)
claunia added the Product-ConhostArea-RenderingResolution-Duplicate labels 2026-01-30 21:54:22 +00:00
Author
Owner

@miniksa commented on GitHub (Jan 22, 2019):

@zadjii-msft, this feels like #283. Can you confirm?

@miniksa commented on GitHub (Jan 22, 2019): @zadjii-msft, this feels like #283. Can you confirm?
Author
Owner

@zadjii-msft commented on GitHub (Jan 22, 2019):

I'd be fairly confident that issue is the same as this one, though I'm not totally sure what emacs is supposed to look like here, only that it's "not correct".

@utsavgupta can you give me exact keypresses (and other needed repro steps) to get into the state you're seeing the buggy rendering, so I can confirm it's fixed in Insiders?

@zadjii-msft commented on GitHub (Jan 22, 2019): I'd be fairly confident that issue is the same as this one, though I'm not totally sure what emacs is supposed to look like here, only that it's "not correct". @utsavgupta can you give me exact keypresses (and other needed repro steps) to get into the state you're seeing the buggy rendering, so I can confirm it's fixed in Insiders?
Author
Owner

@utsavgupta commented on GitHub (Jan 22, 2019):

@zadjii-msft Yes I can confirm that it is the same #283. Not correct as in the cursor keeps jumping as shown in the GIF attached with the the related issue. Can you please tell me when will the fix be available ?

Thanks.

@utsavgupta commented on GitHub (Jan 22, 2019): @zadjii-msft Yes I can confirm that it is the same #283. Not correct as in the cursor keeps jumping as shown in the GIF attached with the the related issue. Can you please tell me when will the fix be available ? Thanks.
Author
Owner

@zadjii-msft commented on GitHub (Jan 22, 2019):

Thanks for confirming it's the same as the other issue, I'll close this one as a dupe.

As per the other thread:

This is fixed in Insiders 18309 and higher.

@zadjii-msft commented on GitHub (Jan 22, 2019): Thanks for confirming it's the same as the other issue, I'll close this one as a dupe. As per the other thread: > This is fixed in Insiders 18309 and higher.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#526