feat(table): add --border-row to draw a separator between every row#1084
Open
WladmirJunior wants to merge 2 commits into
Open
feat(table): add --border-row to draw a separator between every row#1084WladmirJunior wants to merge 2 commits into
WladmirJunior wants to merge 2 commits into
Conversation
lipgloss/table already supports BorderRow(true); this exposes it as a CLI flag (and GUM_TABLE_BORDER_ROW env) on the table command print path.
lipgloss/table already supports Width(w); this exposes it as a CLI flag (and GUM_TABLE_WIDTH env). Pairs with --border-row for fixed-width grids.
WladmirJunior
added a commit
to WladmirJunior/dotfiles
that referenced
this pull request
Jun 10, 2026
Drop stock gum entirely (no brew/apt gum) — until PR charmbracelet/gum#1084 lands the fork is the only gum, on both macOS and Linux ARM. lib/ui.sh now has one source of truth for the binary (UI_GUM_USE_FORK / UI_GUM_REPO / UI_GUM_TAG + ui_gum_asset), so switching to upstream after the merge is a one-line change. ui_ensure_gum fetches gum-<os>-<arch> (darwin-arm64, linux-arm64) to the Santa-allowed path. Fixes the old 404 (asset was a .tar.gz, not the bare binary).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Exposes two
lipgloss/tablecapabilities that thetablecommand did not surface:--border-row(envGUM_TABLE_BORDER_ROW) — draw a horizontal separatorbetween every data row, not just after the header.
--width(envGUM_TABLE_WIDTH) — set a fixed total table width; columnsauto-size to fit.
0(default) keeps the current content-based sizing.Both are opt-in; defaults are unchanged, so no behavior change for existing users.
Why
lipgloss/tablealready supportsBorderRow(true)andWidth(w);gum tablejust did not expose them. Per-row dividers match what SQL CLIs (grid mode),
tabulate(grid) andtty-tabledo by default, and a fixed width lets a tableline up with surrounding UI (e.g. a header box of the same width).
Before / After
Before (content-sized, divider only after the header):
After (
--border-row --width 72):