| 14 Sep 2021 |
 emily | or just github:NixOS/nixpkgs/commit-ref if you're pinning the flake itself | 20:21:27 |
 edrex | i was able to just revert a local working copy and then nix shell .#.... Idk why i felt unsure, i've actually done that before :/ I think all this linker hacking stuff is just a bit baffling for my high level language brain and I start to feel very stupid :) | 20:29:27 |
| 15 Sep 2021 |
 balsoft | In reply to @emilazy:matrix.org
I wish nix edit .#foo did something useful instead of the incredibly useless thing it does. What would you wish it did? | 07:10:42 |
| emily | like nix edit -f . foo (in e.g. nixpkgs or similar), edit the actual source file rather than a frozen /nix/store copy | 07:11:16 |
| emily | otherwise it's more nix view :) | 07:11:28 |
| emily | I use nix edit to get around nixpkgs a lot | 07:11:39 |
| emily | that said I wouldn't switch to .# even if it worked because it seems quite slow with a repo as big as nixpkgs too :/ | 07:11:56 |
| emily | I also wish nix edit worked in the presence of evaluation failures but that's a bigger ask... | 07:13:11 |
| balsoft | In reply to @emilazy:matrix.org
like nix edit -f . foo (in e.g. nixpkgs or similar), edit the actual source file rather than a frozen /nix/store copy How would it edit the actual source file for e.g. nixpkgs ? It points to github:nixos/nixpkgs | 07:15:52 |
| emily | it can't work for that case of course, but it can (and I think already does?) track original location for path-based flakes etc. | 07:16:41 |
| emily | (and you really want to do that anyway so that backtraces give actually useful source locations) | 07:16:57 |
 niksnut | In reply to @emilazy:matrix.org
like nix edit -f . foo (in e.g. nixpkgs or similar), edit the actual source file rather than a frozen /nix/store copy https://github.com/NixOS/nix/issues/3347 | 18:41:28 |
|  paultrial left the room. | 19:27:19 |
| paultrial joined the room. | 19:27:45 |
| 17 Sep 2021 |
|  cleverca22 joined the room. | 06:03:50 |
|  George Wyatt joined the room. | 11:28:45 |
|  j0xaf joined the room. | 20:21:19 |
| 21 Sep 2021 |
 ilkecan | It isn't possible to specify the name of self directory of a flake, right? It is always named <hash>-source to prevent this impurity. Is that correct? | 18:06:47 |
| balsoft | Yes, I think it's hardcoded | 18:11:50 |
| ilkecan | Does anyone know why Nix doesn't allow filtering (using builtins.filterSource or builtins.path) strings with context? The implication of this is that it is not possible to filter Nix inputs. | 23:05:31 |
| ilkecan | * Does anyone know why Nix doesn't allow filtering (using builtins.filterSource or builtins.path) strings with context? The implication of this is that it is not possible to filter Flake inputs. | 23:06:18 |
 tomberek | ilkecan: working on it..... https://github.com/NixOS/nix/pull/5163 | 23:46:54 |
| ilkecan | In reply to @tomberek:matrix.org
ilkecan: working on it..... https://github.com/NixOS/nix/pull/5163 Actually I was writing a comment under your PR saying there are (at least) 3 different issues regarding filterSource on the wild. Your PR seem to be about fixing access to path '<path>' is forbidden in restricted mode while the one caused by filtering strings with context result in string '<string>' cannot refer to other paths. Does your PR fixes both of these? | 23:52:14 |
| tomberek | not sure... can you provide a minimal example to help distinguish the issues? | 23:53:08 |
| ilkecan | Also somewhat off topic but how can I test your PR? | 23:53:21 |
| tomberek | Look at Mazuel's repo | 23:54:03 |
| tomberek | * Look at Mazurel's repo | 23:54:17 |
| ilkecan | What I meant was how can I replace nix (currently nixUnstable) with the one built from your PR? | 23:54:52 |
| ilkecan | * What I meant was how can I replace nix (currently nixUnstable) with the one built from your branch? | 23:55:06 |
| ilkecan | I guess nix run 'github:tomberek/nix/flakes_filterSource' would work | 23:58:43 |
