omarchy

Source excerpt starting at line 1.

1# Themes, Backgrounds, and Fonts2 3Read this before changing themes, backgrounds, fonts, or theme colors.4 5## Theme Commands6 7```bash8omarchy theme list              # Show available themes9omarchy theme current           # Show current theme10omarchy theme set <name>        # Apply theme ("Tokyo Night" and "tokyo-night" both work)11omarchy theme bg next           # Cycle background12omarchy theme install <url>     # Install from git repo13```14 15## Making a New Theme16 171. Create a directory under `~/.config/omarchy/themes`.182. See how an existing theme is done via `/usr/share/omarchy/themes/catppuccin`.193. Download a matching background (or several) from the internet and put them in `~/.config/omarchy/themes/<name-of-new-theme>/backgrounds/`.204. When done with the theme, run `omarchy theme set "Name of new theme"`.21 22Additional user backgrounds for any theme (stock or custom) go in23`~/.config/omarchy/backgrounds/<theme-slug>/`.24 25## What a Theme Installed From a Repo May Not Contain26 27A theme the user wrote by hand in `~/.config/omarchy/themes` is unrestricted, as28are Omarchy's own themes. From a theme cloned by `omarchy theme install`, Omarchy29drops only what runs code: any `*.lua` (Hyprland requires a theme's30`hyprland.lua` and `gum_env.lua` at login, Neovim loads `neovim.lua` at startup),31the terminal configs `alacritty.toml`, `foot.ini`, `ghostty.conf` and32`kitty.conf` (each names the program the terminal launches), and `vscode.json`33(names a VS Code extension to install). Those are regenerated from `colors.toml`34through `$OMARCHY_PATH/default/themed/*.tpl`, and named on stderr.35 36Everything else a cloned theme ships is kept, including `btop.theme`,37`chromium.theme`, `helix.toml`, `icons.theme`, `keyboard.rgb` and `shell.toml`.38Omarchy tells a cloned theme from the user's own by the `.git` directory a clone39leaves behind.40 41To change how Omarchy themes an app for every theme, write the template rather42than the theme: `~/.config/omarchy/themed/<config-name>.tpl` overrides the43built-in one. See `docs/theming.md` in the Omarchy repo.44 45## Customizing a Stock Theme46 47Never edit stock themes under `/usr/share/omarchy/themes/` — changes are lost48on update. Two safe options:49 50Both write into `~/.config/omarchy/themes`, where a theme the user wrote is51unrestricted — the list above applies only to a theme cloned from a repo.52 53**Overlay (preferred for small tweaks):** create a user theme directory with54the SAME slug containing only the files you want to change. When the theme is55applied, the stock theme is copied first and your files win on top:56 57```bash58mkdir -p ~/.config/omarchy/themes/catppuccin59cp /usr/share/omarchy/themes/catppuccin/colors.toml ~/.config/omarchy/themes/catppuccin/60# Edit the copied colors.toml, then re-apply:61omarchy theme set catppuccin62```63 64**Fork:** copy the whole stock theme under a new name for a fully independent65variant:66 67```bash68cp -r /usr/share/omarchy/themes/catppuccin ~/.config/omarchy/themes/catppuccin-custom69# Edit ~/.config/omarchy/themes/catppuccin-custom/, then:70omarchy theme set catppuccin-custom71```72 73## Fonts74 75```bash76omarchy font list               # Available fonts77omarchy font current            # Current font78omarchy font set <name>         # Change font79```80