Fix origin-mode cursor positioning#6
Open
jchristn wants to merge 2 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This fixes DEC origin-mode cursor positioning with scroll regions:
DECSTBM/CSI t;b rnow moves the cursor to home after setting the scroll region.CUP/HVP(CSI row;col H/f) now treat row coordinates as relative to the scroll region whenDECOM/ origin mode is enabled.VPA/CSI row dnow applies the same origin-mode row translation.Why
Terminal UIs that reserve a bottom prompt/status row commonly set a scroll region for the output area and use origin-relative cursor addressing. Without these semantics, content can be written to the wrong absolute rows and preserved into scrollback incorrectly.
This is a core emulator behavior fix only. It intentionally does not include any host-rendering, PTY, ConPTY, or Termrig-specific compatibility shims.
Validation
dotnet test src\XTerm.NET.slnx --no-restoreThe test run still reports the existing compiler warnings about
EscapeSequenceParser.DcsandTerminal.HyperlinkChanged; this PR did not introduce new warnings.