<immae>
(to be more precise: making changes in about:config will modify prefs.js, but users.js come after prefs.js and may override anything you changed the next time you restart firefox)
<__monty__>
Thanks, immae!
<__monty__>
immae++
<{^_^}>
immae's karma got increased to 16
<immae>
:)
<__monty__>
I can't find the attribute names for extensions, via rycee's NUR firefox-addons.
<rycee>
colemickens: I added a comment with a suggesion that `apply` might work.
<colemickens>
makes sense to me, I guess I've never seen isBool before
<rycee>
__monty__: If it is a generally useful addon then you can create an issue in my nur repo and I can add it to the generated set. Otherwise you can create your own addon packages. Just have a look at the `buildFirefoxXpiAddon` function code.
<__monty__>
Hmm, I've added nur to my configuration.nix but darwin-rebuild complains about the nur attribute not being defined in my home.nix. Do I need to do more than add the packageOverride to be able to use nur with home-manager?
ldlework has joined #home-manager
<ldlework>
Hello.
<ldlework>
I am trying to update home-manager for the first time in a long while.
<ldlework>
yeah i'm on unstable as of a few days ago
<__monty__>
And do you have the corresponding home-manager channel?
<ldlework>
maybe i don't need to use home-manager from gt?
<ldlework>
no
<energizer>
rycee: you mentioned an editable symlink feature coming up, is there an issue for that? i'd like to subscribe
MmeQuignon has quit [Quit: WeeChat 2.8]
<rycee>
ldlework: The `home-manager/default.nix` file switched away from taking a `pkgs` argument some time ago. It now takes as argument the individual attributes it needs from `pkgs`. You can import it using `pkgs.callPackage` instead.
<ldlework>
I see.
<rycee>
energizer: What was the editable symlink feature, again?
<energizer>
rycee: so i can edit my dotfiles live without rebuilding
<__monty__>
rycee: I think energizer is referring to the alternative to ln -sf in an activation block.
<energizer>
yes
<rycee>
Ah, right. Yeah, that should work now with the `mkOutOfStoreSymlink` function.
<maralorn>
Hey, I am now running a gnome-session started by enabling that in the system config. Any hints how I can now source my home-manager profile at the start?
<maralorn>
My env-variables don‘t work now.
<maralorn>
Does the gnome-session read ~/.profile on start?
<rycee>
maralorn: Hopefully it reads `~/.xprofile`. You can try putting `. "$HOME/.nix-profile/etc/profile.d/hm-session-vars.sh"` in it.
<energizer>
rycee: is that released yet? i can't find that function in my repl
<rycee>
energizer: It's in the master branch but not 20.03.
<energizer>
ok
<energizer>
what's the home-manager equivalent of nixos-unstable?
<rycee>
The master branch.
<energizer>
everything is tested before merging into master?
<rycee>
Well, the master branch is run trough a CI job once a day so the tests that exists will be run then.
<cole-h>
Wow I didn't even see `mkOutOfStoreSymlink`... That could be a replacement for my current activation scripts where I `ln -sf ${./somefile} ~/.somefile`, right?
<cole-h>
Err, `ln -sf ${toString ./somefile} ~/.somefile` (to prevent it being added to the store)
<rycee>
cole-h: Yes.
<cole-h>
Beautiful. Thank you!
<rycee>
Replace by `home.file."somefile".source = config.lib.file.mkOutOfStoreSymlink ./somefile;`
<cole-h>
<3 rycee
<{^_^}>
rycee's karma got increased to 26
<energizer>
ive been using a function that recursively traverses ~/dotfiles/ and adds the regular files to xdg.configFile. i havent heard of anybody doing this so i sorta wonder if there's something wrong with it
<energizer>
do most people just manually assign all the paths in xdg.configFile?
<asymptotically>
do I need to do anything special to make programs.firefox.extensions work? I picked a couple of addons from the NUR but nothing appears in about:addons to enable :(
<rycee>
asymptotically: Do you use a profile defined through HM? Unfortunately, Firefox changed the way extensions are handled so they will only be seen in profiles managed by HM.
<rycee>
energizer: Should be fine doing it that way.
<energizer>
rycee: nice, thanks
<asymptotically>
oh I don't, I'll make one now
<rycee>
energizer: In some cases you might be able to replace such explicit recursion by using the `xdg.configFile.<name?>.recursive` option: https://rycee.gitlab.io/home-manager/options.html#opt-xdg.configFile._name__.recursive
<energizer>
rycee: that looks great. can you think of cases where it wouldn't work?
<asymptotically>
Extensions working fine now, thank you!
<rycee>
energizer: Mainly if you need to do any transformation of the source file names or directory structure. The `recursive` option just mirrors the source hierarchy.
<rycee>
asymptotically: Cool :-)
<energizer>
rycee: great, thanks
evanjs has quit [Read error: Connection reset by peer]
evanjs has joined #home-manager
evanjs has quit [Ping timeout: 256 seconds]
evanjs has joined #home-manager
judson has quit [Remote host closed the connection]
malSet_ has quit [Quit: Quit.]
malSet has joined #home-manager
judson has joined #home-manager
<maralorn>
rycee: My gnome doesn‘t seem to be reading `~.xprofile`. ☹︎
__monty__ has quit [Quit: leaving]
asymptotically has quit [Quit: Leaving]
<rycee>
maralorn: Hmm, bummer. Unfortunately I don't really know how gnome is setting up the session, looking at the code I don't exactly see how it happens.
<maralorn>
rycee: I think that is a totally valid assumption, when not using wayland.
<maralorn>
Probably should have mentioned that by now …
<rycee>
Yeah, that changes things :-)
<rycee>
Unfortunately I know even less about how wayland sessions are set up :-/
<cole-h>
Wayland doesn't read .Xprofile because it's not... X. lol
<rycee>
Have to go sleep. Best of luck!
<maralorn>
thanks
<maralorn>
rycee: For future reference. It‘s actually `.zprofile` because the gnome-session script looks in the $SHELL variable to start a login shell for getting the variables.