We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
right now dconf2nix interprets a{sv} types as strings, but putting quotes around them makes them interpreted as strings which will not be interpreted
understand a{sv} types, for example
{'org.wezfurlong.wezterm': <{'padding': <{'left': <uint32 13>, 'right': <uint32 14>, 'top': <uint32 29>, 'bottom': <uint32 13>}>, 'keep_rounded_corners': <{'maximized': <false>, 'fullscreen': <false>}>, 'border_radius': <uint32 12>, 'smoothing': <uint32 0>, 'enabled': <true>}>}
i can't think of one
support for a{sv} types may also need to be added to home manager, in the form of sets as accepted datatypes possibly ?
The text was updated successfully, but these errors were encountered:
i think this might be a duplicate of #71
Sorry, something went wrong.
No branches or pull requests
The Problem
right now dconf2nix interprets a{sv} types as strings, but putting quotes around them makes them interpreted as strings which will not be interpreted
The Solution
understand a{sv} types, for example
Alternatives
i can't think of one
Additional context
support for a{sv} types may also need to be added to home manager, in the form of sets as accepted datatypes possibly ?
Happens in the latest version
The text was updated successfully, but these errors were encountered: