Home Manager using Nix VS emacs-overlay

It's probably overkill for what you are trying to do. But I have been using home-manager [0] as a way to quickly restore my working environment.

[0] https://nix-community.github.io/home-manager/

$ home-manager --version 23.05 $ nix-channel --add https://github.com/nix-community/home-manager/archive/release-23.11.tar.gz home-manager $ nix-channel --update $ nix-shell '' -A install [...] All done! The home-manager tool should now be installed and you can edit /home/MY-USERNAME/.config/home-manager/home.nix to configure Home Manager. Run 'man home-configuration.nix' to see all available options. $ home-manager --version 23.05

Unfortunately until we find more volunteers in this area, it is hard to see status quo changing. See also https://github.com/nix-community/home-manager/issues/607 and this ongoing project https://github.com/pjones/plasma-manager

> Channels are, AFAIU, a reference to some point-in-time/commit/version of nixpkgs

It's not specifically nixpkgs, but any Nix code generally.

Per the Nix manual[0]:

> Channels are a mechanism for referencing remote Nix expressions and conveniently retrieving their latest version.

e.g. home-manager's suggested channel is just the github tarball for the relevant branch[1]:

  nix-channel --add https://github.com/nix-community/home-manager/archive/master.tar.gz home-manager

It sounds like you'd benefit a lot from Nix/NixOS [1], if not just home-manager[2].

1. https://nixos.org/

2. https://github.com/nix-community/home-manager

nix-channel --add https://github.com/nix-community/home-manager/archive/master.tar.gz home-manager nix-channel --update nix-shell '' -A install

I'm using flakes and home manager and not really sure how to go about managing my neovim configuration. I've read through some other posts, github issues, and various articles trying to suss out a good way to do this. Reading through other people's configs and posts was somewhat helpful but there is a lot going on I don't understand and everyone's examples I've seen vary wildly.

Said store path contains the home-manager repo. After the home-manager run, the store path is recreated.

I can't answer all your questions, but home-manager does have a dconf module that would probably be better to use than that external tool. Everything inside the options block are the things you can pass to the dconf module.

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.