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
I noticed in nix-community/home-manager#2249 that dconf2nix generates output in a "raw" dconf format, for example, the uint32 value 0 is emitted as a Nix string "uint32 0". This is not really the intended way to construct GVariant values in the HM library. The recommended way to emit values is to use the various mk functions as described in the manual (scroll down to where hm.types.gvariant starts).
For example, instead of having "uint32 0" one would use lib.hm.gvariant.mkUint32 0. Using the functions should be considerably more robust.
Btw, very neat project! Good job 🙂
The text was updated successfully, but these errors were encountered:
I noticed in nix-community/home-manager#2249 that dconf2nix generates output in a "raw" dconf format, for example, the uint32 value 0 is emitted as a Nix string
"uint32 0"
. This is not really the intended way to construct GVariant values in the HM library. The recommended way to emit values is to use the variousmk
functions as described in the manual (scroll down to wherehm.types.gvariant
starts).For example, instead of having
"uint32 0"
one would uselib.hm.gvariant.mkUint32 0
. Using the functions should be considerably more robust.Btw, very neat project! Good job 🙂
The text was updated successfully, but these errors were encountered: