Figure 1: Hyprland NixOS configuration as of 10 May 2026.

These are my NixOS 25.11 configuration files for my MS-7B90 PC with dual 1080p monitor setup. Hyprland is my graphical user interface (GUI). Flakes are used to manage packages.

• Language breakdown
• Autostart
• Default apps
• History
• Hyprland
• Keyboard shortcuts
• nixpkgs
  • Antigravity package
  • Marvin package
  • OpenRA package
• Shell profile
  • Linux From Scratch (LFS) commands
  • Package management commands
• Wallpaper script
  • Syntax
• Waybar
  • NixOS menu (): only shown on monitor 1
  • Workspaces (which are numbered): shown on both monitors
  • Weather conditions: shown on monitor 1
  • Pulseaudio: shown on monitor 1
  • Uptime (󰔚): shown on monitor 1
  • Wallpaper number widget (󰸉): shown on monitor 1
  • Previous wallpaper button (): shown on monitor 1
  • Random wallpaper button (): shown on monitor 1
  • Forward wallpaper button (): shown on monitor 1
  • Wallpaper specification button (): shown on monitor 1
  • The title of your currently focused window: shown on both monitors
  • Keyboard layout (): shown on monitor 2
  • Motherboard temperature (): shown on both monitors
  • Root file system usage (/): shown on monitor 1
  • Arch file system usage (A): shown on monitor 1
  • Data file system usage (D): shown on monitor 1
  • Internet download speed () on enp24s0 interface in bps: shown on monitor 2
  • Internet upload speed () on enp24s0 interface in bps: shown on monitor 2
  • CPU usage percentage (): shown on monitor 1
  • RAM usage percentage (): shown on monitor 1
  • zRAM utilization (󰾆): shown on monitor 1
  • Swap utilization (󰓡): shown on monitor 1
  • GPU memory usage percentage (): shown on monitor 2
  • GPU utilization percentage (󱃏): shown on monitor 2
  • Updates¹ available: shown on both monitors
  • Phone battery status and notifications: shown on both monitors
  • Clock: on both monitors
  • Footnotes
• Workspaces
  • Monitor 1
  • Monitor 2

Applications and programs autostarted include the default browser, virtual machine manager, the Brave browser, Waybar, Discord, Blueman Manager, KDE Connect, Kitty (with Hyfetch), WinBoat, GNOME Files, Alacritty, my Debian 13 virtual machine, and cliphist and wl-clip-persist for managing the clipboard. A command is also run to show the next wallpaper, another kills old processes for showing the wallpaper that are errantly running, and another logs network activity so it can be used for creating graphs if one clicks the network widgets in the Waybar.

• Application menu is Rofi.
• File manager is Dolphin.
• KDE Connect.
• Terminal is Alacritty, although Kitty is also installed and used for creating Hyfetch output-inclusive screenshots.
• Text editor/IDE is Antigravity. Neovim and Visual Studio Code are also installed.
• Web browser is Google Chrome, although Brave and Firefox are also installed.

6e524bcfb7db7653ac4df86b378faab6e25a7bf3 was the final commit with vim-ai with deepseek-coder model. Was removed as it wasn't useful for me.

The sources of Hyprland and hy3 differ depending on the time. Sometimes it is built from the NixOS stable branch, other times unstable branch, other times master branch and other times still from the latest upstream release. As of 16 May 2026, it uses the latest upstream releases for both and a standard .conf config file. A Lua config was tried from 15 to 16 May 2026, but hy3 errors were common on loading and while Antigravity's AI assistent could fix these for that Hyprland session, as soon as I restarted Hyprland (through rebooting or restarting SDDM) the errors returned. Many workspace bindings and keybindings were also forgotten during Hyprland restarts.

shell/hyprland contains shell scripts that are part of my Hyprland setup, or used to launch apps under Hyprland. dotfiles/ contains my Hyprland configuration files and desktop config files for the aforementioned apps. I used to compile the latest version of Hyprland from source, but recompiling every time I ran nixfrb (i.e., rebuild the system) eventually deterred me.

Essentially just a copy of the antigravity package in NixOS/nixpkgs with shell/hyprland/updates auto-updating it.

The Marvin package is essentially just a copy of the marvin package in NixOS/nixpkgs; I keep it as an overlay just so that I can more easily update it to the latest version when a new release comes out. I do update it in NixOS/nixpkgs, too, but it can take a month for my PRs to be merged.

The OpenRA package utilizes $HOME/GitHub/others/OpenRA as the source directory for its git repository. It will install the latest git commit and version it as <commit number>.git.<commit 7-character hash>. It is a modified version of the OpenRA package in NixOS/nixpkgs as of ~October 2025. I use this one as it is more up-to-date, builds from a local copy of the git repo and has a version string I prefer.

To update the deps.json file for OpenRA git package, run:

nix-build --arg pkgs '(import <nixpkgs> {})' -A engines.git

in nixpkgs/openra. Or simply run openraup. The package assumes you have a local copy of the OpenRA git repo at ${homeDir}/GitHub/others/OpenRA (where ${homeDir} is from nix/lib.nix).

Within shell/root is my root shell profile files, and within shell/user is my user shell profile files. I have many functions designed to make my time in the terminal more pleasant.

These commands all run within my LFS virtual machine (VM).

• cleanup_old_libraries_gpt (not defined on NixOS host) is used to remove old libraries and rebuild packages that depend on those old libraries.
• cleanup_old_doc_dirs_gpt (not defined on NixOS host) is used to remove old and unused documentation directories.
• lfs_autobuild (called autobuild in VM) is used to build and install packages. Syntax is lfs_autobuild <package name> argument(s). By default, it won't reinstall a package if it's already installed and up to date, unless you provide the -f (for force) flag. --dry-run is an argument that will list the commands that would be run if the command was issued without this argument. LFS and BFLS instructions are used for most package installs, but if a custom package whose name matches that specified exist in ~/lfs_packaging, it will be built instead.
• lfs_autoremove (called autoremove in VM) is used to remove one or more packages from the LFS system. Syntax is lfs_autoremove [--dry-run] [-f] <package_name> [<package_name> ...]. It automatically checks for libraries provided by other packages that depend on the package being removed; if such library(s) exist, the removal is cancelled. -f removes this library-checking behaviour. --dry-run lists what actions would be taken if the command was issued without this argument. Multiple package names may be supplied and each will be removed in turn.
• du_pkg reports the total disk space used by all files belonging to a given package, using /var/lib/custom-packages/ (or /var/lib/book-packages/) to determine ownership. Syntax is du_pkg <package_name>.
• lfs_commit (not defined on the NixOS host) but is defined within the LFS VM. It commits changes to inventory files.
• lfs_sync_to_vm (not defined on VM) is used to sync the LFS scripts to the LFS VM.
• lfs_update (called update in VM) is used to update the LFS system. It updates Python packages with pip, Julia with juliaup and uses lfs_autobuild to install updates to other packages.
• lfs_updates (called updates in VM) is used to check for updates in the LFS system.

• nixcg is used to remove old generations and sources with sudo nix-collect-garbage -d.
• nixdg is used to delete specified generations.
• nixdiff will show the differences between the two most recent generations of your system.
• nixfrb is used to build the flake-based system configuration.
• nixfu will update your flake.lock file.
• nixlg will list generations.
• nixrb (alias rebuild) will rebuild your system without using your flake setup.
• nixrsu will run nixfu and nixfrb, if nixfu updated flake.lock.
• nixs will search for a package in a specified repository. First argument is repo name and second argument is the package name.
• nixspc will count the number of packages in a specified repository.
• nixstrep will try to repair the Nix store, if necessary.
• nixver will show the version of your NixOS system based on your installed channels.
• update will run nixrsu, nixstrep and nixcg.
• upgrade will upgrade your system to the latest stable NixOS release. Shell profile is set up to automatically check for upgrades within 35 days of the end of life of your installed version of NixOS.
• rollback will roll back your system to the previous generation.

There is a script within this repository called wallpaper that will, using swaybg, set your background to a wallpaper in Arch's /usr/share/wallpapers, /usr/share/backgrounds, /usr/share/antergos/wallpapers, ~/.local/share/backgrounds, ~/.local/share/wallpapers or ~/Pictures/Wallpapers. It is used by some Waybar widgets mentioned below. I originally used hyprpaper to set the wallpaper, I find hyprpaper more difficult to use and I also use the wallpaper script under Niri.

wallpaper <algorithm/no> [direction]

The algorithm/no argument is mandatory; the direction argument is optional.

The algorithm argument decides which algorithm is used to decide the wallpaper set as your background. If you give it the argument random (first letter's case doesn't matter), you will get a randomly decided wallpaper out of those within those specified directories. If you give it the argument systematic (first letter's case also doesn't matter), wallpaper will systematically go through the wallpapers one by one.

An alternative to the algorithm argument is the no argument which specifies the number of the wallpaper to be displayed. Keep in mind that list-wallpapers (which shows wallpapers with Vim line numbers) displays wallpapers with a number one higher than the number used by the wallpaper script (as wallpaper script numbers start at 0, whereas Vim starts at 1).

The direction argument, which is only applicable if the first argument is algorithm, can be "previous" or something else. If it is previous and the first argument is "systematic", this will lead to the previous wallpaper being shown. Otherwise the next wallpaper will be shown. This is also the default behaviour if direction is omitted.

Waybar, as of 8 July 2026, is pinned to the stable 0.15.0 release (reverted from HEAD git due to a workspace-click regression in later git commits). The Waybar has the below components. The order below formerly referred to their order left to right, but that's not the case anymore.

which gives you options for (all websites opened in Chrome and all directories opened in Antigravity):

• Opening up the Nerd font cheat sheet websites.
• Opening up NixOS-configs repo on GitHub.
• Opening up the NixOS options search.
• Opening up the NixOS packages search.
• Opening up the NixOS Wiki.
• Rebuilding one's system.
• Repairing the Nix store.
• Update one's system without repairing the store.
• Opening NixOS-configs in the default code editor.
• Suspend.
• Hibernate.
• Shutdown.
• Logout.
• Reboot.

Workspaces are shown here only on the monitor in which they're active.

Obtained by wttr.in. Beware that wttr.in can be quite unreliable at times.

The background colour of this depends on the temperature. Temperatures of <10°C are blue, between 10 and <15°C are lighter blue, between 15 and <20°C are cyan, between 20 and <25°C are green, between 25 and <30°C are orange, between 30 and <35°C are light red, between 35 and <40°C are medium red and ≥40°C are dark red.

Shows the battery status and volume of your output audio device (as percentages). Has a purple background and white text. You can decrease or increase volume by scrolling on it. Left clicking opens pavucontrol.

If using headphones, the  symbol will be shown; if using bluetooth, the  symbol will be shown. These will be to the immediate left of the audio volume percentage. If these are wireless, you will also see a battery symbol (the specifics of this symbol will depend on the charge in a way explained in the "Phone battery status and notifications" section) and the battery charge to its right.

Shows the uptime in the format: hour(s):minute(s):second(s).

It displays the number of the wallpaper most recently displayed on your desktop, then a forward slash, and then the total number of wallpapers you have installed on your system.

When clicked, this changes your wallpaper to the previous one in your collection (keeping in mind, this is when you're using the systematic algorithm for the wallpaper script).

When clicked, this changes your wallpaper to a randomly selected one.

When clicked, this changes your wallpaper to the next systematically selected one.

When clicked, this changes your wallpaper to a wallpaper whose number you specify in a pop-up window.

Is followed by its two-letter initial. I have two colours set up for this widget: us=teal, which is also the default, and br=purple.

It is colour coded with <40°C being sky blue, 40 to <60°C being green, 60 to <75°C being orange, 75 to <85°C being light red and ≥85°C being deep red.

Left clicking this opens a graph showing the history of the motherboard temperature.

If the used disk space is less than 25%, it is green If it is between 25 to <50%, it is lighter green. If it is between 50 to <75%, it is yellow. If it is between 75 to <90%, it is orange. If it is ≥90%, it is red.

Left clicking this opens gtop in Alacritty. Right clicking runs nixcg in Alacritty.

If the used disk space is less than 25%, it is green If it is between 25 to <50%, it is lighter green. If it is between 50 to <75%, it is yellow. If it is between 75 to <95%, it is orange. If it is ≥95%, it is red. The reason for the higher boundaries is that my /data partition was already very full when this NixOS install was setup.

If the used disk space is less than 25%, it is green If it is between 25 to <50%, it is lighter green. If it is between 50 to <75%, it is yellow. If it is between 75 to <95%, it is orange. If it is ≥95%, it is red. The reason for the higher boundaries is that my /data partition was already very full when this NixOS install was setup.

If the download speed is <10486 bits per second, it is green. If it is between 10486 and <104858 bits per second, it is light green. If it is between 104858 and <1048576 bits per second, it is orange. If it is between 1048576 and <5242880 bits per second, it is light red. If it is ≥5242880 bits per second, it is darker red.

Left clicking this opens nethogs, which is a command-line app monitoring network activity, in Alacritty. Right clicking prompts the user for how long they want to monitor network usage for and then, after this period, it displays network usage and network usage by process. Middle clicking produces a pop up window with a graph of download speed (on enp24s0) history against time.

If the download speed is <5243 bits per second, it is green. If it is between 5243 and <52429 bits per second, it is light green. If it is between 52429 and <524288 bits per second, it is orange. If it is between 524288 and <5242880 bits per second, it is light red. If it is ≥5242880 bits per second, it is darker red.

Left clicking and right clicking does the same thing as per download speed. Middle clicking largely does the same as per download, except with upload speeds.

If the CPU usage is less than 25%, it is green. If it is between 25 to <50%, it is lighter green. If it is between 50 to <75%, it is yellow. If it is between 75 to <90%, it is orange. If it is ≥90%, it is red.

Left clicking this opens gtop, a command-line system monitor app, in Alacritty. Right clicking this opens a graph of the CPU usage over time.

If the CPU usage is less than 25%, it is green. If it is between 25 to <50%, it is lighter green. If it is between 50 to <75%, it is yellow. If it is between 75 to <90%, it is orange. If it is ≥90%, it is red.

Left clicking this opens gtop in Alacritty. Right clicking this opens a graph of the RAM usage over time.

zRAM is only used if RAM is used up.

Swap is only used if zRAM and RAM are used up.

If the GPU memory usage is less than 25%, it is green. If it is between 25 to <50%, it is lighter green. If it is between 50 to <75%, it is yellow. If it is between 75 to <90%, it is orange. If it is ≥90%, it is red.

Left clicking this opens up an Alacritty terminal with nvidia-smi output (showing GPU utilization and processes utilizing it). Right clicking this opens a graph of the GPU memory usage over time.

If the GPU utilization is less than 25%, it is green. If it is between 25 to <50%, it is lighter green. If it is between 50 to <75%, it is yellow. If it is between 75 to <90%, it is orange. If it is ≥90%, it is red.

Left clicking this opens up an Alacritty terminal with nvidia-smi output (showing GPU utilization and processes utilizing it). Right clicking this opens a graph of the GPU utilization over time.

• "h" indicates updates to home-manager are available.
• "m" indicates updates to nixpkgs-master are available.
• "s" indicates that updates to nixpkgs (stable branch) are available.
• "u" indicates updates to nixpkgs-unstable are available.
• 󱇛 indicates that hy3 updates are available.
•  indicates that Hyprland updates are available.
• 󱢇 indicates that OpenRA updates are available.
• 󰄻 indicates that Marvin updates are available.

Battery status is symbolized with:

• 󰂅 if the battery is charging and has 90% to 100% charge.
• 󰂄 if the battery is charging and has 70% to <90% charge.
• 󰂃 if the battery is charging and has 50% to <70% charge.
• 󰂂 if the battery is charging and has 30% to <50% charge.
• 󰢜 if the battery is charging and has <30% charge.
• 󰁹 if the battery is not charging and has ≥90% charge.
• 󰂀 if the battery is not charging and has 70% to <90% charge.
• 󰁾 if the battery is not charging and has 50% to <70% charge.
• 󰁼 if the battery is not charging and has 30% to <50% charge.
• 󰁺 if the battery is 15% to <30%.
• 󰁻 if the battery is <15% charge.

Notifications are symbolized with:

• 󰄷 if disconnected.
• 󱅫 if there is a notification.
• 󰂚 if there are no notifications.
• 󰂛 if in do not disturb mode.

With AM/PM time with seconds, short day of the week name, day of the month/month of the year (short format).

1. The script that manages this runs every ~20 minutes, and runs nixfu as part of checking for updates. If any are available, you merely need to run nixfrb to install them. Left clicking the widget, will open a terminal that runs nixfrb.

Workspace 1: Chrome (F1).
Workspace 2: Kitty terminal that takes up just enough of the screen to show Hyfetch output, useful for taking screenshots(Win+2).
Workspace 5: Antigravity/VSCode (F5).
Workspace 7: Terminal and Chrome windows for dealing with HPC job submission (F7).
Workspace 15: Brave (Insert).
Workspace 16: Instagram (Home).
Workspace 18: Okular (Win+Delete).
Workspace 21: Steam (Win+F1).
Workspace 25: VLC media player (Win+F5).

Workspace 3: Bluetooth (F3).
Workspace 4: WinBoat (F4).
Workspace 6: WinBoat FreeRDP window for working in Word (F6).
Workspace 8: Gaming, especially RuneScape or OpenRA (F8).
Workspace 9: WhatsApp Web (F9).
Workspace 10: Google Chat (F10).
Workspace 11: Discord (F11).
Workspace 12: Boo (F12).
Workspace 13: Nautilus file manager (Win+Scroll Lock).
Workspace 14: KDE Connect (Pause).
Workspace 17: Lutris (Page Up).
Workspace 19: Duolingo (End).
Workspace 20: Terminal (Page Down).
Workspace 22: Payday 2 (Win+F2).
Workspace 23: Google Earth (Win+F3).
Workspace 24: Boo (Win+F4).
Workspace 26: VLC media player (Win+F6).
Workspace 27: Brave private window (Win+F7).
Workspace 28: Virtual machine manager (Win+F8).
Workspaces 29-31: Virt Viewer (Win+F9 to F11).
Workspace 32: Chemistry apps (Win+F12).