How acudworth3/dotfiles works
Project type and purpose
• This is a personal “dotfiles” repository for configuring a developer workstation. It is not a traditional client-server or microservices app but a configuration-management toolset that:
• Manages shell configs (bash, fish)
• Sets up TUI tools (atuin, btop, htop, lazydocker, lazygit, yazi, exa, jqp)
• Provides an opinionated Neovim setup (plugins, LSP configuration)
• Configures shell prompt (starship) and terminal (Windows Terminal)
File structure
• Top-level directories each hold the config for one tool or environment:
• bash_config, fish, htop, btop, lazydocker, lazygit, starship, windows_terminal.json
• nvim (with init.lua, lua/) and accompanying plugin configs
• yazi (file-explorer flavors, keymap.toml, package.toml, theme.toml)
• Utility files:
• install.sh – bootstraps system-wide dependencies via apt, cargo, snap, git clone, curl
• .gitignore, README.md, .jqp.yaml, .stowrc
• Uses GNU Stow for symlinking “repo/config → ~/.config/toolname”
README for additional insights
• README explains how to:
• Run install.sh to install dependencies
• Use stow to symlink configurations into the user’s home directory
• Launch Neovim under this config (NVIM_APPNAME trick)
• How the repo, installation script, stow, package managers, and the user’s environment interact
Detail
• That stow reads its .stowrc to know which folders to link
• Detail the two shell init flows (bashrc sourcing, fish/conf.d)
• NVIM_APPNAME override for an isolated Neovim profile