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

Add support for the DECALN escape sequence #5134

New Issue
Open
opened 2026-01-31 00:05:52 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 00:05:52 +00:00
Owner
Copy Link

Originally created by @j4james on GitHub (Nov 23, 2019).

Description of the new feature/enhancement

The DECALN escape sequence produces a test pattern that was used for adjusting screen alignment on the original VT terminals. I don't think it's of any real use in a modern terminal emulator, but it's needed to pass many of the tests in the Vttest suite.

This is how the control is defined in the VT510 Programmer Information manual:

This control function fills the complete screen area with a test pattern used for adjusting screen alignment ... DECALN sets the margins to the extremes of the page, and moves the cursor to the home position.

The VT100 and VT220 manuals define the fill pattern as an uppercase E, although later manuals are less specific, and the DEC STD 070 manual just says it's "implementation defined".

The DOC STD 070 manual does give a bit more detail about what should be reset though. In addition to clearing the margins, and moving the cursor position to home, it says the origin mode and rendition attributes should also be reset (although the latter was not actually true of the VT100).

As for the color attributes, if we're following the XTerm behaviour, then the colors should not be reset. However, note that the the test pattern should still be rendered with the default foreground and background colors, and not the active colors.

Proposed technical implementation details

This will require a new method to be added to the ITermDispatch interface, which can then be called from OutputStateMachineEngine::ActionEscDispatch when the intermediate char is # and the final char is 8.

The method itself can mostly be implemented with existing ConGetSet and AdaptDispatch calls. The only tricky bit is we'll need the new PrivateFillRegion API proposed in PR #3100 in order to fill the screen with the correct colors.

I've got a PR for this prepared already, but it's dependent on #3100 being approved first, otherwise I'll need to come up with another plan.

Originally created by @j4james on GitHub (Nov 23, 2019). # Description of the new feature/enhancement The [`DECALN`](https://vt100.net/docs/vt510-rm/DECALN.html) escape sequence produces a test pattern that was used for adjusting screen alignment on the original VT terminals. I don't think it's of any real use in a modern terminal emulator, but it's needed to pass many of the tests in the [Vttest](https://invisible-island.net/vttest/) suite. This is how the control is defined in the VT510 _Programmer Information_ manual: > This control function fills the complete screen area with a test pattern used for adjusting screen alignment ... DECALN sets the margins to the extremes of the page, and moves the cursor to the home position. The VT100 and VT220 manuals define the fill pattern as an uppercase E, although later manuals are less specific, and the _DEC STD 070_ manual just says it's "implementation defined". The _DOC STD 070_ manual does give a bit more detail about what should be reset though. In addition to clearing the margins, and moving the cursor position to home, it says the origin mode and rendition attributes should also be reset (although the latter was not actually true of the VT100). As for the color attributes, if we're following the XTerm behaviour, then the colors should not be reset. However, note that the the test pattern should still be rendered with the default foreground and background colors, and not the active colors. # Proposed technical implementation details This will require a new method to be added to the `ITermDispatch` interface, which can then be called from `OutputStateMachineEngine::ActionEscDispatch` when the intermediate char is `#` and the final char is `8`. The method itself can mostly be implemented with existing `ConGetSet` and `AdaptDispatch` calls. The only tricky bit is we'll need the new `PrivateFillRegion` API proposed in PR #3100 in order to fill the screen with the correct colors. I've got a PR for this prepared already, but it's dependent on #3100 being approved first, otherwise I'll need to come up with another plan.
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 Area-VT Issue-Task Priority-3 Product-Conhost Resolution-Fix-Committed
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#5134
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?