How mdrmono/dotfiles works
1. This repository is a personal dotfiles monorepo, not an application service. Its core architecture is a set of user-scoped configuration packages that are deployed into ~ and ~/.config through GNU Stow-created symlinks.
2. The main boundary is “source of truth in git” vs. “live config in the home directory.” After stow ., each package under .config/ maps to the corresponding runtime config location, so desktop tools and editors read their settings directly from symlinked files at startup.
3. The desktop/session layer is centered on i3, polybar, and rofi. i3/config defines the window manager behavior, polybar/config.ini defines the status bar, and rofi/config.rasi controls the app launcher. These components form the interactive shell of the Linux desktop.
4. scripts/util/ contains operational glue for the desktop environment. The scripts for battery alerts, Bluetooth control/status, dual-monitor setup, Polybar launch, and Toggl tracking are likely invoked from i3 keybindings, bar actions, or startup hooks. This is the repo’s main automation layer.
5. Terminal and shell customization are split between .config/alacritty/ and .p10k.zsh. Alacritty handles terminal appearance and behavior, while Powerlevel10k configures the Zsh prompt. These are user-facing presentation layers rather than app logic.
6. The editor subsystem has two parallel stacks: VS Code under .config/Code/User/ and Neovim under .config/nvim/. Neovim uses a LazyVim-style Lua layout (init.lua, lua/config/*, lua/plugins/*, lazy-lock.json), while VS Code is configured through JSON settings/keybindings. Doom Emacs is a third editor configuration path under .config/doom/ with the usual init.el, config.el, and packages.el.
7. Input method and locale-related behavior live under .config/fcitx5/. Those files control the IME profile and text input behavior, which makes this a system integration boundary rather than an app-specific config.
8. calibre is mostly a user-state and customization subtree rather than pure static config. It includes conversion settings, viewer/webengine settings, plugins, fonts caches, server config, and a large set of annotation files. This indicates the repo also preserves runtime preferences and content-processing state for Calibre.
9. The repo includes application-specific defaults and caches only where they matter to user experience: calibre state, alacritty themes, and editor metadata such as .config/nvim/lazy-lock.json and .config/nvim/.neoconf.json. These files capture versioned behavior and plugin pinning, which affects reproducibility.
10. .env.example is the only explicit environment handoff file at the root. It signals that some scripts or configs depend on local machine secrets or account-specific variables, but those values are intentionally kept outside version control.
11. Overall data flow is straightforward: git-managed dotfiles -> Stow symlinks -> desktop apps/editors/shell load configs at launch -> helper scripts are called by the session. There are no long-running services, databases, or backend APIs; the architecture is entirely user-session and workstation configuration.
Main entry points: init.lua Init · config i3 config · config.ini Polybar · nvim Neovim
Components 18
Git source
Versioned dotfiles and repo-managed state.
- dotfiles · Personal workstation configuration monorepo.
- .env.example · Template for local secrets and machine-specific variables.
.env.example
Deployment
How tracked files become live home-directory config.
- GNU Stow · Creates symlinks from repo packages into the home directory.
- Live config · Actual runtime files read from ~/.config and ~.
Desktop shell
Window manager, bar, launcher, and session glue.
Editors
Editor configurations and plugin pinning.
- Neovim · LazyVim-style Lua editor configuration.
.config/nvim - Init · Bootstraps Neovim and plugin loading.
.config/nvim/init.lua - Lua config · Options, keymaps, autocmds, and lazy setup.
.config/nvim/lua/config - Plugins · Plugin declarations and highlighting extensions.
.config/nvim/lua/plugins - VS Code · User settings and keybindings for VS Code.
.config/Code/User - Doom Emacs · Doom Emacs init, config, and package declarations.
.config/doom
Terminal shell
Terminal emulator and Zsh prompt customization.
- Alacritty · Terminal appearance and runtime behavior.
.config/alacritty/alacritty.toml - Powerlevel10k · Shell prompt customization in Zsh.
.p10k.zsh
System input
IME and workstation integration settings.
- Fcitx5 · Input method profile and text input behavior.
.config/fcitx5
App state
User preferences and runtime state preserved for apps.
- Calibre · Preferences, plugins, viewer annotations, and conversion settings.
.config/calibre
Automation
Session scripts invoked by desktop hooks and bindings.
- Session scripts · Battery, Bluetooth, monitor, Polybar, and Toggl helpers.
scripts/util
Connections 18
- dotfiles → GNU Stow: deploys via · Repository packages are installed into the home tree with symlinks.
- GNU Stow → Live config: materializes · Stow exposes tracked files as live config under ~ and ~/.config.
- Live config → i3 config: loads · i3 reads its config at session start.
- Live config → Polybar: loads · Polybar consumes its INI config when launched.
- Live config → Rofi: loads · Rofi reads launcher styling and behavior from the symlinked file.
- Live config → Alacritty: loads · Alacritty reads terminal settings from the live config path.
- Live config → Powerlevel10k: loads · Zsh loads the prompt theme from the home directory.
- Live config → Neovim: loads · Neovim starts from the symlinked editor tree.
- Neovim → Init: boots · Entry point for plugin initialization.
- Init → Lua config: delegates to · Core editor behavior is split into config modules.
- Init → Plugins: loads · Plugin specifications are loaded during startup.
- Live config → VS Code: loads · VS Code reads user settings and keybindings.
- Live config → Doom Emacs: loads · Doom Emacs uses the tracked init/config/package files.
- Live config → Fcitx5: loads · IME profile and input behavior are consumed by the desktop session.
- Live config → Calibre: persists · Calibre preferences and state are kept as user-scoped application data.
- i3 config → Session scripts: invokes · Keybindings and hooks likely call session helper scripts.
- Polybar → Session scripts: invokes · Bar actions and startup hooks use utility scripts.
- dotfiles → .env.example: documents · Template for required local environment variables.