nixos-configs VS emacs-overlay

If you put your flake in a Git repository, you can reference the repo without having to clone it by using a flake reference syntax. I keep my flake in GitHub, so I use github:reckenrode/nixos-configs to reference it when running nixos-rebuild, etc.

I use a GitHub action to run nix flake update nightly to bump my flake. My systems are set to update nightly (rebooting as necessary). It’s bee mostly free of problems. I did lose my Raspberry Pi 4B+, but that was a pretty hacky set up, and I didn’t bother to dig into why it stopped booting. Otherwise, it’s been pretty smooth. The only time I’ve needed to boot into a previous generation was when I botched some config changes when updating to a new NixOS release.

I’m running NixOS on a QNAP TS-453D. I wiped the software that came with it and run on the bare metal. I’ve added 16 GiB of RAM and an AX210-based Wi-Fi card to it. Everything works pretty well with three 16 TiB SeaGate Ironwolf Pro drives on ZFS and an SSD for the NixOS install itself. My NixOS config for it is here.

DXVK is available in nixpkgs. If you install it, it provides the setup_dxvk.sh script to inject DXVK into a Wine prefix. For an example of a derivation that sets up a prefix and copies the DLLs into it manually, see the FFXIV derivation in my configs.

There are my configs: https://github.com/reckenrode/nixos-configs.

Thanks for the clarification. I think our goals are just divergent. I’m looking for something that uses the packages in nixpkgs and integrates nicely with my nixos-configs, which I use to declaratively manage my macOS environments (none of my Linux systems are capable of running the game).

My flake does most of those things. I don’t have any systems with WSL, so I’m not sure whether or how that would work. If it can be created by nixosSystem, then it would probably work. I take a pretty different approach in my flake though. I’ve structured it so I can define platforms, hosts, and users by convention. Adding a new host is just creating the right directory and dropping a configuration.nix in it. Still, that might not be helpful for your needs since you’ve already got an established convention.

I make use of multiple channels in my nixos-configs. Instead of using overlays, I pass them as specialArgs to the system build function (e.g., lib.nixosSystem). That lets me reference them in my configuration as just another set of packages (e.g., I reference flake-specific packages, unstable packages, and x86_64-darwin packages here). Note that you also need to pass them as extraSpecialArgs to your specialArgs to access them from your Home Manager configuration.

The way I handle it in my configs is to add unstable as an attribute via an overlay. If I need a package from unstable, I can use it via pkgs.unstable..

The project uses this overlay: https://github.com/nix-community/emacs-overlay

What that means is if something is broken in Emacs, the community will fix it, and all I need to do is run `nix flake update` to grab the latest commit and then `nix run .#build-switch` to alter my system. Easy.

Thanks for the heads-up on the 404s! I've fixed those links.

In re: to org-agenda, I don't use that as much anymore. But I heavily, heavily using org-roam w/ org-roam-dailies everyday to build my own networked graph of notes. For tasks, nowadays I just use simple docs for projects and Asana to keep a catalog of everything.

Im a newish NixOS user, Ive used it like 20 times before but always quit because I couldnt debug errors, trying not to give up for the 20th time this time lmao; so Ive been trying to learn how to use overlays & flakes for a couple of days now. The ones I want to use/enable are: - Emacs-Overlay - Spicetify-Nix

Nix offers the same advantage through the use of emacs-overlay. Besides, Nixpkgs contains more Linux packages than any other distros. Depending on the user's needs, Nix is another option.

You can use this overlay to get the latest https://github.com/nix-community/emacs-overlay

Depending on your goals, emacs-overlay is also worth a look.

{ pkgs ? import {} }: ((import (builtins.fetchTarball { url = "https://github.com/nix-community/emacs-overlay/archive/master.tar.gz"; })) pkgs pkgs).emacsGit

One option is to install Nix and use emacs-overlay.

You can install Nix on your mac and use https://github.com/nix-community/emacs-overlay/, which supports all the existing tree-sitter-based major modes OOB.

Its great to see both eglot and tree-sitter being merged. However, I am unhappy about the state of 'emacs configurations/distributions' right now. I have been using Doom Emacs, but the development is pretty much stalled there [0], and I don't think there is any distribution that is keeping up with these cutting-edge features (compared to the NeoVim ecosystem, let's say). Somehow it feels like I was seeing a lot more activity about Emacs configurations two-three years ago.

> Compile EmacsLisp files ahead of time

Ooh, this is interesting. Hoping to see a derivation in https://github.com/nix-community/emacs-overlay soon.

[0] I am not complaining though as Doom was the main author's personal config from the get-go. I am just pointing out a void.