Skip to main content
24 events
when toggle format what by license comment
Jun 14, 2021 at 2:35 answer added Tyler timeline score: 1
Jun 13, 2021 at 22:03 history bumped CommunityBot This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Feb 13, 2021 at 21:04 history bumped CommunityBot This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Oct 16, 2020 at 20:00 history bumped CommunityBot This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Jun 18, 2020 at 19:04 history bumped CommunityBot This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Feb 22, 2020 at 21:55 comment added Phil This answer whilst not a solution has some more details and advice on how to handle the issue, and confirms the duplication of all custom options, when editing any custom option via the customize UI, as described above: stackoverflow.com/a/10973076/2904770 - it's not really an answer, but useful reading nonetheless!
Feb 19, 2020 at 19:02 history bumped CommunityBot This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Jan 20, 2020 at 21:53 comment added phils I suspect you have tried to convert the code (setq FOO BAR) into (custom-set-variables '(FOO BAR)), without taking into account the fact that the latter form is quoted. (I can't see an original working/setq version of that code, though, so I'm only guessing.)
Jan 20, 2020 at 21:43 comment added phils There was a normal quote prior to (around) the backquoted part, so your backquote and comma are just a backquote and comma -- quoted literally along with everything else.
Jan 20, 2020 at 18:19 history edited Phil CC BY-SA 4.0
added 4 characters in body
Jan 20, 2020 at 16:18 history edited Phil CC BY-SA 4.0
added 27 characters in body
Jan 20, 2020 at 15:37 history edited Phil CC BY-SA 4.0
added 2664 characters in body
Jan 20, 2020 at 15:32 history edited Phil CC BY-SA 4.0
added 2664 characters in body
Jan 20, 2020 at 14:40 history edited Phil CC BY-SA 4.0
added 3326 characters in body
Jan 20, 2020 at 14:34 history edited Phil CC BY-SA 4.0
added 3326 characters in body
Jan 19, 2020 at 23:33 comment added Phil I was hoping the backtick + comma would mean that the local variable was evaluated in-place? It seems to work until customize writes out the incorrect version which tramples it? I'm retesting how it gets trampled now - I'm not (intentionally) using both methods to cause the trampling myself, but this would explain the behaviour... I'll delete custom.el and restart emacs. My belief is that I can show custom.el being recreated and trampling my settings without me setting any of the trampled values in customize interface.
Jan 19, 2020 at 23:13 history edited Drew
edited tags
Jan 19, 2020 at 23:12 comment added Drew And you apparently did what @phils mentions using Customize (e.g. M-x customize-option). That's the problem: you set and saved the value using Customize. And then you also set it in your init file (with code that correctly binds emacs-temp etc.).
Jan 19, 2020 at 23:08 comment added phils "complicated expressions seems to get rendered incorrectly ... containing an out of scope emacs-temp" -- naturally; you quoted the value, so of course it's like that. I.e. you used (custom-set-variables 'FOO), hence a verbatim FOO is set and saved.
Jan 19, 2020 at 23:07 answer added Drew timeline score: 1
Jan 19, 2020 at 23:00 history edited Phil CC BY-SA 4.0
edited tags
Jan 19, 2020 at 22:52 history edited Phil CC BY-SA 4.0
added 4 characters in body
Jan 19, 2020 at 22:46 history edited Phil CC BY-SA 4.0
added 4 characters in body
Jan 19, 2020 at 22:40 history asked Phil CC BY-SA 4.0