| 6 Mar 2026 |
 just1602 | Ugh, I'm less sure why you would do that. Could make sense for libraries, but not that much for infra management IMO | 23:48:28 |
| 7 Mar 2026 |
 vczf | Am I experiencing unjustified FUD if the vibes I get are “DRM blobs are coming for nix” | 00:13:39 |
 ian-h-chamberlain | does anyone have a recipe handy for getting into a environment with nix-direnv that doesn't require a whole flake to use? I'm getting tired of creating bespoke flakes whenever I need some tools for a random repo I checked out.
Basically I am hoping for something like nix shell nixpkgs#hello nixpkgs#bash but that I can stick into .envrc so it integrates with my shell automatically
| 02:55:23 |
 hexa | like shell.nix? | 03:15:54 |
| hexa | https://nix.dev/guides/recipes/direnv.html | 03:16:19 |
| hexa | where nixpkgs can just be nixpkgs = import <nixpkgs> { }; | 03:16:36 |
| ian-h-chamberlain | same problem: I just want a 1-2 line snippet to put in .envrc and be done with it. Actually in that case I think flake is easier since I can use a template for it.
I'm experimenting now with nix shell --expr but it feels like it will be a pain to plumb my system registry flakes through into it...
| 03:42:27 |
| ian-h-chamberlain | * same problem with creating a whole extra file. I just want a 1-2 line snippet to put in .envrc and be done with it. Actually in that case I think flake is easier since I can use a template for it.
I'm experimenting now with nix shell --expr but it feels like it will be a pain to plumb my system registry flakes through into it...
| 03:42:37 |
 @aloisw:julia0815.de | In reply to @just1602:systemli.org
I guess it's one way tro write stuff in rust without linking issue By linking against a WASM runtime written in Rust? | 07:11:11 |
 KSP Atlas | Redacted or Malformed Event | 12:39:55 |
| KSP Atlas | wait my bad i read it wrong | 12:40:22 |
| KSP Atlas | so sorry | 12:40:24 |
| KSP Atlas | wait nvm | 12:40:40 |
| KSP Atlas | i guess ill resend it | 12:40:49 |
| KSP Atlas | I noticed that, on https://lix.systems/team/, Jade is given they/them pronouns in their Core Team section, while the conflict of interest statements use the pronouns "herself" for them. Was this intended? | 12:41:50 |
 Liyua | Is there a way to find out if lix or nix is being used at evaluation time? My config uses lix but nixos-anywhere uses nix and right now I need to make explicit changes to use nixos-anywhere because the pipe-operator is called pipe-operators on nix. I was thinking maybe I can check which build system (idk what else to call it) is used and then have an if statement decide whether to use pipe-operator or pipe-operators.
| 13:41:32 |
| @aloisw:julia0815.de | At evaluation time you can check whether builtins.nixVersion is "2.18.3-lix", but this sounds like eval time is too late because that's not when you enable experimental features? | 13:44:20 |
 KFears 🏳️⚧️ (they/them) | In reply to @liyua:liyua.moe
Is there a way to find out if lix or nix is being used at evaluation time? My config uses lix but nixos-anywhere uses nix and right now I need to make explicit changes to use nixos-anywhere because the pipe-operator is called pipe-operators on nix. I was thinking maybe I can check which build system (idk what else to call it) is used and then have an if statement decide whether to use pipe-operator or pipe-operators.
You can add both to your config, it's not validated besides throwing a warning anyway | 13:44:54 |
| Liyua | I have it in the nix configuration and when I tried that the build failed | 13:45:21 |
| Liyua | (as in the nix.settings... not /etc/nix.conf)
| 13:45:44 |
| @aloisw:julia0815.de | Yeah that will always check against nix.package and reject unknown settings. | 13:46:05 |
| KFears 🏳️⚧️ (they/them) | Though, forward pipe doesn't exist in Lix, and there might be (but I don't remember, so double check) operator precedence difference | 13:46:34 |
| KFears 🏳️⚧️ (they/them) | In reply to @liyua:liyua.moe
I have it in the nix configuration and when I tried that the build failed Hmm, isn't "pipe-operator" part of "experimental-features" setting which is a freeform string? | 13:47:29 |
| Liyua | Other than the pipe-operator(s) thing I haven't noticed any issues
| 13:47:58 |
| Liyua | for me it's a list of strings | 13:48:19 |
| @aloisw:julia0815.de | It is but unknown experimental features are also rejected by the config validation. | 13:48:20 |
| Liyua | right now I have an if statement combined with a boolean in a let-in block so I can more easily switch without having to comment out the right lines but I'd like to automate it
| 13:49:35 |
| @aloisw:julia0815.de | Tbh I'm not sure what nix.settings has to do with that and when Nix is used for evaluation. If you just use nix once then not caring about it in the config and passing --extra-experimental-features pipe-operators should work? | 13:49:51 |
| Liyua | Although idk if that goes against the idea of declarativeness when the outside env changes the output | 13:50:05 |
| Liyua | The thing is when I use lix the config with pipe-operators doesn't evaluate and when I use nix the config with pipe-operator doesn't evaluate and I don't want to have to pass the 40 character extra exp features flag every time I type a nix command
| 13:52:03 |
