CMD: Typing chars until line break and then back space confuses typing position #5022

Closed
opened 2026-01-31 00:03:09 +00:00 by claunia · 3 comments
Owner

Originally created by @devsko on GitHub (Nov 15, 2019).

Environment

Windows build number: 10.0.18363.476
Windows Terminal version (if applicable): 0.6.2951.0

Any other software?

Steps to reproduce

  • Open cmd
  • Type any chars until line breaks
  • Type Backspace until the cursor gets back to the previous row

Expected behavior

Every Backspace should delete one char

Actual behavior

When cursor changes line there is one additional space to delete and the typing position is off by one afterward.
PS seems to work correctly
Deleting chars with Del seems to work correctly

Originally created by @devsko on GitHub (Nov 15, 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: 10.0.18363.476 Windows Terminal version (if applicable): 0.6.2951.0 Any other software? ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> - Open cmd - Type any chars until line breaks - Type ```Backspace``` until the cursor gets back to the previous row # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> Every ```Backspace``` should delete one char # Actual behavior <!-- What's actually happening? --> When cursor changes line there is one additional space to delete and the typing position is off by one afterward. PS seems to work correctly Deleting chars with ```Del``` seems to work correctly
claunia added the Resolution-Duplicate label 2026-01-31 00:03:09 +00:00
Author
Owner

@VikingScientist commented on GitHub (Nov 15, 2019):

Windows build number: 10.0.18362
Windows Terminal version (if applicable): 0.6.2951.0

Bug appears on my setup as well. Note: it is only a visual bug. Increasing font size up and down again "fixes it": the extra space vanishes and the cursor is in the right place. Looking at the command which is run, then there is no space in this command.

@VikingScientist commented on GitHub (Nov 15, 2019): ``` Windows build number: 10.0.18362 Windows Terminal version (if applicable): 0.6.2951.0 ``` Bug appears on my setup as well. Note: it is only a visual bug. Increasing font size up and down again "fixes it": the extra space vanishes and the cursor is in the right place. Looking at the command which is run, then there is no space in this command.
Author
Owner

@zadjii-msft commented on GitHub (Nov 15, 2019):

Thanks for the bug report! This is actually something that's already been reported, so I'm going to redirect conversation to the original thread.

/dupe #1245

Thanks!

@zadjii-msft commented on GitHub (Nov 15, 2019): Thanks for the bug report! This is actually something that's already been reported, so I'm going to redirect conversation to the original thread. /dupe #1245 Thanks!
Author
Owner

@ghost commented on GitHub (Nov 15, 2019):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Nov 15, 2019): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#5022