What if you leave out the config.environment.variables // part (just
environment.variables = { NIX_PATH = /git/hub/nixcfg; };)?
The NixOS config infrastructure is supposed to take care of the //
part for you. I think the infinite recursion happens because
config.environment.variables is partly
Thanks, you're right that was it! I put the mkForce in while trying to
set NIX_PATH, then forgot to remove it after moving that to
interactiveShellInit instead. Man pages/environment variables back to
normal.
That reminds me though, is there a way to force NIX_PATH while leaving
the rest in
If I do that it complains that NIX_PATH is set elsewhere already. I
think it's merging the attribute sets but not individual attributes.
Which is good, wouldn't want it just concatenating strings or something
else magical. That's why I originally put in the lib.mkForce to
override it.
Thanks for
Hi,
On Wed, Jul 1, 2015 at 12:31 AM, Rickard Nilsson
rickard.nils...@telia.com wrote:
top = mkMerge (
map (a: { ${a}.opt2 = f a; }) (attrNames config.top)
)
This would work, only if you were not redefining top, or if you knew
the list of names ahead.
{
options.top = mkOption
Hi,
On 04/07/15 18:24, Jeffrey David Johnson wrote:
Man pages are hard to read because they're full of control characters. For
example:
NIXOS-REBUILD(8) NixOS Reference Pages
NIXOS-REBUILD(8)
ESC[1mNAMEESC[0m
This can be a symptom of $PAGER not being set to
Yeah I think that's what caused it. I got all my normal environment variables
back by removing the lib.mkForce and using lib.mkOverride instead on just
NIX_PATH, and now my PAGER is set to that and man pages work.
Jeff
On Sun, 05 Jul 2015 20:53:35 +0200
Eelco Dolstra eelco.dols...@logicblox.com
Hello all,
In the next day or two, I intend to merge this PR:
https://github.com/NixOS/nixpkgs/pull/8612
This will greatly improve the way we handle Ruby/Bundler packages.
Before I introduce the benefits, I'd like to draw attention to a
breaking change: you should now pass `gemName` and