Skip to content

Add Pure Black Color theme - #157

Open
ggregoro wants to merge 1 commit into
omacom:masterfrom
ggregoro:add-pure-black-color-theme
Open

Add Pure Black Color theme#157
ggregoro wants to merge 1 commit into
omacom:masterfrom
ggregoro:add-pure-black-color-theme

Conversation

@ggregoro

@ggregoro ggregoro commented Sep 2, 2026

Copy link
Copy Markdown

Adds Pure Black Color to the community themes list — a stark pure-black theme (#000000 bg, white fg, greyscale UI) with a real-colour ANSI terminal palette so syntax highlighting and TUIs read in full colour on the black. Yaru-blue folder icons, 5 bundled backgrounds.

Why: Omarchy's stock monochrome themes render terminal output in greyscale, which many people find hard to read. This keeps the pure-black look but restores real ANSI colour so tokens actually separate again.

Repo: https://github.com/ggregoro/omarchy-pure-black-color

Screenshot: LazyVim on colors.toml + btop + Neo-tree, on the theme's own wallpaper. 1200×662 webp, ~95 KB, added under assets/themes/. Entry placed alphabetically between Pulsar and Purple Moon.

@omarchybot

Copy link
Copy Markdown
Collaborator

Reviewed. The theme repo link resolves (HTTP 200, both anchors), assets/themes/pure-black-color.webp is committed at exactly the path the entry references (95KB, under the guide's limit), the figure block matches its neighbours attribute for attribute, and the entry sits correctly between Pulsar and Purple Moon as your description says. The screenshot shows a real session with an editor, btop and a file tree, which is what the guide asks for. Merges cleanly and collides with none of the other eight theme PRs open tonight.

Nothing found. One cosmetic note you can ignore: at 1200x662 the image is a shade wider than 16:9, so the grid centre-crops about 1% off each side — no layout effect, and worth mentioning only so it is not a surprise.

Checked by Claude Opus 5 with an independent second opinion from Codex at xhigh reasoning, run once across tonight's nine theme PRs; it reached the same conclusion on the crop independently and found nothing further. This repo has no build or test suite — the only CI is the Pages deploy — so nothing was executed. Waiting on the maintainer.

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