Lix | 1117 Members | |
| Lix user channel. Feel free to discuss on-topic issues here and give each other help. For matrix.to links to the rest of the Lix channels, see: https://wiki.lix.systems/books/lix-organisation/page/matrix-rooms | 309 Servers |
| Sender | Message | Time |
|---|---|---|
| 15 Mar 2026 | ||
| it does make me wonder: does it still have the "0.00MiB removed" bug? | 21:11:53 | |
the nix repl stuff for derivations is also almost exactly the thing i put on my "to open issue about" list x) | 21:13:19 | |
| this is looking like it'll be a great release :D | 21:13:46 | |
| i do have a few tiny nits when it comes to the flakes settings prompt (lix#682)
| 22:00:07 | |
| 16 Mar 2026 | ||
| 09:59:28 | ||
| 11:35:42 | ||
| Is I’m trying to use the angle bracket syntax for the den library (https://den.oeiuwq.com/guides/angle-brackets/) which would help cut down on the verbosity (Den is a really neat way to structure cross platform nix code btw. Nonflakes fully supported) I note that lix has a builtin for findFile, while cppnix does not. I didn’t see a release note specifically calling out module.args.__findFile as removed. Just one asking for feedback on use cases last year | 21:53:17 | |
| it is possible | 21:54:23 | |
| I may just need to set my nix path | 21:56:08 | |
| can you show a sample from the file you're trying to do it in? | 21:56:56 | |
* can you show a sample from the file you're trying to do it in? i'm not very familiar with den by it seems like it works with the module system, so are you sure the __findFile symbol is available in the scope you're trying to use the <bracket> syntax in? | 21:59:43 | |
I think this should work? | 22:22:47 | |
hmm, i don't think so, because the __findFile isn't in the lexical scope of the rest of the code; have you tried putting it in the parameter list at the top? | 22:23:34 | |
* hmm, i don't think so, because the __findFile isn't in the lexical scope of the rest of the code; have you tried putting __findFile in the parameter list at the top? (i.e. { den, libdne, __findFile, ... }: ...) | 22:23:57 | |
* hmm, i don't think so, because the __findFile isn't in the lexical scope of the rest of the code; have you tried putting __findFile in the parameter list at the top? (i.e. { den, libdna, __findFile, ... }: ...) | 22:24:01 | |
| or if you don't want to mess with module args, you can always have a let binding for it, i'm pretty sure that should work | 22:24:58 | |
I also tried putting it in the top-level default.nix that evaluates everything | 22:25:18 | |
| * or if you don't want to mess with module args, you can always have a let binding for it, i'm pretty sure that should work:
| 22:25:58 | |
| This is probably something I should ask vic directly, assuming that __findFile works the same in lix as cppnix | 22:27:12 | |
since __findFile has to be in each file's lexical scope, you have to explicitly import it in each one, either by explicitly having it in your module's param list or by having a let binding or something to put it in scope | 22:27:20 | |
| I got it | 22:28:52 | |
| Thanks! | 22:28:56 | |
| :D | 22:29:08 | |
| I didn't understand what was meant by the file's lexical scope | 22:29:37 | |
| yes sorry i should have been clearer ;-; it's a hard concept to explain ^^; | 22:29:57 | |
| it doesn't help that den's docs omit that part | 22:30:29 | |
| * it doesn't help that den's docs omit that part :/ | 22:30:31 | |
| Looking again, it's there just not clear if you don't already know. I am also working on improving the docs | 22:31:23 | |
| Improve the docs all you want, but that part was never meant to be API in the first place | 22:34:13 | |
| yeah, it's an API abuse | 22:34:49 | |