Can't access default lib modules after extending nixpkgs.lib about dotfiles HOT 6 CLOSED

Actually, I might've fixed that; now I need to know why using the extended lib with imports (before config) is throwing errors that the names of my attribute sets for my paths in path.nix are not options!

from dotfiles.

Pinging @hlissner; sorry! I'm just really, really stuck on this next bit!

from dotfiles.

Well that's strange; I somehow fixed the next error by not using the lib.my.paths in my modules list...

from dotfiles.

And it seems I've come back full circle; some modules cannot seem to access certain variables in the lib module, whether built-in, such as mkForce, or my own.

from dotfiles.

Actually, it seems like I can't access anything from the extended module; the attributes are either seen as missing, or are confused for options by the Nix interpreter.

from dotfiles.

@hlissner: It would appear as though usage of your lib extension fails with the same errors as well.

from dotfiles.