Should I use
custom-set-variables (as opposed to
setq) when setting a variable that returns non-nil for
custom-variable-p but was not defined by
The documentation for
A customizable variable is either (i) a variable whose property list contains a non-nil ‘standard-value’ or ‘custom-autoload’ property, or (ii) an alias for another customizable variable.
This leaves me wondering if the conventional advice to prefer
setq when dealing with custom variables (since they may have special setters and/or initialization code) applies to such variables, or whether it's exclusive to variables defined via
If I should only bother with
custom-set-variables when dealing with those defined by
defcustom, how can I quickly make that determination? I was hoping to use
custom-variable-p to programmatically check which variables I should set with
custom-set-variables instead of
setq, as I'd rather not have to dig through library source code for every variable I set.