nix-community / dconf2nix

:feet: Convert dconf files (e.g. GNOME Shell) to Nix, as expected by Home Manager [maintainer=@jtojnar]

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Header namespaces separated by `.` are not supported

mannp opened this issue · comments

commented

Hi there

I am getting the following error from my dconf export and attempted conversion;

dconf2nix: "dconf.settings" (line 160, column 4):
unexpected "."
expecting letter or digit, " ]", "]", "/", "-" or ":"
CallStack (from HasCallStack):
  error, called at src/DConf2Nix.hs:35:16 in dconf2nix-0.0.8-DdiL9AwJHriJYUd1qk7zL9:DConf2Nix

Offending dconf line 160 ;

160 [uk.co.ibboard.cawbird]
161 round-avatars=false
162 startup-accounts=['account_name']
163 window-geometry={'account_name': (30, 26, 694, 1182)}

It appears to be complaining about the dot after [uk and I wondered if is a bug or not supported?

Thanks in advance

Hi @mannp ,

I am not sure if that's valid dconf settings but I can tell you that header format is definitely not supported by dconf2nix (and I'm not sure if it should be supported). Header values usually are separated by / AFAIK. E.g.

[org/gnome/nautilus/window-state]
initial-size=(2115, 738)
maximized=false
sidebar-width=485
start-with-sidebar=true

Most dconf docs I can find (e.g. this one) don't mention the usage of . as a separator in the headers. A quick search seems to be pointing to newer versions of Gsettings but I'm not completely sure.

I guess your example is generated by this app? https://github.com/IBBoard/cawbird

If you can share more info on whether . is a valid separator in a donf file, I can consider supporting it. Maybe the maintainers of that application can shed some light as well.

commented

Hi @gvolpe fair points, and I am not sure, but have logged a bug report /query with the cawbird devs.

@mannp @Krutonium I'd appreciate it if any of you could test your applications using . in the headers namespace and report back on #56, I do not use any programs with that format, thanks!

commented

@gvolpe this has been resolved for me as changes have been made in cawbird.

Thanks for your engagement with the issue, but I will now close.