my simple, portable niri dotfiles
  • CSS 75.2%
  • Shell 24.8%
Find a file
2026-06-04 01:49:52 +02:00
images/.nunewall Upload files to "images/.nunewall" 2026-06-01 07:09:26 +02:00
non-rice Update non-rice/compose-files/macos-qemu/compose.yml 2026-05-30 20:54:00 +02:00
rice Update rice/niri/config.kdl 2026-06-01 07:12:48 +02:00
LICENSE relicense to isc 2026-05-29 22:35:50 +02:00
README.md fix link 2026-06-04 01:49:52 +02:00

nune's niri dotfiles

wallpaper, featuring animated blitzwing

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.

aesthetic

  • just install foot, mako, niri, fuzzel, gnome polkit agent, wawa, and waybar, and copy these into your .config. put a wallpaper in "~/.nunewall", edit your timezone in waybar, set gnome polkit agent's location to your distro's, etc.
  • 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.
  • i, shamefully, use fish as the shell and bash when i need to use posix.

non-rice

  • the distro being used is void linux. i update once every 2 weeks and have had no issues.
  • 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.
    • 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.
  • i installed anything sync daemon to sync browser cache; i provide runit services since those runit isnt officially supported by anything sync daemon.
  • 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.
  • much of my workflow depends on containers and docker.
  • i use nano as text editor.

macos vm info

desktop of macos ventura vm

  • i have a dockerized vm with macos ventura i access with tigervnc. i use it for survey/seo tasks (no free clout) and some general macos related tinkering. why ventura? i know it isnt supported as much anymore but i find it lighter and nicer.
  • graphics are minimized as much as macos makes it possible to reduce load, and the browser, librewolf, is configured to block all media by default, given aggressive memory measures, and third party scripts to also spare the vm.
  • qutebrowser is also available for non-survey tasks.
  • the amount of memory depends on what i'm using it for, but i generally give it 2 cores and 2.5-5gb of ram allocation. i use adblocking dns (dnsforge.de) for the vm via a dnscrypt-proxy config inside the vm.

etc

  • you're on your own here when it comes to config edits.
  • should be compatible with most distros after minor changes.