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

[PR #15782] Modernize CommandHistory and switch to int32 #30738

New Issue
Closed
opened 2026-01-31 09:42:40 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 09:42:40 +00:00
Owner
Copy Link

Original Pull Request: https://github.com/microsoft/terminal/pull/15782

State: closed
Merged: Yes

This commit slightly modernizes CommandHistory by leaning more heavily
on the STL container functionalities. For one, it uses for-range
iterations to loop through _commands instead of using GetNth
on every iteration. Another major improvement however is that
the code previously copied entire CommandHistory instances out of
the linked list s_historyLists, then removed the slot and copied
(not moved!) that instance into the front again. Now it uses the
splice function from std::list to do it in O(1) and virtually
cost-free.

Another major improvement (and the one I'm personally interested in)
is the switch from SHORT to int32_t. This will greatly simplify
the implementation of the future COOKED_READ_DATA class, as the
larger integer type will remove worries about over/underflow.
For instance, we can then just blindly increment/decrement the history
position and then only later clamp it to the expected range.

Validation Steps Performed

  • Existing history tests ✅
  • History cycling with F8 ✅
  • Navigating history with F7 ✅
**Original Pull Request:** https://github.com/microsoft/terminal/pull/15782 **State:** closed **Merged:** Yes --- This commit slightly modernizes `CommandHistory` by leaning more heavily on the STL container functionalities. For one, it uses for-range iterations to loop through `_commands` instead of using `GetNth` on every iteration. Another major improvement however is that the code previously copied entire `CommandHistory` instances out of the linked list `s_historyLists`, then removed the slot and copied (not moved!) that instance into the front again. Now it uses the `splice` function from `std::list` to do it in `O(1)` and virtually cost-free. Another major improvement (and the one I'm personally interested in) is the switch from `SHORT` to `int32_t`. This will greatly simplify the implementation of the future `COOKED_READ_DATA` class, as the larger integer type will remove worries about over/underflow. For instance, we can then just blindly increment/decrement the history position and then only later clamp it to the expected range. ## Validation Steps Performed * Existing history tests ✅ * History cycling with F8 ✅ * Navigating history with F7 ✅
claunia added the pull-request label 2026-01-31 09:42:40 +00:00
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 pull-request
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#30738
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?