You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Take it with a grain of salt but on my machine it takes an average of 7.1ms to process a 349 lines configuration and generate a Nix file with 433 lines.
You can make changes in the UI and create a dump of your dconf file at any time, which you can Nixify so Home Manager can restore the next time you run home-manager switch. To create a dump, run the following command:
dconf dump / > dconf.settings
Run
The easiest way is to pipe the standard input to dconf2nix and expect the result in the standard output:
dconf dump / | dconf2nix > dconf.nix
If you have an input file instead, you can run the following command:
Convert a dconf file into a Nix file, as expected by Home Manager.
Available options: -h,--help Show this help text -v,--version Show the current version -r,--root ARG Custom root path. e.g.: system/locale/ --verbose Verbose mode (debug) -i,--input ARG Path to the dconf file (input) -o,--output ARG Path to the Nix output file (to be created)
Custom root
By default, dconf2nix expects the root to be /. If you want to create a dump of a custom root, you can use the --root flag. For example:
With some minor spots (e.g. hexadecimal floats), the complete GVariant text format is supported. But because Nix and GVariant data models are quite different, the Nix format can be a bit verbose, relying on constructor functions.
GNOME Shell configuration
Once you have your dconf.nix, you can import it via Home Manager.
{ programs.home-manager.enable=true;
imports=[ ./dconf.nix ]; }
If you are using the Home Manager module for NixOS you can import it like so: