-
-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
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
Syntax error when using world clocks #33
Comments
@johanbrandhorst are you sure the double quotes are necessary? The protocol does not mention this at all. |
Or are you suggesting |
Yes,
Which produces
|
I wonder if that's a valid input at all. Was that generated by |
The original error was produced using |
Usually,
Parsing this content, # Generated via dconf2nix: https://github.com/gvolpe/dconf2nix
{ lib, ... }:
let
mkTuple = lib.hm.gvariant.mkTuple;
in
{
dconf.settings = {
"org/gnome/shell/extensions/dash-to-panel" = {
panel-element-positions = "'{"0":[{"element":"showAppsButton","visible":false,"position":"stackedTL"},{"element":"activitiesButton","visible":false,"position":"stackedTL"},{"element":"leftBox","visible":true,"position":"stackedTL"},{"element":"taskbar","visible":true,"position":"stackedTL"},{"element":"centerBox","visible":true,"position":"stackedBR"},{"element":"rightBox","visible":true,"position":"stackedBR"},{"element":"systemMenu","visible":true,"position":"stackedBR"},{"element":"dateMenu","visible":true,"position":"stackedBR"},{"element":"desktopButton","visible":false,"position":"stackedBR"}]}'";
};
};
} Can you check if this works for you? Not sure how HM will process this result back to Otherwise, I'd need more proof that a value can be wrapped in double and single quotes at the same time. FWIW this can be solved too in the Nix generator (the parser does not have issues with it) but I want to make sure there is a problem to solve first. |
I don't know where the double quote came from, but it was there when I debugged it. I fixed it manually already and I don't disagree that dconf2nix does the right thing with that input, but I am certain that I didn't manually insert any double quotes into the initial dconf database values. It's up to you whether you want to handle this strange corner case or not, I just wanted to be a good citizen and raise an issue I had with the software. |
Thanks for raising the issue. I'll close it for now but if it ever comes back, the (relevant) |
I can still reproduce this with v0.0.7. The following
Produces the following file:
Neither lines of which are valid |
The second part of this issue is still present in v0.0.8, the incorrect translation of the
Produces the following output:
The quotes inside of the double quotes should be escaped, I think. |
That's fixed in |
Thanks for this great tool! I installed from
master
usingAnd when I ran it, it produce the following incorrect line:
The double quotes cause a parsing error.
I also ran into #31, though that issue was closed, so I'm a little confused what happened there.
The text was updated successfully, but these errors were encountered: