Yea there are tons of things being introduced here that are not even touched on anywhere and there are no links to the documentation for `with` which probably actually explains this caveat. Like "this example, why it makes sense" ... I think is implying that `pkgs.vim` would clobber the local `vim`, but that implies that the user is aware that `pkgs.vim` is even a thing. Plus where is `pkgs` even coming from? I get that it's coming from that first line, but so far in the tour that line hasn't been discussed at all. And where is `environment` even coming from?
Okay, i understand that "vim" is defined there and also present in the pkgs set. So the explanation i inferred is that nix takes the outmost scope first. Is that correct? None of the explanations say so.
This one doesn't make much sense to me but at least I can be aware of it. let takes priority over with.
Been really enjoying the tour up to this module, I think it needs to be explained better.
Yea there are tons of things being introduced here that are not even touched on anywhere and there are no links to the documentation for `with` which probably actually explains this caveat.
Like "this example, why it makes sense" ... I think is implying that `pkgs.vim` would clobber the local `vim`, but that implies that the user is aware that `pkgs.vim` is even a thing. Plus where is `pkgs` even coming from? I get that it's coming from that first line, but so far in the tour that line hasn't been discussed at all. And where is `environment` even coming from?
Okay, i understand that "vim" is defined there and also present in the pkgs set. So the explanation i inferred is that nix takes the outmost scope first. Is that correct? None of the explanations say so.