Skip to content

feat(statusline): add stacked layout via EDGEE_STATUSLINE_LAYOUT#121

Merged
KokaKiwi merged 2 commits into
mainfrom
feat/statusline-customize
Jun 26, 2026
Merged

feat(statusline): add stacked layout via EDGEE_STATUSLINE_LAYOUT#121
KokaKiwi merged 2 commits into
mainfrom
feat/statusline-customize

Conversation

@KokaKiwi

Copy link
Copy Markdown
Member

Checklist

  • I have read the Contributor Guide
  • I have read and agree to the Code of Conduct
  • I have added a description of my changes and why I'd like them included in the section below

Description of Changes

Adds a EDGEE_STATUSLINE_LAYOUT env var to edgee statusline wrap, allowing the Edgee segment and the wrapped tool's statusline to be displayed on separate lines.

The root problem: when the wrapped statusline is wide (e.g. ccstatusline), the single-line merge truncates or garbles it to fit within the terminal column budget. Stacked layout sidesteps this entirely by giving each segment its own line with no width constraints.

  • Before: edgee statusline wrap <cmd> joined both segments on one line, truncating the wrapped output when it was too wide
  • After: EDGEE_STATUSLINE_LAYOUT=stacked emits each segment on its own line with no truncation; EDGEE_STATUSLINE_POSITION=right reverses the order
  • Implementation: new Layout enum in wrap.rs with from_env(); the stacked branch in merge_outputs short-circuits before the width-budget logic — no column arithmetic, no ellipsis
  • Zero regression: unset or any value other than stacked falls through to the existing inline path unchanged

@KokaKiwi KokaKiwi requested a review from a team as a code owner June 26, 2026 13:23
@KokaKiwi

Copy link
Copy Markdown
Member Author
image

@KokaKiwi KokaKiwi merged commit 4523caa into main Jun 26, 2026
7 of 8 checks passed
@KokaKiwi KokaKiwi deleted the feat/statusline-customize branch June 26, 2026 14:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants