Bug Report: Unintended text updating #2881

Closed
opened 2026-01-30 23:07:51 +00:00 by claunia · 5 comments
Owner

Originally created by @RosalesJ on GitHub (Jul 22, 2019).

Environment

Windows build number: 18362.239
Windows Terminal version: Latest from the microsoft store

Steps to reproduce

Open an application like ranger and browse around.

Expected behavior

Only the intended text updates.

Actual behavior

The intended area updates, but other areas update too garbling the UI.

Ranger:

Emacs:

Originally created by @RosalesJ on GitHub (Jul 22, 2019). # Environment ```none Windows build number: 18362.239 Windows Terminal version: Latest from the microsoft store ``` # Steps to reproduce Open an application like ranger and browse around. # Expected behavior Only the intended text updates. # Actual behavior The intended area updates, but other areas update too garbling the UI. ### Ranger: ![](https://user-images.githubusercontent.com/17154302/61557588-9ec04c00-aa32-11e9-9b91-121f911e5734.gif) ### Emacs: ![](https://user-images.githubusercontent.com/17154302/61557851-4f2e5000-aa33-11e9-9dd9-4ec77a5cb756.gif)
claunia added the Product-ConhostIssue-BugArea-VTNeeds-Tag-FixResolution-No-Repro labels 2026-01-30 23:07:51 +00:00
Author
Owner

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

What distro are you running, and could you share the output of infocmp?

EDIT: Also, does this repro with just the terminal, or does it also repro when you launch wsl directly (in conhost.exe)?

@zadjii-msft commented on GitHub (Jul 22, 2019): What distro are you running, and could you share the output of `infocmp`? EDIT: Also, does this repro with just the terminal, or does it also repro when you launch wsl directly (in conhost.exe)?
Author
Owner

@RosalesJ commented on GitHub (Jul 24, 2019):

I'm running Debian. Here's the ouptut of infocmp: output.txt.
At the time the issue was with the terminal only, it worked fine on both wsl.exe and conhost.exe. However when I tried to replicate the issue again today I'm no longer able to replicate it on windows temrinal. Maybe a restart had something to do with it.

@RosalesJ commented on GitHub (Jul 24, 2019): I'm running Debian. Here's the ouptut of ```infocmp```: [output.txt](https://github.com/microsoft/terminal/files/3426851/output.txt). At the time the issue was with the terminal only, it worked fine on both ```wsl.exe``` and ```conhost.exe```. However when I tried to replicate the issue again today I'm no longer able to replicate it on windows temrinal. Maybe a restart had something to do with it.
Author
Owner

@ghost commented on GitHub (Jul 26, 2019):

I've had some issues with emacs in the last 24 hours. I had three erc buffers open and my terminal rendering was way off. It printed a newline character but jumped to the beginning of the terminal emulator on the left side and not to the middle of the buffer.

My guess is that terminal/conhost2 has a special case in which a newline will always jump to the beginning of the terminal emmulator line and not to the beginning of the multiplexed terminal line.

In terms of newline windows terminal should always default to the ansi compliant way of moving the cursor and printing.

Furthermore, some programs have different issues with ansi-compliance. It is important to prioritize them from most used to least.

Vim and emacs are some of these. They need the terminal to be rendered absolutely properly because of the insane style of text editing they both do.

The best program to look to in terms of ansi compliant terminals is probably tmux. tmux it not a terminal emmulator per se but it gets everything right in terms of how it renders things.

@ghost commented on GitHub (Jul 26, 2019): I've had some issues with emacs in the last 24 hours. I had three erc buffers open and my terminal rendering was way off. It printed a newline character but jumped to the beginning of the terminal emulator on the left side and not to the middle of the buffer. My guess is that terminal/conhost2 has a special case in which a newline will always jump to the beginning of the terminal emmulator line and not to the beginning of the multiplexed terminal line. In terms of newline windows terminal should always default to the ansi compliant way of moving the cursor and printing. Furthermore, some programs have different issues with ansi-compliance. It is important to prioritize them from most used to least. Vim and emacs are some of these. They need the terminal to be rendered absolutely properly because of the insane style of text editing they both do. The best program to look to in terms of ansi compliant terminals is probably tmux. tmux it not a terminal emmulator per se but it gets everything right in terms of how it renders things.
Author
Owner

@miniksa commented on GitHub (Aug 1, 2019):

The OP issue is no longer reproducing. Closing.

@miniksa commented on GitHub (Aug 1, 2019): The OP issue is no longer reproducing. Closing.
Author
Owner

@zadjii-msft commented on GitHub (Aug 1, 2019):

For the record, there is another issue tracking the emacs issue - #1474 is probably the issue you're describing.

@zadjii-msft commented on GitHub (Aug 1, 2019): For the record, there is another issue tracking the emacs issue - #1474 is _probably_ the issue you're describing.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#2881