| 7 Apr 2026 |
 accelbread | Ive used them for work so a bunch of flakes choose same rev to pin to | 17:17:15 |
 goldstein | yeah, kinda, but you also use them “at runtime” when you write, like, nix shell nixpkgs#hello | 17:17:29 |
| accelbread | you can override the global registry with a flake setting iirc | 17:17:46 |
 zoë (she/her) | right right | 17:17:50 |
| goldstein | yeah you can | 17:17:53 |
| zoë (she/her) | ok sorry for the dumb question then ;-; | 17:18:15 |
| accelbread | not a dumb question, situation is a mess lol | 17:19:12 |
| zoë (she/her) | yeah i basically just use the local registry to add nixpkgs for these commands (such that it is the same as the one in my nix path (which is itself based on my system config's npins)), and that's about it | 17:20:09 |
| goldstein | you can also name it n to save yourself 6 keystrokes lol | 17:20:41 |
| zoë (she/her) | for the repl i still do -f <nixpkgs> because the whole legacyPackages.blabla stuff is kinda dumb (thanks to whoever implemented the -f and -E things for all installable lifesaver btw) | 17:21:16 |
| zoë (she/her) | * for the repl i still do -f <nixpkgs> because the whole legacyPackages.blabla stuff is kinda dumb (thanks to whoever implemented the -f and -E things for all installables btw, lifesaver) | 17:21:26 |
| zoë (she/her) | lol didn't think about that | 17:21:40 |
| zoë (she/her) | i might extend nix-debug to work for nix shell now that i actually have that setup now that i think about it | 17:22:15 |
| accelbread | nix run self starts a transient self-contained version of my emacs setup lol | 17:23:05 |
| accelbread | wait, even if something is in the local registry, you cant use it if you are online or the global registry is not reachable?? Thats cursed | 17:29:34 |
| goldstein | you totally can | 17:29:55 |
| accelbread | * wait, even if something is in the local registry, you cant use it if you are offline or the global registry is not reachable?? Thats cursed | 17:29:56 |
| goldstein | if it resolves to something that’s available locally | 17:30:02 |
| goldstein | global registry shouldn’t factor there at all | 17:30:14 |
| goldstein | registry is basically just rewrite rules: “if you see flakeref that looks like this, replace it with a flakeref that looks like that” | 17:30:57 |
| goldstein | (btw in lix global registry is vendored, so it’s fully offline; cppnix uses cached download) | 17:31:28 |
| accelbread | ahh i was testing some cppnix stuff
it doesnt allow any registry use if global registry is not cached
| 17:34:32 |
 llakala | In reply to @blokyk:matrix.org
for the repl i still do -f <nixpkgs> because the whole legacyPackages.blabla stuff is kinda dumb (thanks to whoever implemented the -f and -E things for all installables btw, lifesaver) in a lix context you can actually add all sorts of things to your repl with repl-overlays | 17:34:34 |
| llakala | i can immediately embed pkgs, lib, sources, wrappers, etc based on the dir I'm currently in | 17:34:56 |
| llakala | repl-overlays is woefully underutilized for how useful it is | 17:35:07 |
| llakala | see my repl-overlay [here](https://github.com/llakala/nixos/blob/607fcec2bbc14007c2e7736d79d59648ac507193/system/extras/_overlay.nix) | 17:35:44 |
| goldstein | lmao that’s cursedd | 17:36:21 |
| zoë (she/her) | thanks, i've been curious about repl-overlays but honestly haven't really found a use for them beyond the pkgs = legacyPackages.blabla thing | 17:36:43 |
| llakala | you have to use a lot of pwd nonsense bc when executing, `./.` is defined as the path of the repl-overlay, not your current path | 17:37:50 |
| llakala | but $PWD solves that (without purity, but who needs purity) | 17:38:09 |
