nakulbhat/dotfiles

Purpose and Entry Points

This is a personal Linux desktop dotfiles repository centered on a NixOS host and Hyprland Wayland session. The primary system entry point is nixos/configuration.nix; user-session behavior is rooted in hypr/hyprland.conf. Application configuration is maintained directly in sibling directories and is expected to be linked or deployed into user config locations.

NixOS System Composition

nixos/configuration.nix defines the machine-level NixOS configuration and imports hardware settings from nixos/hardware-configuration.nix. It composes focused modules for installed applications, shell setup, user accounts, development tools, Python, Neovim, and Hyprland:

• nixos/modules/apps.nix

• nixos/modules/users.nix

• nixos/modules/hyprland.nix

This is the main declarative provisioning boundary: NixOS evaluates these modules to configure system packages, services, users, and desktop-session prerequisites.

Hyprland Desktop Session

hypr/hyprland.conf is the interactive compositor/session control plane: monitor, input, window-management, keybinding, and startup behavior belong here. Its commands delegate operational actions to scripts under hypr/scripts/, separating compositor policy from imperative desktop actions:

• hypr/scripts/monitor_setup.sh

• hypr/scripts/runner.sh

• hypr/scripts/walls_randomiser.sh

The session depends on Wayland-native desktop utilities configured elsewhere in the repository.

Desktop UI and Notification Boundary

The visible desktop shell is split across specialized processes:

• waybar/config and waybar/style.css define the status bar and presentation.

• mako/config configures notifications.

• tofi/config configures the application launcher.

• hypr/hyprpaper.template provides wallpaper configuration input.

waybar/script.sh is the notable bridge from status-bar configuration to shell-derived runtime data or actions.

Launcher and Device Automation Scripts

Hyprland bindings and launch actions invoke shell scripts that encapsulate environment-specific behavior. Terminal, editor, PDF, runner, monitor, wallpaper, and audio-output actions are independently scriptable:

• hypr/scripts/term_launcher.sh

• hypr/scripts/nvim_launcher.sh

• hypr/scripts/switch_to_headphones.sh

These scripts are an imperative boundary around external desktop tools and hardware/audio state; Hyprland remains the dispatcher.

Editor and Developer Environment

Neovim is configured as a Lua-based IDE. nvim/init.lua bootstraps editor configuration; nvim/lua/config/lazy.lua establishes plugin management, while LSP and plugin declarations define language tooling and completion:

• nvim/lua/config/lsp.lua

• nvim/lua/plugins/core.lua

• nvim/lua/plugins/blink.lua

System-level availability of Neovim and development dependencies is coordinated through nixos/modules/neovim.nix, nixos/modules/dev-utils.nix, and nixos/modules/python-environment.nix.

Terminal, Shell, and Document Clients

The user interaction layer uses Kitty, Zsh, Zathura, and Oh My Posh theme data:

• kitty/kitty.conf

• zsh/.zshrc

• zathura/zathurarc

These applications are configured independently but participate in the Hyprland session through launch scripts and NixOS-installed packages. The result is a NixOS-provisioned Wayland workstation whose runtime control flows from Hyprland bindings into dedicated scripts and configured desktop clients.