How gianlucatruda/dotfiles works
Main Components
a) Core Configuration Layer
• Bash Environment (.bash_profile, .bashrc)
• Configuration Files (.config directory)
• System Scripts (scripts directory)
b) Tool-specific Configurations
• Terminal Emulator (Alacritty)
• Shell Enhancement (Tmux)
• Text Editors (NeoVim, Vim)
• Package Management (Homebrew)
• System Automation (Hammerspoon, Karabiner)
c) Installation & Bootstrap Components
• Bootstrap Script
• Brew Installation
• macOS Configuration
┌─────────────────────────────────────────────────────┐
• User Interface │
• (Alacritty + Tmux + NeoVim/Vim + Karabiner) │
• ┤
• Shell Environment │
• (Bash + Aliases + Functions + Exports) │
• ┤
• Configuration Management │
• (Bootstrap + Homebrew + macOS Settings) │
• ┤
• Utility Scripts │
• (Custom GT Scripts + Hammerspoon) │
• ┘
Key Relationships to Highlight
a) Bootstrap Flow:
• How bootstrap.sh initiates the setup
• Configuration file symlinks
• Homebrew package installation flow
b) Tool Integration:
• How Tmux integrates with Alacritty
• NeoVim's plugin architecture
• Karabiner's key mapping system
Important Details
• Configuration File Locations:
• .config directory structure
• Configuration files
• Symlink relationships
• Tool Dependencies:
• Homebrew package relationships
• Plugin dependencies (especially for NeoVim)
• System integration points
Specific Implementation Notes
• Rectangles: Core configuration files
• Hexagons: Applications/Tools
• Rounded rectangles: Scripts
• Diamonds: Decision points in bootstrap process
Annotations for:
• Git configuration
• Shell customization
• NeoVim plugin structure
• Script functionality