Open ThatOneOcto opened 2 years ago
Could you please post the code you are using to import Home Manager into your NixOS configuration? I have a feeling that <home-manager/nix-darwin>
is being imported alongside <home-manager/nixos>
, but I don't understand how their home-manager.users
option definition could conflict (as they both seem to inherit it from Home Manager's nixos/common.nix
).
I am importing both
This is my code that I am using to import
imports =
[ # Include the results of the hardware scan.
./hardware-configuration.nix
<home-manager/nixos>
<home-manager/nix-darwin>
];
After removing nix-darwin I am getting this error home-manager.users.octo.home.gtk
I thought home-manager could manage GTK themes, if not is there another way
home-manager.users.octo = {pkgs, ...}: {
home.pointerCursor = { package = pkgs.breeze-icons; gtk.enable = true; name = "breeze_cursors"; size = 24; };
home.gtk = {
enable = true;
iconTheme = { name = "ePapirus-dark"; package = "pkgs.papirus-icon-theme"; };
theme = { name = "Equilux"; package = "pkgs.equilux-theme"; };
};
};
The options for configuring GTK are under the gtk
attribute (as opposed to home.gtk
). When specifying the GTK themes, you should not quote the packages (i.e., use package = pkgs.papirus-icon-theme;
and package = pkgs.equilux-theme;
instead of package = "pkgs.papirus-icon-theme";
and package = "pkgs.equilux-theme";
).
Thank you for your contribution! I marked this issue as stale due to inactivity. Please be considerate of people watching this issue and receiving notifications before commenting 'I have this issue too'. We welcome additional information that will help resolve this issue. Please read the relevant sections below before commenting.
* If this is resolved, please consider closing it so that the maintainers know not to focus on this. * If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.
* If you are also experiencing this issue, please add details of your situation to help with the debugging process. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.
Don't be afraid to manually close an issue, even if it holds valuable information. Closed issues stay in the system for people to search, read, cross-reference, or even reopen – nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort.
Is there an existing issue for this?
Issue description
the error message is below
Maintainer CC
No response
System information