How plax-00/.dotfiles works
Project Type & Purpose
• This repository is a “dotfiles” (personal configuration) project.
• Its goal is to bootstrap and orchestrate your development environment: shell (Zsh), terminal multiplexers (tmux, Zellij), and Neovim, along with helper scripts.
High‐level Components
a. Host Operating System (macOS/Linux)
b. Terminal Emulator (iTerm2, Alacritty, etc.)
c. Shell Layer
– Zsh with ~/.zprofile, ~/.zshrc, functions & plugins
d. Multiplexer Layer
– tmux (tmux.conf)
– Zellij (config.kdl & layouts)
e. Editor Layer
– Neovim (nvim/init.lua, plugin configs, LSP configs)
f. Utility Scripts
– scripts/zsh/*.sh
g. Version Control
– Git repository (Makefile, .gitignore)
h. External Services
– Git remotes (GitHub) for plugin repos
– LSP Servers (rust-analyzer, pyright, etc.) pulled in by nvim-lspconfig
– Plugin registries (npm for treesitter, GitHub for telescope)
Relationships & Data Flows
• The OS launches the Terminal Emulator.
• The Terminal loads Zsh, which in turn sources dotfiles (aliases, completions, functions).
• Zsh invokes either tmux or Zellij sessions (depending on preference/layout).
• Within each pane, Neovim is launched:
• init.lua sets up Lazy.nvim (lazy-lock.json) to fetch and manage plugins.
• Plugins (treesitter, telescope, lsp) are loaded, triggering LSP servers.
• Utility scripts are invoked from Zsh or Neovim (e.g., edit-command-line-history).
• Makefile targets (e.g., install, sync) bootstrap or update the entire configuration.
• Git manages versioning and syncing to remote.
Architectural Patterns & Principles
• Layered Architecture: clear separation between Shell, Multiplexer, Editor, and Utilities.
• Declarative Configuration: all settings are code (lua, kdl, zsh scripts).
• Plugin‐driven Extensibility: uses lazy loading (lazy.nvim) to keep startup fast.
• DRY and Reusability: shared functions, centralized LSP server configs.
Final Advice
• Keep it detailed but clean: avoid overly granular file lists—focus on directories and their roles.