A partial section of a terminal line is being shifted down one line #4350

Closed
opened 2026-01-30 23:44:44 +00:00 by claunia · 3 comments
Owner

Originally created by @sc0ttwad3 on GitHub (Oct 8, 2019).

Environment

Windows build number: Microsoft Windows [Version 10.0.18995.1]
Windows Terminal version: source git at: #aa682bfd (origin/master, origin/HEAD) doc: update the path to profiles.json (#3087) [Dustin L. Howett (MSFT)]

Any other software? Ubuntu-18.04_LTS WSL 2

Steps to reproduce

Simply open terminal, then open a new tab using the profile:

"commandline" : "wsl.exe -d Ubuntu-18.04"

Then run $ ls on a directory that has a lot of files (or any command such that the screen displays more then the number of lines your terminal is able show at one time. It may take more than one time, but usually after a couple.

Expected behavior

There should be normal display lines without the shifting of a section of the entry/cursor line down by one line; it should display correctly, like with prior builds.

Actual behavior

At some point, adding lines to the buffer after listing files (or anything else), starting from where the cursor is at, the current line gets shifted down by one line. Then near the end of the line, the remainder of the line is displayed correctly.

Any typing is displayed on the line down and is initially treated as valid input by your shell, but soon, the input line starts being displayed twice, or characters don't show up correctly, and generally becomes visually and functionally almost impossible to use.

I've also confirmed that is not related to any particular shell, commands, or programs. It's how Terminal's display handling of the line that appears to be the problem (no pun intended ;-).

Images attached show this more clearly. The first is simple file listing from zsh. The second is an example in Vim that shows exactly where the shift occurs. The cursor is on the line number that is underlined, but insert characters display on the next line. And the status bar provides clear range of the shift.

It's not .vimrc or any configuration issue in any program or dotfiles, none of those have changed, and vanilla vim and/or nvim show it clearly as well.

terminal-issue-line-display-001

terminal-issue-line-display-002

Originally created by @sc0ttwad3 on GitHub (Oct 8, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: Microsoft Windows [Version 10.0.18995.1] Windows Terminal version: source git at: #aa682bfd (origin/master, origin/HEAD) doc: update the path to profiles.json (#3087) [Dustin L. Howett (MSFT)] Any other software? Ubuntu-18.04_LTS WSL 2 ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> Simply open terminal, then open a new tab using the profile: ```"commandline" : "wsl.exe -d Ubuntu-18.04"``` Then run ```$ ls``` on a directory that has a lot of files (or any command such that the screen displays more then the number of lines your terminal is able show at one time. It may take more than one time, but usually after a couple. # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> There should be normal display lines without the shifting of a section of the entry/cursor line down by one line; it should display correctly, like with prior builds. # Actual behavior <!-- What's actually happening? --> At some point, adding lines to the buffer after listing files (or anything else), starting from where the cursor is at, the current line gets shifted down by one line. Then near the end of the line, the remainder of the line is displayed correctly. Any typing is displayed on the line down and is initially treated as valid input by your shell, but soon, the input line starts being displayed twice, or characters don't show up correctly, and generally becomes visually and functionally almost impossible to use. I've also confirmed that is not related to any particular shell, commands, or programs. It's how Terminal's display handling of the line that appears to be the problem (no pun intended ;-). Images attached show this more clearly. The first is simple file listing from zsh. The second is an example in Vim that shows exactly where the shift occurs. The cursor is on the line number that is underlined, but insert characters display on the next line. And the status bar provides clear range of the shift. It's not .vimrc or any configuration issue in any program or dotfiles, none of those have changed, and vanilla vim and/or nvim show it clearly as well. ![terminal-issue-line-display-001](https://user-images.githubusercontent.com/1682691/66421502-f5a44480-e9d5-11e9-9378-db8bf48744b5.png) ![terminal-issue-line-display-002](https://user-images.githubusercontent.com/1682691/66421503-f5a44480-e9d5-11e9-8f59-1b40240ff679.png)
claunia added the Area-OutputIssue-BugResolution-DuplicateProduct-Terminal labels 2026-01-30 23:44:44 +00:00
Author
Owner

@sc0ttwad3 commented on GitHub (Oct 9, 2019):

Might this be related to other line problems such as the regression with line wrap mentioned in #2924 #3052

@sc0ttwad3 commented on GitHub (Oct 9, 2019): Might this be related to other line problems such as the regression with line wrap mentioned in #2924 #3052
Author
Owner

@DHowett-MSFT commented on GitHub (Oct 10, 2019):

Yeah, this definitely looks like it could be #3052. Can you try after reverting 5d906d9f3e78a467c1914a1b8b6fde92e7d86090?

@DHowett-MSFT commented on GitHub (Oct 10, 2019): Yeah, this definitely looks like it could be #3052. Can you try after reverting 5d906d9f3e78a467c1914a1b8b6fde92e7d86090?
Author
Owner

@ghost commented on GitHub (Oct 11, 2019):

This issue has been marked as duplicate and has not had any activity for 1 day. It will be closed for housekeeping purposes.

@ghost commented on GitHub (Oct 11, 2019): This issue has been marked as duplicate and has not had any activity for **1 day**. It will be closed for housekeeping purposes.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#4350