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 have observed Custom dumping its variables into the wrong spot multiple times today.
As far as I can tell, the steps to reproduce the issue are:
Have some stuff inside your dotspacemacs/user-init
Open your dotspacemacs for editing, and make some changes
Open the Customize interface, and make some changes and APPLY AND SAVE THEM FOR FUTURE SESSIONS
Quit Emacs, with or without saving .spacemacs
Reopen Emacs and your .spacemacs should be borked, with the following paragraph describing wherecustom-set-variables was dumped improperly.
It seems that custom-set-variables is inserted into dotspacemacs/user-init just before the first trailing s character in a variable value of the setq form.
Previously, I had witnessed this occurring multiple times with rmail-movemail-variant-in-use 'mailutil*s, where * indicates where custom-set-variables was inserted. This happened multiple times, remember.
I have added a new variable, which happens to have a trailing s character in it's value: rmail-movemail-flags (list "--tl*s"), with * again indicating where custom-set-variables is inserted.
I already updated my packages and pulled the latest changes in an attempt to see if that would resolve it, with no such luck.
What a strange bug.
The portion the Custom inserts is the form beginning with (custom-set-variables [...] and ending with the final parenthesis in the file.
The text was updated successfully, but these errors were encountered:
I have observed Custom dumping its variables into the wrong spot multiple times today.
As far as I can tell, the steps to reproduce the issue are:
dotspacemacs/user-init
custom-set-variables
was dumped improperly.It seems that
custom-set-variables
is inserted intodotspacemacs/user-init
just before the first trailings
character in a variable value of thesetq
form.Previously, I had witnessed this occurring multiple times with
rmail-movemail-variant-in-use 'mailutil*s
, where*
indicates wherecustom-set-variables
was inserted. This happened multiple times, remember.I have added a new variable, which happens to have a trailing
s
character in it's value:rmail-movemail-flags (list "--tl*s")
, with*
again indicating wherecustom-set-variables
is inserted.I already updated my packages and pulled the latest changes in an attempt to see if that would resolve it, with no such luck.
What a strange bug.
The portion the Custom inserts is the form beginning with
(custom-set-variables [...]
and ending with the final parenthesis in the file.The text was updated successfully, but these errors were encountered: