Bring live Omarchy/Quickshell customization under version control - #15
Open
susamn wants to merge 1 commit into
Open
Bring live Omarchy/Quickshell customization under version control#15susamn wants to merge 1 commit into
susamn wants to merge 1 commit into
Conversation
Untracked customization was sitting only in ~/.config/omarchy on the live
machine, at risk of being lost on reinstall or a new machine. This pulls it
into the dotfiles repo:
- 5 custom Quickshell plugins added as submodules (each is its own GitHub
repo already): mpd-lyrics, mpd-dashboard, homeassistant, rclone, illusions.
- susamn.desktop-widgets plugin (no separate repo) added as plain files.
- 3 third-party themes installed via `omarchy theme install` added as
submodules pointing at their upstream repos, rather than vendored:
last-call (OldJobobo), serenity (themiddlechildreal), terminus (r-bart).
- 3 genuinely hand-authored themes added as plain files: dandadan, momo-ken,
spiritedaway.
- shell.json / shell.toml (bar layout, plugin list, idle/lock, font size),
extensions/omarchy-menu.jsonc, branding/{about,screensaver}.txt, and
defaults/agent added as plain files.
- Only the one genuinely user-authored hook per event added: reload-mpdtui
and reload-herdr (theme-set.d). Omarchy's own stock onboarding-invitation
hooks (install-voxtype, setup-fingerprint, setup-agent under
post-update.d) were left out — those ship with every Omarchy install and
aren't user customization.
Deliberately excluded:
- homeassistant.json: holds a live Home Assistant long-lived access token
(verified via grep before staging anything). Needs a secrets-aware home
(e.g. the _secured submodule pattern) before it can be tracked in git.
- themes/theme and themes/aether: generic-named/empty directories, look
like stray leftovers rather than real themes. Left for confirmation.
Nothing in ~/.config on the live machine was touched — this only adds files
inside the worktree. Symlinking it back in (do-stow.sh) and deciding what to
do about homeassistant.json / the stray theme dirs are follow-up steps.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Untracked customization was sitting only in ~/.config/omarchy on the live machine, at risk of being lost on reinstall or a new machine. This pulls it into the dotfiles repo:
omarchy theme installadded as submodules pointing at their upstream repos, rather than vendored: last-call (OldJobobo), serenity (themiddlechildreal), terminus (r-bart).Deliberately excluded:
Nothing in ~/.config on the live machine was touched — this only adds files inside the worktree. Symlinking it back in (do-stow.sh) and deciding what to do about homeassistant.json / the stray theme dirs are follow-up steps.