starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Unexpected backspace behaviour in the rightmost column of the screen #195

New Issue
Closed
opened 2026-01-30 21:45:15 +00:00 by claunia · 2 comments
claunia commented 2026-01-30 21:45:15 +00:00
Owner
Copy Link

Originally created by @j4james on GitHub (Mar 15, 2018).

Originally assigned to: @zadjii-msft on GitHub.

  • Your Windows build number:

Microsoft Windows [Version 10.0.16299.248]

  • What you're doing and what's happening:

In older versions of Windows, and DOS, if you output a character in the rightmost column of the screen, the cursor would immediately wrap onto the next line. However, in the new Windows 10 console, the cursor remains where it is after outputting something in the rightmost column - it only wraps onto the next line once you output an additional character. This I assume is intentional behaviour for compatibility with Linux.

What's unexpected, though, is how it behaves when you attempt to move back from this position, either with an ANSI CUB sequence (\033[D) or a backspace. Below are two test cases that move the cursor to the rightmost column, output an x, then attempt to move back one character, before outputting a y.

printf "\033[1000Cx\by\n"
printf "\033[1000Cx\033[Dy\n"

On Linux, both of these sequences result in the characters yx appearing at the end of the line, i.e. both methods move the cursor one column back from the rightmost column when it's in that ambiguous state.

On Windows 10, however, only the CUB sequence produces the yx output. The backspace appears to have no effect, so the y ends up overwriting the x, and you just have the y left at the end of the line.

  • What's wrong / what should be happening instead:

I'd expect the CUB sequence and backspace sequence to behave the same way in this situation, both resulting in yx appearing at the end of the line (the same as Linux).

Originally created by @j4james on GitHub (Mar 15, 2018). Originally assigned to: @zadjii-msft on GitHub. * Your Windows build number: Microsoft Windows [Version 10.0.16299.248] * What you're doing and what's happening: In older versions of Windows, and DOS, if you output a character in the rightmost column of the screen, the cursor would immediately wrap onto the next line. However, in the new Windows 10 console, the cursor remains where it is after outputting something in the rightmost column - it only wraps onto the next line once you output an additional character. This I assume is intentional behaviour for compatibility with Linux. What's unexpected, though, is how it behaves when you attempt to move back from this position, either with an ANSI CUB sequence (`\033[D`) or a backspace. Below are two test cases that move the cursor to the rightmost column, output an `x`, then attempt to move back one character, before outputting a `y`. printf "\033[1000Cx\by\n" printf "\033[1000Cx\033[Dy\n" On Linux, both of these sequences result in the characters `yx` appearing at the end of the line, i.e. both methods move the cursor one column back from the rightmost column when it's in that ambiguous state. On Windows 10, however, only the CUB sequence produces the `yx` output. The backspace appears to have no effect, so the `y` ends up overwriting the `x`, and you just have the `y` left at the end of the line. * What's wrong / what should be happening instead: I'd expect the CUB sequence and backspace sequence to behave the same way in this situation, both resulting in `yx` appearing at the end of the line (the same as Linux).
claunia added the Product-Conhost label 2026-01-30 21:45:15 +00:00
claunia commented 2026-01-30 21:45:16 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 15, 2018):

Huh. I think I know exactly which code handles that. I doubt we considered this particular edge case 😝

I'll file a bug to look at it.

@zadjii-msft commented on GitHub (Mar 15, 2018): Huh. I think I know exactly which code handles that. I doubt we considered this particular _edge_ case 😝 I'll file a bug to look at it.
claunia commented 2026-01-30 21:45:16 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Nov 21, 2018):

It looks like this fix shipped in the 1809 update. Thanks for reporting!

@DHowett-MSFT commented on GitHub (Nov 21, 2018): It looks like this fix shipped in the 1809 update. Thanks for reporting!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Product-Conhost
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#195
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?