user

User-level Nix Modules

Separate Nix files can be imported as modules using an import block:

imports = [ import1.nix
            import2.nix
            ...
          ];

My user-level Nix modules are organized into this directory:

• app - Apps or collections of apps bundled with my configs
  • browser - Used to set default browser
  • dmenu-scripts
  • doom-emacs
  • flatpak - Installs flatpak as a utility (flatpaks must be installed manually)
  • games - Gaming setup
  • git
  • keepass
  • ranger
  • terminal - Configuration for terminal emulators
  • virtualization - Virtualization and compatability layers
• lang - Various bundled programming languages
  • I will probably get rid of this in favor of a shell.nix for every project, once I learn how that works
• pkgs - “Package builds” for packages not in the Nix repositories
  • pokemon-colorscripts
  • rogauracore - not working yet
• shell - My default bash and zsh configs
  • sh - bash and zsh configs
  • cli-collection - Curated useful CLI utilities
• style - Stylix setup (system-wide base16 theme generation)
• wm - Window manager, compositor, wayland compositor, and/or desktop environment setups
  • hyprland
  • xmonad
  • picom

Variables imported from flake.nix

Variables can be imported from flake.nix by setting the extraSpecialArgs block inside the flake (see my flake for more details). This allows variables to merely be managed in one place (flake.nix) rather than having to manage them in multiple locations.

I use this to pass a few attribute sets:

• userSettings - Settings for the normal user (see flake.nix for more details)
• systemSettings - Settings for the system (see flake.nix for more details)
• inputs - Flake inputs (see flake.nix for more details)
• pkgs-stable - Allows me to include stable versions of packages along with (my default) unstable versions of packages
• pkgs-emacs - Pinned version of nixpkgs I use for Emacs and its dependencies
• pkgs-kdenlive - Pinned version of nixpkgs I use for kdenlive