Skip to content

Add session note history to the Capture input#49

Merged
ScottMorris merged 3 commits intomainfrom
fix/issue-37-capture-history
Apr 2, 2026
Merged

Add session note history to the Capture input#49
ScottMorris merged 3 commits intomainfrom
fix/issue-37-capture-history

Conversation

@ScottMorris
Copy link
Copy Markdown
Contributor

@ScottMorris ScottMorris commented Apr 2, 2026

Summary

User-facing changes

  • Session note history: Ctrl+Up and Ctrl+Down now browse plain-text note history from the current TUI session without taking over the existing Up and Down queue navigation.
  • Editor-like multiline behaviour: When the Capture input has multiple lines, Ctrl+Up and Ctrl+Down move within the current draft first and only switch history entries at the top or bottom.
  • Status note rendering: Multi-line notes now render as multiple lines in the Status pane instead of being flattened.
  • Command palette layout: Long command descriptions are truncated to the popup width instead of spilling past the right border.

Documentation

  • Shortcut guidance: Updated the in-app help, shortcut hints, README, and spec to document the new note-history behaviour.

Test plan

  • cargo fmt --check
  • cargo build
  • cargo clippy --workspace -- -D warnings
  • cargo test

Closes #37.

**What:**
- add session-only plain-text note history for the TUI Capture input
- let `Ctrl+Up` and `Ctrl+Down` move through past notes without changing the existing Up and Down selection behaviour
- preserve the current in-flight draft as the bottom of the history stack so it can be restored
- add tests for the history state and shortcut recognition

**Why:**
- issue #37 asks for a way to revisit earlier Capture text without giving up the current queue navigation bindings
- session-scoped note history keeps the implementation focused and predictable without adding persistence
**What:**
- add `Ctrl+Up` and `Ctrl+Down` note-history guidance to the in-app help and shortcut hints
- update the README and spec to describe session note history and draft restore behaviour

**Why:**
- the new history flow needs to be visible where users discover Insert mode shortcuts
- matching docs and help text reduce the chance that the feature feels hidden or surprising
**What:**
- let `Ctrl+Up` and `Ctrl+Down` move within multiline draft text before switching history entries at the top or bottom
- truncate command palette rows to the popup width so descriptions do not spill past the right border
- render multi-line note bodies as separate lines in the Status pane
- add focused tests for the cursor-boundary, palette-width, and note-rendering cases

**Why:**
- the history navigation should feel like text editing first and history browsing second
- the command palette overflow and flattened note bodies are visible TUI defects
- these fixes make issue #37 more polished in day-to-day use
@ScottMorris ScottMorris added bug Something isn't working tui liminal-flow-tui crate notes Notes issue documentation Improvements or additions to documentation labels Apr 2, 2026
@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 2, 2026

Flow Tests

110 tests  +10   110 ✅ +10   0s ⏱️ ±0s
  4 suites ± 0     0 💤 ± 0 
  1 files   ± 0     0 ❌ ± 0 

Results for commit 5ad53a5. ± Comparison against base commit 41b4514.

@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 2, 2026

CI check summary

  • [PASS] Format: success
  • [PASS] Clippy: success
  • [PASS] Test: success

@ScottMorris
Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector
Copy link
Copy Markdown

Codex Review: Didn't find any major issues. 🚀

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@ScottMorris ScottMorris merged commit 3ec8784 into main Apr 2, 2026
5 checks passed
@ScottMorris ScottMorris deleted the fix/issue-37-capture-history branch April 2, 2026 04:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working documentation Improvements or additions to documentation notes Notes issue tui liminal-flow-tui crate

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Navigate back to past comments in the Capture input

1 participant