Skip to content

feat: allow configuring terminal pane borders#778

Open
bgub wants to merge 1 commit into
pop-os:masterfrom
bgub:pane-border-styles
Open

feat: allow configuring terminal pane borders#778
bgub wants to merge 1 commit into
pop-os:masterfrom
bgub:pane-border-styles

Conversation

@bgub
Copy link
Copy Markdown

@bgub bgub commented Apr 7, 2026

Volunteered for this in the Pop!_OS Mattermost! When there are 2+ split panes, I put a container behind the pane grid and add gaps between panes so the background shows through. I didn't address the active pane background color yet (tried it but it doesn't seem to integrate with terminal color themes yet). Screenshot below.

image
  • I have disclosed use of any AI generated code in my commit messages.
  • I understand these changes in full and will be able to respond to review comments.
  • My change is accurately described in the commit message.
  • My contribution is tested and working as described.
  • I have read the Developer Certificate of Origin and certify my contribution under its conditions.

@maria-komarova
Copy link
Copy Markdown

@bgub what is the container color right now?

@bgub
Copy link
Copy Markdown
Author

bgub commented Apr 11, 2026

@maria-komarova do you mean the existing container? Or the container I added?

@maria-komarova
Copy link
Copy Markdown

@bgub which one is around the split area on the screenshot?

@bgub bgub force-pushed the pane-border-styles branch from 2272449 to 3c13e05 Compare April 14, 2026 06:46
@bgub
Copy link
Copy Markdown
Author

bgub commented Apr 14, 2026

@maria-komarova it's cosmic.bg_divider()

@maria-komarova
Copy link
Copy Markdown

Awesome, thanks! It looks good on the screenshot.

@bgub
Copy link
Copy Markdown
Author

bgub commented Apr 14, 2026

@maria-komarova I almost wonder if it would look better with slightly skinnier borders...

@maria-komarova
Copy link
Copy Markdown

Those are gaps really, not borders. And I think it looks good this way. Otherwise we should just use dividers.

@bgub
Copy link
Copy Markdown
Author

bgub commented Apr 15, 2026

@maria-komarova fair enough! What are next steps then? Should I just wait on a review or do you want me to be actively rebasing on the base branch?

@jackpot51 jackpot51 requested review from a team April 15, 2026 19:10
@jacobktm jacobktm self-assigned this Apr 21, 2026
Copy link
Copy Markdown

@jacobktm jacobktm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good!

@leviport
Copy link
Copy Markdown
Member

leviport commented May 7, 2026

There are some conflicts on this now. Since it already has both approvals, it should be good to merge after those are resolved.

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.

5 participants