How abhinavborah/bspwm-dotfiles works
Project type and purpose
• This repo is not a traditional codebase but a “rice” or desktop‐environment configuration for Arch Linux.
• Its purpose is to define and organize user‐level components (window manager, status bar, compositing, etc.) through dotfiles under ~/.config.
File structure
• Top‐level config directories:
• .config/bspwm – bspwm window manager settings
• .config/sxhkd – hotkey daemon bindings
• .config/polybar – status bar configuration
• .config/picom – compositor rules
• .config/dunst – notification daemon settings
• README lists runtime dependencies (bspwm, sxhkd, polybar, picom, dunst, feh, dmenu, rxvt-unicode, figlet, etc.).
• No build scripts—these are user‐level daemons and utilities that launch at login.
README for additional insights
• The “Packages needed” section enumerates each runtime component.
• “Future Scopes” hints at an install script that pieces all configs together—so think of an init script or bootstrap process.
a. Main components
• X server (Xorg or equivalent)
• bspwm (tiling window manager)
• sxhkd (keyboard event daemon)
• polybar (status bar)
• picom (compositor for shadows, transparency)
• dunst (notification daemon)
• feh (wallpaper setter)
• dmenu (application launcher)
• urxvt (terminal emulator)
• figlet (ASCII banner generator)
• (Optional) redshift, flameshot, fonts subsystem
b. Relationships and interactions
• User input (keyboard/mouse) → sxhkd → bspwm
• bspwm ←→ X server (window placement, focus)
• bspwm → polybar (workspace info, system stats)
• bspwm windows rendered → picom → X server compositor
• Applications (term, gui apps) spawn via dmenu/sxhkd/bspwm
• System notifications → dunst → displayed to user
• Wallpaper set once at session start via feh → X server background
c. Architectural patterns and principles
• Modular daemon‐based design: each concern runs as its own process reading from ~/.config
• Event‐driven: sxhkd captures events, dunst listens for notifications
• Declarative config: pure text files define behavior, no central monolith
d. Key technologies
• bspwm (C, uses XCB)
• sxhkd (C)
• polybar (C++, customizable modules)
• picom (C)
• dunst (C)
• feh, dmenu, rxvt‐unicode, figlet (shell‐driven utilities)