Make the pane separator appearance configurable

Open
#3,662 2 comments 43 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
rust
Domain
design, desktop

Research direction

No source files, tests, or entry points are identified in the issue. Locate the terminal pane-splitting and appearance-configuration entry points, then define the configurable separator size and color and verify that horizontal splits visibly use both settings.

Written by the indexing model from the issue text.

Description

area:window-tabs-panes enhancement triaged
Discord username (optional)

No response

Describe the solution you'd like?

When I split the terminal horizontally, I would like the appearance of the separator to be configurable, both in size and color.

Is your feature request related to a problem? Please describe.

My preferred working style is to have one terminal window split horizontally into two panes. In other terminal applications, the separator is almost as obvious as the title bar. Not necessarily attractive, but it stands out. In Warp, even with the lightness of the active and inactive panes being different, the pane separator is barely distinguishable from the command separators. This is especially true if each pane has had a lot of commands run, including some failures.

Additional context

It's not what I would call a bug, but it's a jarring enough experience for me that it's the main reason that I don't normally use Warp.

How important is this feature to you?

5 (Can't work without it!)

Warp Internal (ignore) - linear-label:770f6576-d6c0-4e4f-a259-fc64b5156087

None

Dominant language
Rust
Stars
65.1k
Forks
5.6k
PR merge metrics
PR metrics pending

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from warpdotdev/warp

All issues in warpdotdev/warp

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.