nune's niri dotfiles

theres very little stuff here when it comes to aesthetic. this is because i keep most apps to their defaults aside from ones i give dotfiles for. i also avoid noctalia, dank material shell, etc, because i believe those werent how niri was meant to be and are bloated. the best productivity setup is simple, light, and nondistracting for me and my use case. no need to overcomplicate window managers.

dependencies

required for "rice"

• niri (window manager)
• foot (terminal emulator)
• fuzzel (menu)
• mako (notification daemon)
• gnome polkit
• wawa (wallpaper setter)
• waybar (taskbar)
• fish (main shell)
• bash (posix shell)
• rust-script (for fastfetch packages counting)
• gpu-usage-waybar (for gpu usage in waybar)

tools i use (may be needed in configs)

• void linux (youll need to edit the fish config if your distro differs)
• zellij (multiplexer)
• smartmontools (drive testing)
• zoxide (funny cd command)
• senpai (irc client)
• eza (funny ls command)
• networkmanager (wifi)
• docker (for containers and development)
• nano (terminal text editor)
• kwrite (when a terminal text editor isnt enough)
• dnscrypt-proxy (encrypting my internet connections with cloudflare dns)
• cava (visualizing audio)
• cargo (managing rust packages)
• pipx (managing cargo packages)
• anything sync daemon (using my runit services, see non-rice/sv)
• exfetch (system fetch)

aesthetic

• my theme is a basic blue theme with a minimal, non-distracting waybar config and mako. if an even lighter alternative to waybar comes, im switching to it.

non-rice

• i use the linux-tkg kernel compiled with thin lto, scx-sched support, llvm toolchain, and optimized for my microarchitecture (skylake). i recompile it in case of a new security vulnerability OR when i feel like it.
• • as of this writing, i am temporarily not compiling my kernels with lto because of the new chassis i got, which only has 8gb ram.
• • the scx scheduler used most of the time is scx-rusty.
• non-aesthetic files (ie compose for production experimentation containers, fan control scripts) are in non-rice.
• fstrim and a basic fan setter is set up in services as well.
• theres also a dnscrypt-proxy config i use to force all my connections in dns over https.

etc

• you're on your own here when it comes to config edits. for example, setting your $wifi_name in .config/fish/secrets.fish.
• should be compatible with most distros after minor changes.