Inconsistent line gap height #6946

Closed
opened 2026-01-31 00:51:13 +00:00 by claunia · 1 comment
Owner

Originally created by @AnuthaDev on GitHub (Mar 18, 2020).

Environment

Windows build number: Microsoft Windows [Version 10.0.18363.535]
Windows Terminal version (if applicable): 0.10.761.0

Steps to reproduce

  1. Open cmd (Doesn't matter if its in terminal or conhost)
  2. Press Ctrl+C 2-3 times.(Note the height of the line gap)
  3. Press Enter.
  4. Press Ctrl+C 2-3 times.(Note the height of the line gap)
  5. Enter some invalid command.(Well, not necessarily invalid)
  6. Press Ctrl+C 2-3 times.(Note the height of the line gap).

Expected behavior

Consistent height of line gap

Actual behavior

Terminal:

image

Conhost:
image

Originally created by @AnuthaDev on GitHub (Mar 18, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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.18363.535] Windows Terminal version (if applicable): 0.10.761.0 ``` # Steps to reproduce 1. Open cmd (Doesn't matter if its in terminal or conhost) 2. Press Ctrl+C 2-3 times.(Note the height of the line gap) 3. Press Enter. 4. Press Ctrl+C 2-3 times.(Note the height of the line gap) 5. Enter some invalid command.(Well, not necessarily invalid) 6. Press Ctrl+C 2-3 times.(Note the height of the line gap). # Expected behavior Consistent height of line gap # Actual behavior Terminal: ![image](https://user-images.githubusercontent.com/36439704/76933537-5a63b380-6913-11ea-9a5d-7ecb9bb411ed.png) Conhost: ![image](https://user-images.githubusercontent.com/36439704/76933370-f214d200-6912-11ea-924c-a6add218550c.png)
claunia added the Needs-Tag-FixResolution-Won't-FixProduct-Cmd.exe labels 2026-01-31 00:51:14 +00:00
Author
Owner

@DHowett-MSFT commented on GitHub (Mar 18, 2020):

Thanks for the report! This is just a minor visual issue in CMD that doesn’t seem to have any impact on its usability, so it doesn’t meet the bar for fixes to CMD. I’d rather not risk destabilizing it since it really exists to maintain legacy compatibility.

Sorry!

@DHowett-MSFT commented on GitHub (Mar 18, 2020): Thanks for the report! This is just a minor visual issue in CMD that doesn’t seem to have any impact on its usability, so it doesn’t meet the bar for fixes to CMD. I’d rather not risk destabilizing it since it really exists to maintain legacy compatibility. Sorry!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#6946