More granular and extensive theming support
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by locating the current handling of the accent and foreground theme variables and tracing how popup colors, highlighting, and other UI styling are applied. The request spans RGBA, blur, tab styles, spacing, rounded corners, and hiding UI elements, so completion first requires agreeing on a scoped subset and its expected behavior.
Written by the indexing model from the issue text.
Description
Discord username (optional)
No response
Describe the solution you'd like?
More granular and extensive theming support: see additional context.
Is your feature request related to a problem? Please describe.
Much of the UI appearance is controlled by just two color variables, `accent` and `foreground`.
Additional context
- Finer control over color schemes, esp.
- separate variables for popup background colors, maybe even one for each kind of popup, defaulting to shades of
foregroundonly if unset - separate variables for different functions of the accent color, defaulting to shades of
accentonly if unset - additional variables to customize appearance of text highlighting
- separate variables for popup background colors, maybe even one for each kind of popup, defaulting to shades of
- Support for RGBA colors (cf. #17)
- Support for blur in backgrounds (incl. popups)
- Theming support beyond colors, e.g.:
- Different tab bar styles
- Rounded corners
- Custom padding amounts / margins (i.e., customizability beyond just compact vs. standard mode)
- Ability to hide some UI elements (e.g. help or settings icons in the top right of windows)
Default warp dark theme except with foreground: #ff0000 instead of foreground: #ffffff to illustrate current coarse theming granularity.
How important is this feature to you?
4
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
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from warpdotdev/warp
-
area:agent area:window-tabs-panes enhancement needs-info os:mac repro:high triaged
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
warpdotdev/warp#15768 · 3 comments · 1 reaction ·
-
bug factory-auto-implement factory:revops-factory os:mac ready-to-implement repro:high triaged warp:auto-triage-review
Difficulty 1/5 Under an hour Newbie friendliness 90/100
warpdotdev/warp#15697 · 2 comments ·
-
area:editor-notebooks bug repro:high triaged warp:auto-triage-review warp:tracking
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
warpdotdev/warp#13949 · 3 comments ·
-
markdown_parser: unclosed `<u>` markers pair via the emphasis algorithm and delete surrounding text Openarea:editor-notebooks bug ready-to-implement repro:high triaged warp:auto-triage-review
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
warpdotdev/warp#12863 · 2 comments ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
warpdotdev/warp#11969 · 2 comments ·
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
kwakseongjae/auto-hwp#319 ·
-
area:cli bug filter-quality good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
bevyengine/bevy#25861 ·
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
enhancement remote
Difficulty 2/5 1-3 hours Newbie friendliness 68/100