aethyr/Aethyr
2
0
Fork 0
Code Issues 281 Pull requests Projects Releases Packages Wiki Activity Actions

Epic: Command History System #143

New issue
Open
opened 2026-03-15 04:13:35 +00:00 by freemo · 0 comments
freemo commented 2026-03-15 04:13:35 +00:00
Owner
Copy link

Metadata

  • Commit Message: feat(ui): implement command history system
  • Branch: feature/command-history

Background and Context

The specification (§ Command History) describes a formal CommandHistory class with
push/previous/next/search methods, reverse incremental search (Ctrl+R), session
persistence, and integration with InputWindow.

Currently, command history is handled inline in Display#read_line with a simple
array and index.

Acceptance Criteria

  • CommandHistory class with push, previous, next, search, clear methods
  • Configurable capacity (default 1000)
  • Duplicate suppression
  • Reverse incremental search state machine (Ctrl+R)
  • Session persistence via player.info
  • Integration with InputWindow and keybinding system
  • BDD test coverage

Subtasks

  • Implement CommandHistory class
  • Implement reverse incremental search
  • Add session persistence
  • Integrate with InputWindow and keybindings

Definition of Done

This Epic is complete when all child issues are closed.

## Metadata - **Commit Message**: `feat(ui): implement command history system` - **Branch**: `feature/command-history` ## Background and Context The specification (§ Command History) describes a formal CommandHistory class with push/previous/next/search methods, reverse incremental search (Ctrl+R), session persistence, and integration with InputWindow. Currently, command history is handled inline in Display#read_line with a simple array and index. ## Acceptance Criteria - CommandHistory class with push, previous, next, search, clear methods - Configurable capacity (default 1000) - Duplicate suppression - Reverse incremental search state machine (Ctrl+R) - Session persistence via player.info - Integration with InputWindow and keybinding system - BDD test coverage ## Subtasks - [ ] Implement CommandHistory class - [ ] Implement reverse incremental search - [ ] Add session persistence - [ ] Integrate with InputWindow and keybindings ## Definition of Done This Epic is complete when all child issues are closed.
freemo added this to the (deleted) milestone 2026-03-15 04:13:35 +00:00
freemo self-assigned this 2026-03-15 04:25:25 +00:00
freemo modified the milestone from (deleted) to v1.1.0 2026-03-16 00:28:25 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
feature/m2-headless-renderer
dependabot/bundler/rdoc-6.3.2
dependabot/bundler/rexml-3.2.5
dependabot/bundler/json-tw-2.3
inprogress
dependabot/bundler/rake-tw-13.0
No results found.
Labels
Clear labels   
Blocked

Cannot proceed, depends on unresolved issue

  
Duplicate

Issue is a duplicate of an existing one

  
MoSCoW/Could Have

Desirable but not necessary, included if time permits

  
MoSCoW/Must Have

Essential, project cannot ship without it

  
MoSCoW/Should Have

Important but not strictly essential

  
Points/1

Estimated effort: 1 story points

  
Points/13

Estimated effort: 13 story points

  
Points/2

Estimated effort: 2 story points

  
Points/21

Estimated effort: 21 story points

  
Points/3

Estimated effort: 3 story points

  
Points/5

Estimated effort: 5 story points

  
Points/8

Estimated effort: 8 story points

  
Priority/Backlog

Not yet prioritized

  
Priority/Critical

Must be addressed immediately

  
Priority/High

Important, should be completed soon

  
Priority/Low

Nice to have, not time-sensitive

  
Priority/Medium

Normal priority, valid and should be addressed

  
State/Completed

Issue resolved and all PRs merged

  
State/In progress

Someone is actively working on this issue

  
State/In review

Implementation complete, PR submitted for review

  
State/Paused

Work temporarily suspended, typically blocked

  
State/Unverified

Issue created but not yet reviewed by a maintainer

  
State/Verified

Maintainer confirmed valid and actionable

  
State/Wont Do

Deliberate decision not to address this issue

  
Type/Bug

A defect in existing functionality

  
Type/Epic

Large body of work broken into multiple issues

  
Type/Feature

A new capability or user story

  
Type/Legendary

Major strategic pillar composed of multiple Epics

  
Type/Task

Technical or administrative work (not bug or feature)

  
Type/Testing

Test-only work item (TDD, test infrastructure, coverage)

No labels
Blocked
Duplicate
MoSCoW/Could Have
MoSCoW/Must Have
MoSCoW/Should Have
Points/1
Points/13
Points/2
Points/21
Points/3
Points/5
Points/8
Priority/Backlog
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
State/Completed
State/In progress
State/In review
State/Paused
State/Unverified
State/Verified
State/Wont Do
Type/Bug
Type/Epic
Type/Feature
Type/Legendary
Type/Task
Type/Testing
Milestone
Clear milestone
No items
No milestone
v1.1.0
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
freemo
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks
#112 Terminal UI Framework
aethyr/Aethyr
Depends on
#144 Implement CommandHistory class with push/previous/next/search
aethyr/Aethyr
#145 Implement reverse incremental search (Ctrl+R) state machine
aethyr/Aethyr
#146 Add command history session persistence via player.info
aethyr/Aethyr
#147 Integrate CommandHistory with InputWindow and keybinding system
aethyr/Aethyr
Reference: aethyr/Aethyr#143
No description provided.
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?